RFC 4808: Key Change Strategies for TCP-MD5

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…

Read RFC 4808 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 1323: TCP Extensions for High Performance
Informative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 4107: Guidelines for Cryptographic Key Management
Informative reference — RFC 3036: LDP Specification
Informative reference — RFC 3562: Key Management Considerations for the TCP MD5 Signature Option
Informative reference — RFC 4634: US Secure Hash Algorithms (SHA and HMAC-SHA)
Informative reference — RFC 4278: Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification
Informative reference — RFC 3682: The Generalized TTL Security Mechanism (GTSM)
Informative reference — RFC 4418: UMAC: Message Authentication Code using Universal Hashing

Incoming relationships (5 related RFCs)

Informatively referenced by — RFC 5920: Security Framework for MPLS and GMPLS Networks
Informatively referenced by — RFC 5925: The TCP Authentication Option
Informatively referenced by — RFC 6810: The Resource Public Key Infrastructure (RPKI) to Router Protocol
Informatively referenced by — RFC 8210: The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
Informatively referenced by — RFC 7211: Operations Model for Router Keying