Generalized TTL security mechanism

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Generalized TTL security mechanism" – news · newspapers · books · scholar · JSTOR (July 2016) (Learn how and when to remove this message)

The Generalized TTL Security Mechanism (GTSM) is a proposed Internet data transfer security method relying on a packet's Time to Live (IPv4) or Hop limit (IPv6) thus to protect a protocol stack from spoofing and denial of service attacks.

The desired purpose of this proposal is to verify whether the packet was originated by an adjacent node and to protect router infrastructure from overload-based attacks.

For protocols which GTSM is enabled, the following procedure is performed.

• If the router is directly connected
  • Change the outbound TTL to 255 for its protocol connection
  • If the protocol is a configured protocol peer

    Set the Access Control List (ACL) to allow packets of the given protocol to only pass to the route processor (RP). The TTL must be set to either 255 if the destination is directly connect or 255 minus the range of acceptable hops if not connect directly. This method assumes however that the ACL designated by the receive path is configured to control packets passing to the RP.

• If the inbound TTL is set to 255 or 255 minus the range of acceptable hops (when the peer is not directly connected), the packet will not be processed and will be sent to a low priority queue.

Many people have been given credit for creating the idea. Among them are Paul Traina and Jon Stewart. A similar method was also proposed by Ryan McDowell.^{[citation needed][1]}

• Protocol stack
• Denial-of-service attack

• The Generalized TTL Security Mechanism (GTSM), RFC 5082
• 2015, a Record Year in CyberSecurity Breaches