RFC 5082 on The Generalized TTL Security Mechanism (GTSM)
rfc-editor@rfc-editor.org Wed, 31 October 2007 22:53 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InMQx-0007Mq-1z; Wed, 31 Oct 2007 18:53:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InMQs-0007K7-N2; Wed, 31 Oct 2007 18:53:06 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InMQs-0004Yt-8Y; Wed, 31 Oct 2007 18:53:06 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id E83A0E9EE0; Wed, 31 Oct 2007 15:53:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20071031225305.E83A0E9EE0@bosco.isi.edu>
Date: Wed, 31 Oct 2007 15:53:05 -0700
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: rtgwg@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 5082 on The Generalized TTL Security Mechanism (GTSM)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
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@umbc.edu, heas@shrubbery.net, dmm@1-4-5.net, psavola@funet.fi, cpignata@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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions tlistinfo/ietf-announce