metasystema.org
ObsoletedBEST CURRENT PRACTICEIETF streamBCP172

RFC 6472: Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9774.

Current version: RFC 9774 — Deprecation of AS_SET and AS_CONFED_SET in BGP

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

This document recommends against the use of the AS_SET and AS_CONFED_SET types of the AS_PATH in BGPv4. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a route more clear. This will also simplify the design, implementation, and deployment of ongoing work in the Secure Inter-Domain Routing Working Group. This memo documents an Internet Best Current Practice.

Document record

Document ID
RFC6472
Published
December 2011
Authors
W. Kumari; K. Sriram
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
rtg
Pages
5
Also known as
BCP172
Obsoleted by:
RFC 9774

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/6472-recommendation-for-not-using-as-set-and-as-confed-set-in-bgp