RFC 5925: The TCP Authentication Option
In plain English — editorial summary, not part of the RFC
This document specifies the TCP Authentication Option (TCP-AO), which obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO specifies the use of stronger Message Authentication Codes (MACs), protects against replays even for long-lived TCP connections, and provides more details on the association of security with TCP connections than TCP MD5. TCP-AO is compatible with either a static Master Key Tuple (MKT) configuration or an external, out-of-band MKT management mechanism; in either case, TCP-AO also protects connections when using the same MKT across repeated instances of a connection, using traffic keys derived from the MKT, and coordinates MKT changes between endpoints. The result is intended to support current infrastructure uses of TCP MD5, such as to protect long-lived connections (as used, e.g., in BGP and LDP), and to support a larger set of MACs with minimal other system and operational changes. TCP-AO uses a different option identifier than TCP MD5, even though TCP-AO and TCP MD5 are never permitted to be used simultaneously. TCP-AO supports IPv6, and is fully compatible with the proposed requirements for the replacement of TCP MD5. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5925
- Published
- June 2010
- Authors
- J. Touch; A. Mankin; R. Bonica
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 48
- Also known as
- —
- Obsoletes:
- RFC 2385
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4456BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)Updated
April 2006
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 2858Multiprotocol Extensions for BGP-4Obsoleted
June 2000
- RFC 2842Capabilities Advertisement with BGP-4Obsoleted
May 2000
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2283Multiprotocol Extensions for BGP-4Obsoleted
February 1998
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 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?