**Session Date/Time:** 06 Nov 2024 13:00

# grow

## Summary

The grow working group meeting at IETF 121 covered several topics related to global routing operations. Discussions included BMP over QUIC, BMP statistics, the use of the DSCP field, a Peering API proposal, offline BMP, and BGP operational security considerations. Several calls for working group adoption were made for presented drafts.

## Key Discussion Points

*   **BMP over QUIC:** A presentation on using BMP over QUIC highlighted potential benefits like improved efficiency and security. Concerns were raised regarding the necessity of security enhancements, potential race conditions with message handling, and the relevance of head-of-line blocking for BMP implementations. There was some agreement that a separate control channel might be beneficial.
*   **BMP Statistics:** An update on the application for IANA code points for new statistical types in the BMP protocol was presented. The importance of an implementation status section for draft progression was emphasized.
*   **Use of DSCP Field:** A presentation discussed the practical use of the DSCP field and its divergence from RFC specifications. The need for standardization and operational considerations was debated. There wasn't really a consensus on what the group could do to contribute to addressing this gap.
*   **Peering API:** A proposal for a Peering API to automate peering turn-up was presented. The discussion centered on the need for such an API, especially with the increasing adoption of RPKI, and whether a standardized LOA substitute could be beneficial. The usefulness of signing the object or not was discussed.
*   **Offline BMP:** A new draft proposing TLVs to make BMP usable offline was introduced. The draft suggested sending periodic summaries of all peers to reduce the amount of data needed to parse to determine peer status. It was proposed that the message generation is a property of the BMP station, but it could also be a property of the BMP exporter. There were questions regarding how errors and conflicts are handled.
*   **BGP Operational Security Considerations:** An update on BGP operational security considerations was given. The approach of splitting the core policy document from implementation examples into separate "eternal drafts" was discussed. There were some concerns about this and the verbage in the documents and if policymakers interpret it to strictly.

## Decisions and Action Items

*   **BMP over QUIC:** The presenter was encouraged to address concerns on the mailing list and consider a separate control channel.
*   **BMP Statistics:** The presenter was requested to include an implementation status section in the next version of the draft (version 06).
*   **Peering API:** A new call for working group adoption will be initiated for the current version of the document (version 6).
*   **BGP Operational Security Considerations:** A call for adoption should be done for the document. Discuss the wording on the mailing list for consideration in editing the draft.

## Next Steps

*   Mailing list discussions will continue for BMP over QUIC, the use of the DSCP field, and the BGP operational security draft.
*   Updated drafts will be submitted for BMP Statistics, Peering API, Offline BMP, and BGP Operational Security Consideration.
*   Working group adoption calls will be initiated for the Peering API proposal and the BGP Operational Security Consideration drafts.