RFC 3562: Key Management Considerations for the TCP MD5 Signature Option
In plain English — editorial summary, not part of the RFC
The TCP MD5 Signature Option (RFC 2385), used predominantly by BGP, has seen significant deployment in critical areas of Internet infrastructure. The security of this option relies heavily on the quality of the keying material used to compute the MD5 signature. This document addresses the security requirements of that keying material. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3562
- Published
- July 2003
- Authors
- M. Leech
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
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?