RFC 4808: Key Change Strategies for TCP-MD5
In plain English — editorial summary, not part of the RFC
The TCP-MD5 option is most commonly used to secure BGP sessions between routers. However, changing the long-term key is difficult, since the change needs to be synchronized between different organizations. We describe single-ended strategies that will permit (mostly) unsynchronized key changes. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4808
- Published
- March 2007
- Authors
- S. Bellovin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 3562Key Management Considerations for the TCP MD5 Signature OptionCurrent
July 2003
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
- RFC 3219Telephony Routing over IP (TRIP)Updated
January 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
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?