RFC 5925: The TCP Authentication Option

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…

Read RFC 5925 on the RFC Editor

Outgoing relationships (26 related RFCs)

Obsoletes, Normative reference — RFC 2385: Protection of BGP Sessions via the TCP MD5 Signature Option
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Normative reference — RFC 793: Transmission Control Protocol
Normative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Normative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Normative reference — RFC 4306: Internet Key Exchange (IKEv2) Protocol
Normative reference — RFC 2018: TCP Selective Acknowledgment Options
Normative reference — RFC 2883: An Extension to the Selective Acknowledgement (SACK) Option for TCP
Normative reference — RFC 2403: The Use of HMAC-MD5-96 within ESP and AH
Normative reference — RFC 3517: A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP
Normative reference — RFC 4724: Graceful Restart Mechanism for BGP
Normative reference — RFC 5926: Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)
Normative reference — RFC 4781: Graceful Restart Mechanism for BGP with MPLS
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 4301: Security Architecture for the Internet Protocol
Informative reference — RFC 2104: HMAC: Keyed-Hashing for Message Authentication
Informative reference — RFC 1321: The MD5 Message-Digest Algorithm
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 1323: TCP Extensions for High Performance
Informative reference — RFC 3234: Middleboxes: Taxonomy and Issues
Informative reference — RFC 4953: Defending TCP Against Spoofing Attacks
Informative reference — RFC 1948: Defending Against Sequence Number Attacks
Informative reference — RFC 3947: Negotiation of NAT-Traversal in the IKE
Informative reference — RFC 3562: Key Management Considerations for the TCP MD5 Signature Option
Informative reference — RFC 4808: Key Change Strategies for TCP-MD5

Incoming relationships (63 related RFCs)

Showing 50 of 63 related RFCs.

Normatively referenced by — RFC 6810: The Resource Public Key Infrastructure (RPKI) to Router Protocol
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Normatively referenced by — RFC 7454: BGP Operations and Security
Normatively referenced by — RFC 8210: The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 6978: A TCP Authentication Option Extension for NAT Traversal
Normatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Normatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Normatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 7353: Security Requirements for BGP Path Validation
Normatively referenced by — RFC 9346: IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 8751: Hierarchical Stateful Path Computation Element (PCE)
Normatively referenced by — RFC 9353: IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
Normatively referenced by — RFC 9648: YANG Data Model for TCP
Normatively referenced by — RFC 9826: A YANG Data Model for the Path Computation Element Communication Protocol (PCEP)
Normatively referenced by — RFC 6559: A Reliable Transport Mechanism for PIM
Normatively referenced by — RFC 8916: A YANG Data Model for the Multicast Source Discovery Protocol (MSDP)
Normatively referenced by — RFC 9125: Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing
Normatively referenced by — RFC 9415: On the Generation of Transient Numeric Identifiers
Normatively referenced by — RFC 9832: BGP Classful Transport Planes
Informatively referenced by — RFC 7432: BGP MPLS-Based Ethernet VPN
Informatively referenced by — RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
Informatively referenced by — RFC 9293: Transmission Control Protocol (TCP)
Informatively referenced by — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Informatively referenced by — RFC 6952: Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
Informatively referenced by — RFC 6296: IPv6-to-IPv6 Network Prefix Translation
Informatively referenced by — RFC 8177: YANG Data Model for Key Chains
Informatively referenced by — RFC 6836: Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)
Informatively referenced by — RFC 5927: ICMP Attacks against TCP
Informatively referenced by — RFC 6039: Issues with Existing Cryptographic Protection Methods for Routing Protocols
Informatively referenced by — RFC 6528: Defending against Sequence Number Attacks
Informatively referenced by — RFC 7117: Multicast in Virtual Private LAN Service (VPLS)
Informatively referenced by — RFC 6518: Keying and Authentication for Routing Protocols (KARP) Design Guidelines
Informatively referenced by — RFC 6006: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Informatively referenced by — RFC 9252: BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
Informatively referenced by — RFC 9040: TCP Control Block Interdependence
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 6720: The Generalized TTL Security Mechanism (GTSM) for the Label Distribution Protocol (LDP)
Informatively referenced by — RFC 7132: Threat Model for BGP Path Security
Informatively referenced by — RFC 8306: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Informatively referenced by — RFC 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Informatively referenced by — RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture
Informatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Informatively referenced by — RFC 6013: TCP Cookie Transactions (TCPCT)
Informatively referenced by — RFC 7705: Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH Attribute
Informatively referenced by — RFC 7897: Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)
Informatively referenced by — RFC 8782: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Informatively referenced by — RFC 8922: A Survey of the Interaction between Security Protocols and Transport Services
Informatively referenced by — RFC 8923: A Minimal Set of Transport Services for End Systems