RFC 9117: Revised Validation Procedure for BGP Flow Specifications
In plain English — editorial summary, not part of the RFC
This document describes a modification to the validation procedure defined for the dissemination of BGP Flow Specifications. The dissemination of BGP Flow Specifications as specified in RFC 8955 requires that the originator of the Flow Specification match the originator of the best-match unicast route for the destination prefix embedded in the Flow Specification. For an Internal Border Gateway Protocol (iBGP) received route, the originator is typically a border router within the same autonomous system (AS). The objective is to allow only BGP speakers within the data forwarding path to originate BGP Flow Specifications. Sometimes it is desirable to originate the BGP Flow Specification from any place within the autonomous system itself, for example, from a centralized BGP route controller. However, the validation procedure described in RFC 8955 will fail in this scenario. The modification proposed herein relaxes the validation rule to enable Flow Specifications to be originated within the same autonomous system as the BGP speaker performing the validation. Additionally, this document revises the AS_PATH validation rules so Flow Specifications received from an External Border Gateway Protocol (eBGP) peer can be validated when such a peer is a BGP route server. This document updates the validation procedure in RFC 8955.
Document record
- Document ID
- RFC9117
- Published
- August 2021
- Authors
- J. Uttaro; J. Alcaide; C. Filsfils; D. Smith; P. Mohapatra
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 8955
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9125Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment RoutingCurrent
August 2021
- RFC 9107BGP Optimal Route Reflection (BGP ORR)Current
August 2021
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9128YANG Data Model for Protocol Independent Multicast (PIM)Current
October 2022
- RFC 9129YANG Data Model for the OSPF ProtocolCurrent
October 2022
- RFC 9104Distribution of Traffic Engineering Extended Administrative Groups Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2021
- RFC 9130YANG Data Model for the IS-IS ProtocolCurrent
October 2022
- RFC 9135Integrated Routing and Bridging in Ethernet VPN (EVPN)Current
October 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?