RFC 4278: Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification
In plain English — editorial summary, not part of the RFC
The IETF Standards Process requires that all normative references for a document be at the same or higher level of standardization. RFC 2026 section 9.1 allows the IESG to grant a variance to the standard practices of the IETF. This document explains why the IESG is considering doing so for the revised version of the BGP-4 specification, which refers normatively to RFC 2385, "Protection of BGP Sessions via the TCP MD5 Signature Option". RFC 2385 will remain at the Proposed Standard level. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4278
- Published
- January 2006
- Authors
- S. Bellovin; A. Zinin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- 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 4276BGP-4 Implementation ReportCurrent
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 4264BGP WedgiesCurrent
November 2005
- RFC 4384BGP Communities for Data CollectionCurrent
February 2006
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?