--- 1/draft-ietf-bfd-multihop-04.txt 2007-03-08 00:12:26.000000000 +0100 +++ 2/draft-ietf-bfd-multihop-05.txt 2007-03-08 00:12:26.000000000 +0100 @@ -1,19 +1,19 @@ Network Working Group D. Katz Internet Draft Juniper Networks D. Ward Cisco Systems -Expires: December, 2006 June, 2006 +Expires: September, 2007 March, 2007 BFD for Multihop Paths - draft-ietf-bfd-multihop-04.txt + draft-ietf-bfd-multihop-05.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -24,24 +24,20 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html -Copyright Notice - - Copyright (C) The Internet Society (2006). All Rights Reserved. - Abstract This document describes the use of the Bidirectional Forwarding Detection protocol (BFD) over multihop paths, including unidirectional links. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this @@ -163,27 +159,27 @@ 5. Authentication By their nature, multihop paths expose BFD to spoofing. Implementations of BFD SHOULD utilize authentication over multihop paths to help mitigate denial-of-service attacks. Normative References [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding Detection", - draft-ietf-bfd-base-05.txt, June, 2006. + draft-ietf-bfd-base-06.txt, March, 2007. [BFD-1HOP] Katz, D., and Ward, D., "BFD for IPv4 and IPv6 (Single - Hop)", draft-ietf-bfd-v4v6-1hop-05.txt, June, 2006. + Hop)", draft-ietf-bfd-v4v6-1hop-06.txt, March, 2007. [BFD-MPLS] Aggarwal, R., and Kompella, K., "BFD for MPLS LSPs", - draft-ietf-bfd-mpls-03.txt, June, 2006. + draft-ietf-bfd-mpls-04.txt, March, 2007. [KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [OSPFv2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPFv3] Coltun, R., et al, "OSPF for IPv6", RFC 2740, December 1999. Security Considerations @@ -205,23 +201,22 @@ Dave Ward Cisco Systems 170 W. Tasman Dr. San Jose, CA 95134 USA Phone: +1-408-526-4000 Email: dward@cisco.com Changes from the previous draft - The only substantive change was the addition of the assigned UDP port - number for use with this protocol. All other changes are purely - editorial in nature. + This is a reissue of the previous version of the draft. There are + only minor editorial changes. IPR Disclaimer The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be @@ -235,30 +230,30 @@ http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. Full Copyright Notice - Copyright (C) The Internet Society (2006). + Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS - OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET - ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, - INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE - INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED + OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND + THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS + OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF + THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. - This document expires in December, 2006. + This document expires in September, 2007.