draft-ietf-bfd-multipoint-06.txt   draft-ietf-bfd-multipoint-07.txt 
Internet Engineering Task Force D. Katz Internet Engineering Task Force D. Katz
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track D. Ward Intended status: Standards Track D. Ward
Expires: November 7, 2015 Cisco Systems Expires: February 19, 2016 Cisco Systems
S. Pallagatti, Ed. S. Pallagatti, Ed.
Juniper Networks Juniper Networks
May 6, 2015 August 18, 2015
BFD for Multipoint Networks BFD for Multipoint Networks
draft-ietf-bfd-multipoint-06 draft-ietf-bfd-multipoint-07
Abstract Abstract
This document describes extensions to the Bidirectional Forwarding This document describes extensions to the Bidirectional Forwarding
Detection (BFD) protocol for its use in multipoint and multicast Detection (BFD) protocol for its use in multipoint and multicast
networks. Comments on this draft should be directed to rtg- networks. Comments on this draft should be directed to rtg-
bfd@ietf.org. bfd@ietf.org.
Requirements Language Requirements Language
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 7, 2015. This Internet-Draft will expire on February 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 4 4. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Multipoint BFD Control Packets . . . . . . . . . . . . . 4 4.1. Multipoint BFD Control Packets . . . . . . . . . . . . . 4
4.2. Session Model . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Session Model . . . . . . . . . . . . . . . . . . . . . . 4
4.3. Session Failure Semantics . . . . . . . . . . . . . . . . 5 4.3. Session Failure Semantics . . . . . . . . . . . . . . . . 5
4.4. State Variables . . . . . . . . . . . . . . . . . . . . . 5 4.4. State Variables . . . . . . . . . . . . . . . . . . . . . 5
4.4.1. New State Variables . . . . . . . . . . . . . . . . . 5 4.4.1. New State Variables . . . . . . . . . . . . . . . . . 5
4.4.2. State Variable Initialization and Maintenance . . . . 6 4.4.2. State Variable Initialization and Maintenance . . . . 6
4.5. State Machine . . . . . . . . . . . . . . . . . . . . . . 6 4.5. State Machine . . . . . . . . . . . . . . . . . . . . . . 6
4.6. Session Establishment . . . . . . . . . . . . . . . . . . 7 4.6. Session Establishment . . . . . . . . . . . . . . . . . . 7
4.7. Discriminators and Packet Demultiplexing . . . . . . . . 7 4.7. Discriminators and Packet Demultiplexing . . . . . . . . 7
4.8. Packet consumption on tails . . . . . . . . . . . . . . . 7 4.8. Packet consumption on tails . . . . . . . . . . . . . . . 8
4.9. Bringing Up and Shutting Down Multipoint BFD Service . . 8 4.9. Bringing Up and Shutting Down Multipoint BFD Service . . 8
4.10. Timer Manipulation . . . . . . . . . . . . . . . . . . . 8 4.10. Timer Manipulation . . . . . . . . . . . . . . . . . . . 8
4.11. Detection Times . . . . . . . . . . . . . . . . . . . . . 9 4.11. Detection Times . . . . . . . . . . . . . . . . . . . . . 9
4.12. State Maintenance for Down/AdminDown Sessions . . . . . . 9 4.12. State Maintenance for Down/AdminDown Sessions . . . . . . 9
4.12.1. MultipointHead Sessions . . . . . . . . . . . . . . 9 4.12.1. MultipointHead Sessions . . . . . . . . . . . . . . 9
4.12.2. MultipointTail Sessions . . . . . . . . . . . . . . 9 4.12.2. MultipointTail Sessions . . . . . . . . . . . . . . 9
4.13. Base Specification Text Replacement . . . . . . . . . . . 10 4.13. Base Specification Text Replacement . . . . . . . . . . . 10
4.13.1. Reception of BFD Control Packets . . . . . . . . . . 10 4.13.1. Reception of BFD Control Packets . . . . . . . . . . 10
4.13.2. Demultiplexing BFD Control Packets . . . . . . . . . 12 4.13.2. Demultiplexing BFD Control Packets . . . . . . . . . 12
4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 13 4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 13
5. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 16 5. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
9. Normative References . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
10. Normative References . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
The Bidirectional Forwarding Detection protocol [RFC5880] specifies a The Bidirectional Forwarding Detection protocol [RFC5880] specifies a
method for verifying unicast connectivity between a pair of systems. method for verifying unicast connectivity between a pair of systems.
This document defines a method for using BFD to provide verification This document defines a method for using BFD to provide verification
of multipoint or multicast connectivity between a multipoint sender of multipoint or multicast connectivity between a multipoint sender
(the "head") and a set of one or more multipoint receivers (the (the "head") and a set of one or more multipoint receivers (the
"tails"). "tails").
skipping to change at page 17, line 11 skipping to change at page 17, line 16
number of MultipointTail sessions that can be created, with the number of MultipointTail sessions that can be created, with the
upper bound potentially being computed based on the number of upper bound potentially being computed based on the number of
multicast streams that the system is expecting. multicast streams that the system is expecting.
8. Contributors 8. Contributors
Rahul Aggarwal of Juniper Networks and George Swallow of Cisco Rahul Aggarwal of Juniper Networks and George Swallow of Cisco
Systems provided the initial idea for this specification and Systems provided the initial idea for this specification and
contributed to its development. contributed to its development.
9. Normative References 9. Acknowledgements
Authors would also like to thank Nobo Akiya, Vengada Prasad Govindan,
Jeff Haas, Wim Henderickx, Gregory Mirsky and Mingui Zhang who have
greatly contributed to this document.
10. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<http://www.rfc-editor.org/info/rfc5880>.
Authors' Addresses Authors' Addresses
Dave Katz Dave Katz
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, California 94089-1206 Sunnyvale, California 94089-1206
USA USA
Email: dkatz@juniper.net Email: dkatz@juniper.net
 End of changes. 10 change blocks. 
10 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/