metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9774
Published
May 2025
Authors
W. Kumari; K. Sriram; L. Hannachi; J. Haas
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
13
Also known as
—
Obsoletes:
RFC 6472
Updates:
RFC 4271, RFC 5065

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9774-deprecation-of-as-set-and-as-confed-set-in-bgp