RFC 4276: BGP-4 Implementation Report
In plain English — editorial summary, not part of the RFC
This document reports the results of the BGP-4 implementation survey. The survey had 259 questions about implementations' support of BGP-4 as specified in RFC 4271. After a brief summary of the results, each response is listed. This document contains responses from the four implementers that completed the survey (Alcatel, Cisco, Laurel, and NextHop) and brief information from three that did not (Avici, Data Connection Ltd., and Nokia). The editors did not use exterior means to verify the accuracy of the information submitted by the respondents. The respondents are experts with the products they reported on. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4276
- Published
- January 2006
- Authors
- S. Hares; A. Retana
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 97
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
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?