IDR Session

Summary

The IDR session covered a wide range of topics, including updates on various drafts, working group status, and discussions around key routing and signaling mechanisms. Significant discussion revolved around the CAR and CT drafts, SRv6, and several proposed extensions to BGP. The session also featured requests for working group adoption for certain drafts.

Key Discussion Points

Working Group Status: The ISG is serious about the 5 author limit on RFCs and Internet drafts. The B2B Yang model is finished with working group last call. CAR and CT are in last call. The SRV6 policy document shipper review is done.
Link Bandwidth: Two flavors of link bandwidth are floating around; efforts are underway to clean this up, potentially involving an interim meeting.
Segment Routing Policies: Concerns about unimplemented types. Discussion on potentially separating unimplemented types into a separate document.
CAR/CT (Class for Transport): Discussion on the need for intent-based routing and forwarding. Reviewers are needed, and feedback is strongly requested. Support will be judged by the end of the week. Addressing concerns about dependencies on non-adopted drafts. Discussion on redundancy aspects of BGP CT.
BGP CAR Updates: Extended for SRv6. Locator distribution, new SAFI for transport purposes. Addressing concerns on why CAR is not reusing existing SAFI.
BGP Colorful Prefix Routing (CPR) for SRv6: Informational document. The basic principle of the CPR is to make use of the SR 6 locators to represent the different in terms of colors. Discussion on the relation between interdomain and explicitly limited domain protocol.
Multiple Next Hop Attribute (MNH): Discussion on removing the propagation scope checker. Use cases: ECMP, load balancing, label oscillation avoidance. Request for adoption.
SRv6 Segment List Optimization: Proposed solution for optimization of tail-end decapsulation, including a new "egress node SID" flag.
OEDI (Overlapping EGP Domains Interconnect): New peering type to carry IBGP specific attributes across administrative domains. New session type.
5G Edge Service Metadata: Site availability index, preference index, service delay prediction. Expert review recommended for INA registry.
Transport Network Aware and Mobility: Utilize flows back to pass the policy into the ingress node. Redirect into SD WAN IPSec tunnels.
Segment List Protection: B flag in the segment list ABTRV to indicate a pure backup list.
SRV6 and MPLS Coexistence: A new capability code for SRv6 based BGP service proposed.
BGP-LS Draft for SR Policy Advertisement: Advertising SR policies from PC.
Validity of SR Policy Candidate Path: Introduce control parameters for the regulatory adjustment of county pass.
BGP over QUIC: Discussion of using QUIC as a transport for BGP. Potential benefits include better resiliency and enhanced security. Major concepts discussed: "channels" and asymmetric sessions. Addressed concerns about certificate management.
MP-BGP Extension and Procedure for IPv6 Mapping Out of a Testament: Using existing fyscoffycompilation and new BTP actually pass out.
IPv4PI: Explicit Node Requirement Update

Decisions and Action Items

CAR/CT: Working group last call to continue until the end of the week. Reviewers strongly encouraged to provide feedback. Authors to address concerns about dependencies.
Link Bandwidth: Expect potential interim to address the two flavors of link bandwidth.
Segment Routing Policies: Discussion to continue on the mailing list regarding splitting off unimplemented types into a separate document.
All drafts: send a formal request to the list, and we will take it from there.

Next Steps

Authors to address raised concerns and feedback on the mailing lists.
Chairs to assess working group support for the various draft proposals.
Continue discussions on the mailing list regarding splitting off unimplemented types in segment routing policy documents.
Consider presenting BGP over QUIC to side of ops to get feedback on its security implications.

Session Date/Time: 26 Jul 2023 00:00

idr

Summary

The second IDR session covered several topics, including BGP Flow Specification extensions for Time-Sensitive Networking (TSN), secondary labels for BGP, BPLS extensions for security capabilities, path attribute escape, and source address validation architecture. Discussions revolved around protocol extensions, operational considerations, and potential solutions for identified problems.

Key Discussion Points

BGP Flow Specification Extensions for TSN: Presented extensions for mapping TSN streams to flat flows and vice versa, including filtering rules and latency actions. Alignment with BGP FS version 2 and the Intransit Datapath working group was mentioned.
BGP Secondary Label: A proposal to use a secondary label in BGP to address label churn issues when using per-next-hop received label allocation mode in conjunction with prefix-independent convergence (PIC). The secondary label would be based on the primary path, aiming to improve convergence and prevent label exhaustion.
BPLS Extensions for Security Capabilities: A presentation on extending BPLS to carry security capabilities, including node, link, and prefix attributes. The motivation stemmed from the need for coordination across multiple regions with different security equipment.
Path Attribute Escape: A discussion on the operational problems caused by path attributes propagating outside their intended scope, leading to inconsistent route selection, black holes, and session failures. The presentation suggested building a taxonomy of common scoping criteria and exploring mitigation strategies.
Source Address Validation Architecture: Presentation of a source address validation architecture focusing on automatic updates and accurate validation. The architecture involves exchanging source-specific information to generate more accurate sub-rules than those based solely on routing information. Extending BGP to carry this source-specific information was considered.

Decisions and Action Items

BGP Flow Specification Extensions for TSN: Seek feedback from the IDR working group on the presented extensions.
BGP Secondary Label: Engage with the IETF regarding proper procedures for the proposed attribute.
BPLS Extensions for Security Capabilities: Add "TBD" to attribute codes until allocations are confirmed.
Path Attribute Escape: Socialize the ideas presented and engage with the operational community. Build a problem statement and start building mitigations, operational procedures, and potentially documentation.
Source Address Validation Architecture: Welcome comments on the mailing list.

Next Steps

Continue discussions on the IDR mailing list for all presented topics.
Present the "Path Attribute Escape" concept to other relevant groups, including the nogs.