| draft-ietf-bfd-multihop-07.txt | draft-ietf-bfd-multihop-08.txt | |||
|---|---|---|---|---|
| Network Working Group D. Katz | Network Working Group D. Katz | |||
| Internet Draft Juniper Networks | Internet Draft Juniper Networks | |||
| Intended status: Proposed Standard D. Ward | Intended status: Proposed Standard D. Ward | |||
| Cisco Systems | Cisco Systems | |||
| Expires: August, 2009 February 5, 2009 | Expires: April, 2010 October 16, 2009 | |||
| BFD for Multihop Paths | BFD for Multihop Paths | |||
| draft-ietf-bfd-multihop-07.txt | draft-ietf-bfd-multihop-08.txt | |||
| Status of this Memo | Status of this Memo | |||
| This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 1, line 43 | skipping to change at page 1, line 43 | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | 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 | Abstract | |||
| This document describes the use of the Bidirectional Forwarding | This document describes the use of the Bidirectional Forwarding | |||
| Detection protocol (BFD) over multihop paths, including | Detection protocol (BFD) over multihop paths, including | |||
| unidirectional links. | unidirectional links. | |||
| Conventions used in this document | Conventions used in this document | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| skipping to change at page 5, line 22 | skipping to change at page 5, line 22 | |||
| 5. Authentication | 5. Authentication | |||
| By their nature, multihop paths expose BFD to spoofing. As the | By their nature, multihop paths expose BFD to spoofing. As the | |||
| number of hops increase, the exposure to attack grows. As such, | number of hops increase, the exposure to attack grows. As such, | |||
| implementations of BFD SHOULD utilize cryptographic authentication | implementations of BFD SHOULD utilize cryptographic authentication | |||
| over multihop paths to help mitigate denial-of-service attacks. | over multihop paths to help mitigate denial-of-service attacks. | |||
| Normative References | Normative References | |||
| [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding Detection", | [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 | [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 | [KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", RFC 2119, March 1997. | Requirement Levels", RFC 2119, March 1997. | |||
| Informative References | Informative References | |||
| [BFD-MPLS] Aggarwal, R., Kompella, K., et al, "BFD for MPLS LSPs", | [BFD-MPLS] Aggarwal, R., Kompella, K., et al, "BFD for MPLS LSPs", | |||
| draft-ietf-bfd-mpls-07.txt, June, 2008. | draft-ietf-bfd-mpls-07.txt, June, 2008. | |||
| [OSPFv2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. | [OSPFv2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. | |||
| skipping to change at page 6, line 16 | skipping to change at page 6, line 16 | |||
| As the number of hops increases, BFD becomes further exposed to | As the number of hops increases, BFD becomes further exposed to | |||
| attack. The use of strong forms of authentication is strongly | attack. The use of strong forms of authentication is strongly | |||
| encouraged. | encouraged. | |||
| No additional security issues are raised in this document beyond | No additional security issues are raised in this document beyond | |||
| those that exist in the referenced BFD documents. | those that exist in the referenced BFD documents. | |||
| IANA Considerations | IANA Considerations | |||
| This document has no actions for IANA. | Port 4784 has been assigned by IANA for use with this protocol. | |||
| Authors' Addresses | Authors' Addresses | |||
| Dave Katz | Dave Katz | |||
| Juniper Networks | Juniper Networks | |||
| 1194 N. Mathilda Ave. | 1194 N. Mathilda Ave. | |||
| Sunnyvale, California 94089-1206 USA | Sunnyvale, California 94089-1206 USA | |||
| Phone: +1-408-745-2000 | Phone: +1-408-745-2000 | |||
| Email: dkatz@juniper.net | Email: dkatz@juniper.net | |||
| Dave Ward | Dave Ward | |||
| Cisco Systems | Cisco Systems | |||
| 170 W. Tasman Dr. | 170 W. Tasman Dr. | |||
| San Jose, CA 95134 USA | San Jose, CA 95134 USA | |||
| Phone: +1-408-526-4000 | Phone: +1-408-526-4000 | |||
| Email: dward@cisco.com | Email: dward@cisco.com | |||
| Changes from the previous draft | Changes from the previous draft | |||
| A note was added that the Echo function is not available for multihop | The fact that the port number was assigned by IANA was added. All | |||
| BFD. All other changes are editorial in nature. | other changes are editorial in nature. | |||
| This document expires in August, 2009. | This document expires in April, 2010. | |||
| End of changes. 8 change blocks. | ||||
| 8 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||