RFC 6720: The Generalized TTL Security Mechanism (GTSM) for the Label Distribution Protocol (LDP)
In plain English — editorial summary, not part of the RFC
The Generalized TTL Security Mechanism (GTSM) describes a generalized use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to verify that the packet was sourced by a node on a connected link, thereby protecting the router\'s IP control plane from CPU utilization-based attacks. This technique improves security and is used by many protocols. This document defines the GTSM use for the Label Distribution Protocol (LDP). This specification uses a bit reserved in RFC 5036 and therefore updates RFC 5036. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6720
- Published
- August 2012
- Authors
- C. Pignataro; R. Asati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
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.
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 5561LDP CapabilitiesCurrent
July 2009
- RFC 9070YANG Data Model for MPLS LDPCurrent
March 2022
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
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?