RFC 3682: The Generalized TTL Security Mechanism (GTSM)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5082.
Current version: RFC 5082 — The Generalized TTL Security Mechanism (GTSM)
In plain English — editorial summary, not part of the RFC
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 settings (see for example, RFC 2461). This document generalizes these techniques for use by other protocols such as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP), Bidirectional Forwarding Detection, and Label Distribution Protocol (LDP) (RFC 3036). While the Generalized TTL Security Mechanism (GTSM) is most effective in protecting directly connected protocol peers, it can also provide a lower level of protection to multi-hop sessions. GTSM is not directly applicable to protocols employing flooding mechanisms (e.g., multicast), and use of multi-hop GTSM should be considered on a case-by-case basis. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3682
- Published
- February 2004
- Authors
- V. Gill; J. Heasley; D. Meyer
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 5082
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
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?