RFC 3682: The Generalized TTL Security Mechanism (GTSM)

The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to protect a protocol stack from CPU-utilization based attacks has been proposed in many…

Read RFC 3682 on the RFC Editor

Outgoing relationships (16 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 791: Internet Protocol
Normative reference — RFC 3032: MPLS Label Stack Encoding
Normative reference — RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
Normative reference — RFC 2784: Generic Routing Encapsulation (GRE)
Normative reference — RFC 2003: IP Encapsulation within IP
Normative reference — RFC 2385: Protection of BGP Sessions via the TCP MD5 Signature Option
Normative reference — RFC 1771: A Border Gateway Protocol 4 (BGP-4)
Normative reference — RFC 3036: LDP Specification
Normative reference — RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers
Normative reference — RFC 1772: Application of the Border Gateway Protocol in the Internet
Normative reference — RFC 3392: Capabilities Advertisement with BGP-4
Normative reference — RFC 2842: Capabilities Advertisement with BGP-4
Informative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 3618: Multicast Source Discovery Protocol (MSDP)
Informative reference — RFC 2028: The Organizations Involved in the IETF Standards Process

Incoming relationships (4 related RFCs)

Obsoleted by — RFC 5082: The Generalized TTL Security Mechanism (GTSM)
Normatively referenced by — RFC 4732: Internet Denial-of-Service Considerations
Informatively referenced by — RFC 4808: Key Change Strategies for TCP-MD5
Informatively referenced by — RFC 4381: Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)