RFC 1774: BGP-4 Protocol Analysis
In plain English — editorial summary, not part of the RFC
The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol version 4 (BGP-4). This report summarizes the key features of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1774
- Published
- March 1995
- Authors
- P. Traina
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
- RFC 1656BGP-4 Protocol Document Roadmap and Implementation ExperienceObsoleted
July 1994
- 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 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 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?