Session Date/Time: 09 Feb 2026 15:00

IDR

Summary

The IDR interim meeting covered a wide range of topics, including updates on the working group's status and processes, discussions on several BGP-related drafts, and calls for adoption or early allocation. Key technical discussions revolved around improving RPKI-based origin attestation, extending BGP-LS for service metadata and cell rule distribution, addressing IANA code point issues for BGP dynamic capability, and evolving FlowSpec with new filtering and feedback mechanisms. The chairs reiterated their commitment to proactive review processes and fostering clear technical discussion.

Key Discussion Points

IDR Working Group Status Update:
- The chairs provided an overview of IDR's status tracking, emphasizing a transition towards using GitHub for daily work, action items, and tracking drafts, especially those in Working Group Last Call (WGLC).
- Work is now organized into functional queues by area, including Core BGP, BGP FlowSpec, BGP-LS, BGP Segment Routing (including TE), and BGP-SR (Prefix-SID attribute).
- Current WGLC drafts (draft-ietf-idr-mhc, draft-ietf-idr-sr-policy-sedg-list, draft-ietf-idr-flowspec-redirect, draft-ietf-idr-ts-flowspec-sr-policy) are in various stages of review, revision, or awaiting IPR.
- Chairs are adopting a proactive stance, initiating English language, IANA, early routing DER, and IDR chair reviews prior to WGLC.
RPKI-based Origin Attestation (BGPoA) - presented by Jing Zhao:
- The presentation highlighted challenges with existing RPKI deployment, specifically transient false positives due to synchronization issues and outdated data, leading to operational overhead and hesitation in deploying Route Origin Validation (ROV).
- A solution was proposed using a BGP Origin Attestation (BGPoA) attribute extension to perform pre-validation at the origin and attest this validated information downstream, aiming to synchronize data and reduce false positives.
- Discussion focused on the value proposition of advertising attestation if local pre-validation already prevents inconsistencies and whether this mechanism inadvertently tolerates misconfigurations rather than incentivizing their correction.
- The chair encouraged continued discussion on both the IDR and CiderOps mailing lists.
Distribution of Service Metadata in BGP-LS - presented by Xinxin Yi:
- This draft proposes extending BGP-LS to collect service metadata from compute nodes for the CATS (Compute-Aware Traffic Steering) framework, supporting centralized and hybrid deployment models.
- New TLVs were defined for Prefix NLRI, Metadata Path Attributes, Prefix SID Attributes (extending RFC 9185), and Color Attributes.
- The chair noted concerns about the interaction of this work with the CATS Charter and IDR's defined scope.
BGP-LS SR Policy Supplement - presented by Yao Liu:
- The draft aims to supplement existing SR Policy information in BGP-LS by including the administrative state of a segment list and 32-bit S-MPLS information (TC/TTL fields) relevant for MNA sub-stack solutions.
- Proposed extensions include an 'S' flag in the SR SegmentList TLV for administrative state and a new 32-bit MPLS LSC sub-TLV.
- A question was raised regarding the compatibility of MNA label stack formats with the SR architecture, particularly concerning RFC 9256. Joel Halpern offered to provide input on this.
Advertisement of Multi-Sourced Cell Rules using BGP-LS - presented by Jing Zhao:
- The presentation outlined a method to advertise multi-sourced cell rules (from various origins like static config, OSPF, BGP) to a network controller using BGP-LS extensions.
- A BGP-LS SAURU-NLRI was defined, including Interface Name TLV, Interface Group TLV, Cell Prefix TLV, and a Cell Mode Attribute for various validation modes.
- The key principle is that these cell rules primarily reside on access/boundary routers and the network controller, simplifying management and conflict resolution.
BGP Dynamic Capability Early Allocation - presented by Sri Hari:
- An update was provided on draft-ietf-idr-dynamic-cap, which proposes dynamic negotiation of capabilities during a BGP session without requiring a session reset.
- The presentation highlighted an issue with previously proposed IANA code points, specifically a conflict where code 0.7 for BGP Notification Error is already allocated.
- The updated draft (version 18) requests code 0.6 for the dynamic capability message and a new code point for BGP notification errors.
- The chair requested information on existing implementations (e.g., Cisco NX-OS, Nokia) and their stability for early allocation testing.
FlowSpec Introduction and Status - presented by Sue Hares:
- The chair provided a roadmap for FlowSpec v1 and v2, including the generation of shepherd reports for all drafts to guide modifications.
- Upcoming steps involve sending out existing v1 action drafts, reclassifying action drafts, and initiating adoption calls for new v2 IP filters.
- Flow Spec Extension for Feedback Binding - presented by Yuzhao Li: This draft proposes a FlowSpec feedback action, encoded in a community container, to track the execution status of FlowSpec rules via a state machine, aiming to bridge the gap between control plane intent and data plane enforcement.
- Packet Content Filter for BGP Flow Spec - presented by Yuzhao Li: This FlowSpec v2 filter enables matching on packet contents (payload filter) to address complex DDoS attacks, with careful consideration for operational, security, and scalability aspects. Hardware validation was demonstrated.
- Bitwise IP Filters for BGP Flow Spec - presented by Net Gao: This FlowSpec v2 filter provides a mechanism for symmetric load balancing based on bitwise matching of subscriber IP addresses, with deployment guidelines for avoiding forwarding loops and hierarchical balancing.
- A recurring discussion point across FlowSpec presentations was the critical need to define how different types of FlowSpec rules interact safely, detect conflicts, and establish a clear order of operations in the forwarding pipeline, rather than solely focusing on extensible PDU formats.
BGP-LS SRv6 Transport - presented by Swadesh Agarwal:
- The draft proposes to advertise SRv6 SIDs (specifically DTM46 and DTM behaviors) with the BGP-LU SAFI for inter-domain SRv6 and MPLS interworking, aligning with existing SRv6 architecture documents.
- A new SRv6 Transport TLV within the BGP Prefix SID attribute is defined for this purpose.
- The presenter noted interest from deployments and multiple implementations underway.
BGP-SR Policy & Prefix SID Attribute Status - presented by Sue Hares:
- The chair provided an overview of the extensive work in BGP-SR (SR Policy/SR-TE) and BGP-SR (Prefix SID attribute), highlighting approved, adopted, and pending adoption drafts.
- Emphasis was placed on ensuring clarity in drafts regarding which NLRI and sub-TLVs they operate on.
- The chairs will focus reviews on questions about the utility of identifiers and metrics, and potential interactions or conflicts among head-end actions.

