RFC 2042: Registering New BGP Attribute Types
In plain English — editorial summary, not part of the RFC
This document describes the process for creating new BGP attribute type codes. Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, and new attribute type codes that are used in the Internet are registered with the IANA. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2042
- Published
- January 1997
- Authors
- B. Manning
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2547BGP/MPLS VPNsObsoleted
March 1999
- RFC 3167Request to Move RFC 1745 to Historic StatusCurrent
August 2001
- RFC 1998An Application of the BGP Community Attribute in Multi-home RoutingCurrent
August 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
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?