RFC 1997: BGP Communities Attribute
In plain English — editorial summary, not part of the RFC
This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1997
- Published
- August 1996
- Authors
- R. Chandra; P. Traina; T. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1998An Application of the BGP Community Attribute in Multi-home RoutingCurrent
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
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
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?