--- 1/draft-ietf-bfd-multihop-07.txt 2009-10-16 19:12:06.000000000 +0200 +++ 2/draft-ietf-bfd-multihop-08.txt 2009-10-16 19:12:06.000000000 +0200 @@ -1,19 +1,19 @@ Network Working Group D. Katz Internet Draft Juniper Networks Intended status: Proposed Standard D. Ward Cisco Systems -Expires: August, 2009 February 5, 2009 +Expires: April, 2010 October 16, 2009 BFD for Multihop Paths - draft-ietf-bfd-multihop-07.txt + draft-ietf-bfd-multihop-08.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -32,21 +32,24 @@ Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect - to this document. + to this document. Code Components extracted from this document must + include Simplified BSD License text as described in Section 4.e of + the Trust Legal Provisions and are provided without warranty as + described in the BSD License. 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", @@ -174,24 +177,24 @@ 5. Authentication By their nature, multihop paths expose BFD to spoofing. As the number of hops increase, the exposure to attack grows. As such, implementations of BFD SHOULD utilize cryptographic 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-09.txt, February, 2009. + draft-ietf-bfd-base-10.txt, October, 2009. [BFD-1HOP] Katz, D., and Ward, D., "BFD for IPv4 and IPv6 (Single - Hop)", draft-ietf-bfd-v4v6-1hop-09.txt, February, 2009. + Hop)", draft-ietf-bfd-v4v6-1hop-10.txt, October, 2009. [KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. Informative References [BFD-MPLS] Aggarwal, R., Kompella, K., et al, "BFD for MPLS LSPs", draft-ietf-bfd-mpls-07.txt, June, 2008. [OSPFv2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. @@ -202,34 +205,34 @@ As the number of hops increases, BFD becomes further exposed to attack. The use of strong forms of authentication is strongly encouraged. No additional security issues are raised in this document beyond those that exist in the referenced BFD documents. IANA Considerations - This document has no actions for IANA. + Port 4784 has been assigned by IANA for use with this protocol. Authors' Addresses Dave Katz Juniper Networks 1194 N. Mathilda Ave. Sunnyvale, California 94089-1206 USA Phone: +1-408-745-2000 Email: dkatz@juniper.net 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 - A note was added that the Echo function is not available for multihop - BFD. All other changes are editorial in nature. + The fact that the port number was assigned by IANA was added. All + other changes are editorial in nature. -This document expires in August, 2009. +This document expires in April, 2010.