Deprecation of AS_SET and AS_CONFED_SET in BGP
RFC 9774
Revision differences
Document history
Date | By | Action |
---|---|---|
2025-05-21
|
(System) | Received changes through RFC Editor sync (created document RFC 9774, created became rfc relationship between draft-ietf-idr-deprecate-as-set-confed-set and RFC 9774, set abstract to 'BCP … Received changes through RFC Editor sync (created document RFC 9774, created became rfc relationship between draft-ietf-idr-deprecate-as-set-confed-set and RFC 9774, set abstract to 'BCP 172 (i.e., RFC 6472) recommends not using AS_SET and AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol (BGP). This document advances that recommendation to a standards requirement in BGP; it prohibits the use of the AS_SET and AS_CONFED_SET path segment types in the AS_PATH. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a BGP route clearer. This will also simplify the design, implementation, and deployment of various BGP security mechanisms. This document updates RFC 4271 by deprecating the origination of BGP routes with AS_SET (Type 1 AS_PATH segment) and updates RFC 5065 by deprecating the origination of BGP routes with AS_CONFED_SET (Type 4 AS_PATH segment). Finally, it obsoletes RFC 6472.', set pages to 13, set standardization level to Proposed Standard, added RFC published event at 2025-05-21, created obsoletes relation between RFC 9774 and RFC 6472, created updates relation between RFC 9774 and RFC 4271, created updates relation between RFC 9774 and RFC 5065) |
2025-05-21
|
(System) | RFC published |