2007
DOI: 10.17487/rfc5082
|View full text |Cite
|
Sign up to set email alerts
|

The Generalized TTL Security Mechanism (GTSM)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
42
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 30 publications
(42 citation statements)
references
References 6 publications
0
42
0
Order By: Relevance
“…The Generalized TTL Security Mechanism (GTSM) [RFC5082] may be used with UDP applications when the intended endpoint is on the same link as the sender. This lightweight mechanism allows a receiver to filter unwanted packets.…”
Section: Icmp Guidelinesmentioning
confidence: 99%
“…The Generalized TTL Security Mechanism (GTSM) [RFC5082] may be used with UDP applications when the intended endpoint is on the same link as the sender. This lightweight mechanism allows a receiver to filter unwanted packets.…”
Section: Icmp Guidelinesmentioning
confidence: 99%
“…Additionally, the GTSM for LDP specified in this document applies only to single-hop LDP peering sessions and not to multi-hop LDP peering sessions, in line with Section 5.5 of [RFC5082]. Consequently, any LDP method or feature (such as LDP IGP Synchronization [RFC5443] or LDP Session Protection [LDP-SPROT]) that relies on multi-hop LDP peering sessions would not work with GTSM and will require (statically or dynamically) disabling the GTSM capability.…”
Section: Scopementioning
confidence: 99%
“…The Generalized TTL Security Mechanism (GTSM) [RFC5082] is a mechanism based on IPv4 Time To Live (TTL) or IPv6 Hop Limit value verification so as to provide a simple and reasonably robust defense from infrastructure attacks using forged protocol packets from outside the network. GTSM can be applied to any protocol peering session that is established between routers that are adjacent.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…To prevent spoofing attacks, the TRILL hop count of a received session is checked [RFC5082]. For a single-hop session, if the hop count is less than 0x3F and the RBridge Channel Header MH flag is zero, the packet is discarded.…”
Section: Bfd Over Trillmentioning
confidence: 99%