RFC 1773: Experience with the BGP-4 protocol
In plain English — editorial summary, not part of the RFC
The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report documents experience with BGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1773
- Published
- March 1995
- Authors
- P. Traina
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Obsoletes:
- RFC 1656
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 1774BGP-4 Protocol AnalysisCurrent
March 1995
- RFC 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
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?