draft-ietf-rtgwg-rfc3682bis-04.txt   draft-ietf-rtgwg-rfc3682bis-05.txt 
INTERNET-DRAFT V. Gill INTERNET-DRAFT V. Gill
draft-ietf-rtgwg-rfc3682bis-04.txt J. Heasley draft-ietf-rtgwg-rfc3682bis-05.txt J. Heasley
D. Meyer D. Meyer
Category Proposed Standard Category Proposed Standard
Obsoletes: RFC 3682 Obsoletes: RFC 3682
Expires: March 2005 September 2004
Expires: October 2005 April 2005
The Generalized TTL Security Mechanism (GTSM) The Generalized TTL Security Mechanism (GTSM)
<draft-ietf-rtgwg-rfc3682bis-04.txt> <draft-ietf-rtgwg-rfc3682bis-05.txt>
Status of this Memo Status of this Memo
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all This document is an Internet-Draft and is subject to all
provisions of section 3 of RFC 3667 [RFC3667]. By submitting provisions of Section 3 of RFC 3667. By submitting this
this Internet-Draft, each author represents that any Internet-Draft, each author represents that any applicable patent
applicable patent or other IPR claims of which he or she is or other IPR claims of which he or she is aware have been or will
aware have been or will be disclosed, and any of which he or be disclosed, and any of which he or she become aware will be
she become aware will be disclosed, in accordance with RFC disclosed, in accordance with RFC 3668.
3668 [RFC3668].
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet Engineering
Engineering Task Force (IETF), its areas, and its working Task Force (IETF), its areas, and its working groups. Note that
groups. Note that other groups may also distribute working other groups may also distribute working documents as Internet-Drafts.
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use documents at any time. It is inappropriate to use
Internet-Drafts as reference material or to cite them other Internet-Drafts as reference material or to cite them other than
than as "work in progress." as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed The list of Internet-Draft Shadow Directories can be accessed at
at http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document is a product of the RTGWG WG. Comments should be This document is a product of the RTGWG WG. Comments should be
addressed to the authors, or the mailing list at rtgwg@ietf.org. addressed to the authors, or the mailing list at rtgwg@ietf.org.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)
to protect a protocol stack from CPU-utilization based attacks has to protect a protocol stack from CPU-utilization based attacks has
been proposed in many settings (see for example, RFC 2461). This been proposed in many settings (see for example, RFC 2461). This
document generalizes these techniques for use by other protocols such document generalizes these techniques for use by other protocols such
as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP), as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP),
Bidirectional Forwarding Detection, and Label Distribution Protocol Bidirectional Forwarding Detection, and Label Distribution Protocol
(LDP) (RFC 3036). While the Generalized TTL Security Mechanism (GTSM) (LDP) (RFC 3036). While the Generalized TTL Security Mechanism (GTSM)
skipping to change at page 14, line 8 skipping to change at page 14, line 8
[SBGP2] Kent, S., C. Lynn, J. Mikkelson, and K. Seo, [SBGP2] Kent, S., C. Lynn, J. Mikkelson, and K. Seo,
"Secure Border Gateway Protocol (S-BGP) -- Real "Secure Border Gateway Protocol (S-BGP) -- Real
World Performance and Deployment Issues", World Performance and Deployment Issues",
Proceedings of the IEEE Network and Distributed Proceedings of the IEEE Network and Distributed
System Security Symposium, February, 2000. System Security Symposium, February, 2000.
8.2. Informative References 8.2. Informative References
[BFD] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection", draft-ietf-bfd-base-00.txt, Work in Detection", draft-ietf-bfd-base-02.txt, Work in
Progress. Progress.
[PEERING] Empirical data gathered from the Sprint and AOL [PEERING] Empirical data gathered from the Sprint and AOL
backbones, October, 2002. backbones, October, 2002.
[RFC2434] Narten, T., and H. Alvestrand, "Guidelines for [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for
Writing an IANA Considerations Section in RFCs", Writing an IANA Considerations Section in RFCs",
BCP 26, RFC 2434, October 1998. BCP 26, RFC 2434, October 1998.
[RFC3618] Meyer, D. and W. Fenner, Eds., "The Multicast [RFC3618] Meyer, D. and W. Fenner, Eds., "The Multicast
skipping to change at page 15, line 41 skipping to change at page 15, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/