Decisions and Action Items

RPKI-based Origin Attestation:
- Action: Presenter Jing Zhao is to continue discussion on the IDR and CiderOps mailing lists.
BGP-LS SR Policy Supplement:
- Action: Yao Liu is to send an email to Joel Halpern with detailed questions regarding MNA label stack format compatibility with RFC 9256, and Joel Halpern will provide input to the IDR chairs and execs.
BGP Dynamic Capability Early Allocation:
- Action: Sri Hari is to solicit implementation reports from co-authors (Cisco NX-OS, Nokia, others if known) to confirm the stability of the implementation for early allocation testing and respond to the mailing list.
- Decision: The chairs will initiate a working group poll for early allocation after this meeting.
FlowSpec New Filters/Actions:
- Action: Xinxin Yi is to consider if a different protocol leveraging FlowSpec encodings would be more appropriate for distributing computing metrics if the goal is not to integrate into the FlowSpec forwarding chain; further discussion with chairs on mailing list or Zoom.
- Action: Net Gao is to discuss on the mailing list how Bitwise IP Filters will interact with other FlowSpec rule types, especially concerning multiple redirection actions.
BGP-LS SRv6 Transport:
- Decision: The working group will move towards adoption of draft-ietf-idr-bgp-ls-srv6-transport.
- Decision: The working group requests IANA code allocation for the defined TLV.
- Action: Swadesh Agarwal is to provide interoperability examples to support the early allocation request.

Next Steps

All working group participants are encouraged to provide feedback to the chairs on the interim meeting format.
Continue discussions on the respective mailing lists for all presented drafts, especially concerning interaction between different features and architectural implications.
Authors should revise their drafts based on feedback received during the meeting and from shepherd reviews.
The working group looks forward to reconvening virtually or in person at IETF 125.