draft-ietf-bfd-multipoint-13.txt   draft-ietf-bfd-multipoint-14.txt 
Internet Engineering Task Force D. Katz Internet Engineering Task Force D. Katz
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Updates: 5880, 7880 (if approved) D. Ward Updates: 5880, 7880 (if approved) D. Ward
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 3, 2018 S. Pallagatti, Ed. Expires: August 25, 2018 S. Pallagatti, Ed.
Individual contributor Individual contributor
G. Mirsky, Ed. G. Mirsky, Ed.
ZTE Corp. ZTE Corp.
January 30, 2018 February 21, 2018
BFD for Multipoint Networks BFD for Multipoint Networks
draft-ietf-bfd-multipoint-13 draft-ietf-bfd-multipoint-14
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. networks.
Requirements Language Requirements Language
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 1, line 45 skipping to change at page 1, line 45
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 3, 2018. This Internet-Draft will expire on August 25, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 41 skipping to change at page 2, line 41
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 . . . . . . . . . . . . . . . . . . 6 4.6. Session Establishment . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . 10
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 . . . . . . . . . 13
4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 13 4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 14
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
10. Normative References . . . . . . . . . . . . . . . . . . . . 17 10. Normative References . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
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 7, line 46 skipping to change at page 7, line 46
document. document.
Note that, unlike point-to-point sessions, the My Discriminator value Note that, unlike point-to-point sessions, the My Discriminator value
on MultipointHead session MUST NOT be changed during the life of a on MultipointHead session MUST NOT be changed during the life of a
session. This is a side effect of the more complex demultiplexing session. This is a side effect of the more complex demultiplexing
scheme. scheme.
4.8. Packet consumption on tails 4.8. Packet consumption on tails
BFD packets received on tails for an IP multicast group MUST be BFD packets received on tails for an IP multicast group MUST be
consumed by tails and MUST NOT be forwarded to receivers. Session of consumed by tails and MUST NOT be forwarded to receivers. Node with
type MultipointTail MUST identify the packet as BFD with the help of the BFD session of type MultipointTail MUST identify packet received
destination UDP port number "3784" on IP multipoint path. on an IP multipoint path as BFD control packet if the destination UDP
port value equals 3784.
For multipoint LSPs, when IP/UDP encapsulation of BFD control packets For multipoint LSPs, when IP/UDP encapsulation of BFD control packets
is used, MultipointTail MUST use destination UDP port "3784" and is used, MultipointTail MUST expect destination UDP port 3784.
"127.0.0.0/8" range for IPv4 or "0:0:0:0:0:FFFF:7F00:0/104" range for Destination IP address of BFD control packet MUST be in 127.0.0.0/8
IPv6 ([RFC8029]). Packets identified as BFD packets MUST be consumed range for IPv4 or in 0:0:0:0:0:FFFF:7F00:0/104 range for IPv6. The
by MultipointTail and demultiplex as described in Section 4.13.2. use of these destination addresses is consistent with the
Use of other types of encapsulation for multipoint LSP is outside the explanations and usage in [RFC8029]. Packets identified as BFD
scope of this document. packets MUST be consumed by MultipointTail and demultiplex as
described in Section 4.13.2. Use of other types of encapsulation of
the BFD control message over multipoint LSP is outside the scope of
this document.
4.9. Bringing Up and Shutting Down Multipoint BFD Service 4.9. Bringing Up and Shutting Down Multipoint BFD Service
Because there is no three-way handshake in Multipoint BFD, a newly Because there is no three-way handshake in Multipoint BFD, a newly
started head (that does not have any previous state information started head (that does not have any previous state information
available) SHOULD start with bfd.SessionState set to Down and with available) SHOULD start with bfd.SessionState set to Down and with
bfd.RequiredMinRxInterval set to zero in the MultipointHead session. bfd.RequiredMinRxInterval set to zero in the MultipointHead session.
The session SHOULD remain in this state for a time equal to The session SHOULD remain in this state for a time equal to
(bfd.DesiredMinTxInterval * bfd.DetectMult). This will ensure that (bfd.DesiredMinTxInterval * bfd.DetectMult). This will ensure that
all MultipointTail sessions are reset (so long as the restarted head all MultipointTail sessions are reset (so long as the restarted head
skipping to change at page 11, line 21 skipping to change at page 11, line 32
transmission of Echo packets, if any, MUST cease. transmission of Echo packets, if any, MUST cease.
If a Poll Sequence is being transmitted by the local system and If a Poll Sequence is being transmitted by the local system and
the Final (F) bit in the received packet is set, the Poll Sequence the Final (F) bit in the received packet is set, the Poll Sequence
MUST be terminated. MUST be terminated.
If bfd.SessionType is PointToPoint, update the transmit interval If bfd.SessionType is PointToPoint, update the transmit interval
as described in [RFC5880] section 6.8.2. as described in [RFC5880] section 6.8.2.
If bfd.SessionType is PointToPoint, update the Detection Time as If bfd.SessionType is PointToPoint, update the Detection Time as
described in [RFC5880] section 6.8.4. Otherwise, update the described in section 6.8.4 of [RFC5880]. If bfd.SessionType is
Detection Time as described in Section 4.11 above. MultipointTail, then update the Detection Time as the product of
the last received values of Desired Min TX Interval and Detect
Mult, as described in Section 4.11 of this specification.
If bfd.SessionState is AdminDown If bfd.SessionState is AdminDown
Discard the packet Discard the packet
If received state is AdminDown If received state is AdminDown
If bfd.SessionState is not Down If bfd.SessionState is not Down
Set bfd.LocalDiag to 3 (Neighbor signaled session down) Set bfd.LocalDiag to 3 (Neighbor signaled session down)
 End of changes. 10 change blocks. 
19 lines changed or deleted 25 lines changed or added

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