CurrentPROPOSED STANDARDIETF stream

RFC 6286: Autonomous-System-Wide Unique BGP Identifier for BGP-4

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

To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only Autonomous-System-wide (AS-wide) uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issues. This document updates RFC 4271. [STANDARDS-TRACK]

Document record

Document ID
RFC6286
Published
June 2011
Authors
E. Chen; J. Yuan
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
4
Also known as
Updates:
RFC 4271

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/6286-autonomous-system-wide-unique-bgp-identifier-for-bgp-4