RFC 4274: 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 publication of a routing protocol as an Internet Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report satisfies the requirement for "the second report", as described in Section 6.0 of RFC 1264. In order to fulfill the requirement, this report augments RFC 1774 and summarizes the key features of BGP-4, as well as analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4274
- Published
- January 2006
- Authors
- D. Meyer; K. Patel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4276BGP-4 Implementation ReportCurrent
January 2006
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4486Subcodes for BGP Cease Notification MessageUpdated
April 2006
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
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?