A new Request for Comments is now available in online RFC libraries.
Title: The Generalized TTL Security Mechanism
Author: V. Gill, J. Heasley,
D. Meyer, P. Savola, Ed.,
Status: Standards Track
Date: October 2007
Mailbox: [email protected],
[email protected], [email protected],
I-D Tag: draft-ietf-rtgwg-rfc3682bis-10.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 [email protected] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body
help: ways_to_get_rfcs. For example:
To: [email protected]
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
[email protected] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
rtgwg mailing list