ObsoletedPROPOSED STANDARDIETF stream

RFC 4893: BGP Support for Four-octet AS Number Space

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

Current version: RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number Space

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

Currently the Autonomous System (AS) number is encoded as a two-octet entity in BGP. This document describes extensions to BGP to carry the Autonomous System number as a four-octet entity. [STANDARDS-TRACK]

Document record

Document ID
RFC4893
Published
May 2007
Authors
Q. Vohra; E. Chen
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
10
Also known as
Obsoleted by:
RFC 6793

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/4893-bgp-support-for-four-octet-as-number-space