Search RFCs
RFC 9774
Deprecation of AS_SET and AS_CONFED_SET in BGP,May 2025
- File formats:
- Also available:XML file for editing
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 6472
- Updates:
- RFC 4271,RFC 5065
- Authors:
- W. Kumari
K. Sriram
L. Hannachi
J. Haas - Stream:
- IETF
- Source:
- idr (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9774
Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9774
Abstract
BCP 172 (i.e., RFC 6472) recommends not using AS_SET andAS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol(BGP). This document advances that recommendation to a standardsrequirement in BGP; it prohibits the use of the AS_SET andAS_CONFED_SET path segment types in the AS_PATH. This is done tosimplify the design and implementation of BGP and to make thesemantics of the originator of a BGP route clearer. This will alsosimplify the design, implementation, and deployment of various BGPsecurity mechanisms. This document updates RFC 4271 by deprecatingthe origination of BGP routes with AS_SET (Type 1 AS_PATH segment)and updates RFC 5065 by deprecating the origination of BGP routeswith AS_CONFED_SET (Type 4 AS_PATH segment). Finally, it obsoletesRFC 6472.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.