[rfc-dist] RFC 5082 on The Generalized TTL Security Mechanism (GTSM)

[rfc-editor at rfc-editor.org ([e-mail])]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5082

        Title:      The Generalized TTL Security Mechanism 
                    (GTSM) 
        Author:     V. Gill, J. Heasley,
                    D. Meyer, P. Savola, Ed.,
                    C. Pignataro
        Status:     Standards Track
        Date:       October 2007
        Mailbox:    vijay at umbc.edu, 
                    heas at shrubbery.net, 
                    dmm at 1-4-5.net,  psavola at funet.fi, 
                    cpignata at cisco.com
        Pages:      16
        Characters: 36579
        Obsoletes:  RFC3682
        See-Also:   

        I-D Tag:    draft-ietf-rtgwg-rfc3682bis-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5082.txt

The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)
to verify whether the packet was originated by an adjacent node on a
connected link has been used in many recent protocols.  This document
generalizes this technique.  This document obsoletes Experimental RFC
3682.  [STANDARDS TRACK]

This document is a product of the Routing Area Working Group
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...