A new Request for Comments is now available in online RFC libraries.
RFC 9774
Title: Deprecation of AS_SET and AS_CONFED_SET in BGP
Author: W. Kumari,
K. Sriram,
L. Hannachi,
J. Haas
Status: Standards Track
Stream: IETF
Date: May 2025
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 13
Obsoletes: RFC 6472
Updates: RFC 4271, RFC 5065
I-D Tag: draft-ietf-idr-deprecate-as-set-confed-set-18.txt
URL: https://www.rfc-editor.org/info/rfc9774
DOI: 10.17487/RFC9774
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.
This document is a product of the Inter-Domain Routing Working Group of the
IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
