grow

Summary

This meeting covered several BMP-related drafts, including TLV updates, extensions for non-standard elements, event-driven messages, RPKI filtering, and stats reporting. Discussions focused on simplifying TLV structures, time stamping requirements, code point allocation, addressing redundancy, and new message types. The working group discussed approaches to data synchronization, policy debugging, and monitoring within BMP.

Key Discussion Points

TLV Draft BMP version 4:
- Stateless parsing TLV simplification by using BGP capabilities directly.
- Discussion of making time stamping mandatory and whether this is appropriate in this draft.
- IANA code point allocation requests for TLVs.
- Debate over whether to include AFI/SAFI and capability code in the TLV or just use the raw BGP capability.
EBIT Draft:
- Discussed merging the EBIT draft into the TLV draft.
- Open to alternative methods beyond EBIT for non-standard elements.
Rail Draft:
- Policy discard TLV was reworked based on feedback.
- Open question about REL's role and potential feedback loop use cases (e.g., flowspec).
- Discussion about whether REL should focus on errors or expand to cover a broader set of events.
RIAB Filter Draft:
- Consideration of working group adoption for BMP filtered.
BMP RIP Stats Draft:
- Discussion of initiating a working group last call for the BMP stats draft.
- Addressing stats that have not yet been implemented in production.
BMP Collector Synchronization Draft:
- Proposal to extend the peer header with a P-bit for BMP collector purging.
- Alternative approaches, such as a peer down notification with a TLV or a new message type, were suggested.
Route Policy Modification Draft:
- Proposal to use a C-bit in the peer header or a common update TLV to avoid sending duplicate unmodified messages in pre- and post-policy views.
- Discussion of the percentage of updates modified by inbound or outbound policies.
BMP Local Peer Address Draft:
- Discussion on potential updates to the ARAX peer address TLV.
- Consideration of using IPv6 mapped addresses for IPv4, replacing interface name/ID subtypes with zone IDs, and removing the address type field altogether.

Decisions and Action Items

RIAB Filter Draft: The minute taker to note a to-do item to do a working group call for adoption for BMP filtered.
BMP RIP Stats Draft:
- The minute taker to note a to-do item that working group last call will be issued for BMP stats.
- Confirm with the authors that they think they are at the point of being ready for last call.
BMP Collector Synchronization and Route Policy Modification Drafts: Multiple implementers should get together and converge on what is the most efficient way to get the task done and then circle back to the working group for working group adoption.

Next Steps

Paolo to process feedback on the TLV, EBIT and Rail drafts.
Authors of drafts under discussion to consider the various suggestions made and potential integrations with other BMP drafts.
Working group to discuss and converge on a preferred method for handling synchronization.
Maxentiancy to process comments regarding the BMP Local Peer Address Draft.

Session Date/Time: 20 Mar 2025 10:00

grow

Summary

This was the second grow session at IETF 122. The session covered updates on several drafts, including BMP state summaries, BCP 194 revisions, source address validation deployment status, requirements for monitoring RPKI related processes on routers using BMP, and using BMP over quick connections. The chair initiated an adoption call for the terminology and routing drafts. There was a discussion on the feasibility of implementing BMP features on both the exporting and station sides. Also, the role of RFC editor was discussed.

Key Discussion Points

BMP State Summaries:
- The draft has been retitled "BMP State Summaries" with a revised approach.
- The new approach introduces a state summary message as a collection of TLVs, including a mandatory summary ID TLV.
- Open questions include the need to signal the end of a summary and whether the initial sync could be changed to a summary.
- Concerns were raised about the cost of going over RIP content on the exporting side and potential need to make parts of the summary optional.
- Discussions suggested leveraging the end-of-rib mechanism for state summaries.
BCP 194 Revisions:
- The main document is waiting for two eternal drafts (EDs) to be adopted.
- A call for working group adoption of the EDs was initiated, with limited response.
- Suggestions to proceed with adoption if no objections are raised.
- Discussion regarding the status of BCP194 and the need to "kill it".
Source Address Validation Deployment Status:
- Draft presentation covering measurement methods and deployment status of source address validation.
- Observed about 67% of tested IPV4 ASNs and 72% of tested IPV6 ASNs lack any source address validation deployment.
- Manors network shows higher deployment ratio.
Requirements for Monitoring RPKI Related Processes on Routers Using BMP:
- Proposal of requirements for monitoring RPKI-related processes on routers using BMP.
- Discussion on the need to monitor the full life cycle of RPKI processes on routers.
- High-level requirements were raised for supporting RPKI in BMP.
Using BMP over Quick Connections:
- Update on the draft for using BMP over quick connections, including the addition of two new multi-stream usage modes.
- Discussions around stream allocation, multiplexing, and out-of-order messages.
- Concerns raised about appropriately mapping concepts for BMP.

Decisions and Action Items

Action Item: Chair to send a reminder to the working group about the adoption call for the terminology and routing drafts.
Decision: Proceed with the BMP State Summary approach with its new message type.
Action Item: The BMP over Quick authors to continue collaboration on understanding how exactly B&P benefits from Quig.

Next Steps

Determine if the revised BMP State Summary approach is a better way forward than the previous one, focusing on feasibility on the exporting side.
Address the question about how the approach interacts with the system for assigning BCP numbers.
Continue discussions on the mailing list for the RPKI monitoring draft.