< draft-ietf-bfd-multipoint-12.txt		draft-ietf-bfd-multipoint-13.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: June 22, 2018 Cisco Systems		Expires: July 19, 2018 Cisco Systems
	S. Pallagatti, Ed.		S. Pallagatti, Ed.
	Individual contributor		Individual contributor
	G. Mirsky, Ed.		G. Mirsky, Ed.
	ZTE Corp.		ZTE Corp.
	December 19, 2017		January 15, 2018
	BFD for Multipoint Networks		BFD for Multipoint Networks
	draft-ietf-bfd-multipoint-12		draft-ietf-bfd-multipoint-13
	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 46 ¶		skipping to change at page 1, line 46 ¶
	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 June 22, 2018.		This Internet-Draft will expire on July 19, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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
	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
	skipping to change at page 2, line 30 ¶		skipping to change at page 2, line 30 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		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 . . . . . . . . . . . . . . . . . . . . . . 5		4.2. Session Model . . . . . . . . . . . . . . . . . . . . . . 5
	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 Variable . . . . . . . . . . . . . . . . . 5
	4.4.2. State Variable Initialization and Maintenance . . . . 6		4.4.2. New State Variable Values . . . . . . . . . . . . . . 6
			4.4.3. 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 . . . . . . . . . . . . . . . 8		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 . . . . . . . . . . . . . . . . . . . 9		4.10. Timer Manipulation . . . . . . . . . . . . . . . . . . . 9
	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 . . . . . . 10
	4.12.1. MultipointHead Sessions . . . . . . . . . . . . . . 10		4.12.1. MultipointHead Sessions . . . . . . . . . . . . . . 10
	4.12.2. MultipointTail Sessions . . . . . . . . . . . . . . 10		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 . . . . . . . . . 13		4.13.2. Demultiplexing BFD Control Packets . . . . . . . . . 13
	4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 14		4.13.3. Transmitting BFD Control Packets . . . . . . . . . . 14
	5. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 16		5. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 16
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 17		7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
	8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17		8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
	10. Normative References . . . . . . . . . . . . . . . . . . . . 17		10. Normative References . . . . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18		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.
	skipping to change at page 5, line 39 ¶		skipping to change at page 5, line 41 ¶
	If a MultipointTail session fails, it means that the tail definitely		If a MultipointTail session fails, it means that the tail definitely
	has lost contact with the head (or the head has been administratively		has lost contact with the head (or the head has been administratively
	disabled) and the tail should take appropriate action.		disabled) and the tail should take appropriate action.
	4.4. State Variables		4.4. State Variables
	Multipoint BFD introduces some new state variables, and modifies the		Multipoint BFD introduces some new state variables, and modifies the
	usage of a few existing ones.		usage of a few existing ones.
	4.4.1. New State Variables		4.4.1. New State Variable
	A number of state variables and their values are added to the base		A new state variable is added to the base BFD [RFC5880] specification
	BFD [RFC5880] and base S-BFD [RFC7880] specifications in support of		in support of Multipoint BFD.
	Multipoint BFD.
			bfd.SilentTail
			Always set to 1, a tail will never transmit any BFD Control
			packets to the head under any circumstances. Setting to 0 is
			outside the scope of this document.
			This variable is only pertinent when bfd.SessionType is
			MultipointTail.
			4.4.2. New State Variable Values
			A number of state variable values are added to the base BFD [RFC5880]
			and base S-BFD [RFC7880] specifications in support of Multipoint BFD.
	bfd.SessionType		bfd.SessionType
	The type of this session as defined in [RFC7880]. Newly added		The type of this session as defined in [RFC7880]. Newly added
	values are:		values are:
	PointToPoint: Classic point-to-point BFD.		PointToPoint: Classic point-to-point BFD.
	MultipointHead: A session on the head responsible for the		MultipointHead: A session on the head responsible for the
	periodic transmission of multipoint BFD Control packets		periodic transmission of multipoint BFD Control packets
	along the multipoint path.		along the multipoint path.
	MultipointTail: A multipoint session on a tail.		MultipointTail: A multipoint session on a tail.
	This variable MUST be initialized to the appropriate type when		This variable MUST be initialized to the appropriate type when
	the session is created, according to the rules in Section 4.13		the session is created, according to the rules in Section 4.13
	bfd.SilentTail		4.4.3. State Variable Initialization and Maintenance
	Always set to 1, a tail will never transmit any BFD Control
	packets to the head under any circumstances. Setting to 0 is
	outside the scope of this document.
	This variable is only pertinent when bfd.SessionType is
	MultipointTail.
	4.4.2. State Variable Initialization and Maintenance
	Some state variables defined in section 6.8.1 of the [RFC5880] needs		Some state variables defined in section 6.8.1 of the [RFC5880] needs
	to be initialized or manipulated differently depending on the session		to be initialized or manipulated differently depending on the session
	type.		type.
	bfd.RequiredMinRxInterval		bfd.RequiredMinRxInterval
	This variable MUST be set to 0 for session type MultipointHead.		This variable MUST be set to 0 for session type MultipointHead.
	bfd.DemandMode		bfd.DemandMode
End of changes. 11 change blocks.
	23 lines changed or deleted		28 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/