< draft-hu-bier-bfd-06.txt		draft-hu-bier-bfd-07.txt >
	BIER WG Quan Xiong		BIER WG Quan Xiong
	Internet-Draft Greg Mirsky		Internet-Draft Greg Mirsky
	Intended status: Standards Track ZTE Corporation		Intended status: Standards Track ZTE Corporation
	Expires: October 31, 2020 Fangwei Hu		Expires: January 11, 2021 Fangwei Hu
	Individual		Individual
	Chang Liu		Chang Liu
	China Unicom		China Unicom
	April 29, 2020		July 10, 2020
	BIER BFD		BIER BFD
	draft-hu-bier-bfd-06.txt		draft-hu-bier-bfd-07.txt
	Abstract		Abstract
	Point to multipoint (P2MP) BFD is designed to verify multipoint		Point to multipoint (P2MP) BFD is designed to verify multipoint
	connectivity. This document specifies the application of P2MP BFD in		connectivity. This document specifies the application of P2MP BFD in
	BIER network.		BIER network.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 October 31, 2020.		This Internet-Draft will expire on January 11, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 21 ¶		skipping to change at page 2, line 21 ¶
	2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3		2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
	3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3		3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3
	4. BIER BFD Session Bootstrapping . . . . . . . . . . . . . . . 3		4. BIER BFD Session Bootstrapping . . . . . . . . . . . . . . . 3
	4.1. BIER OAM Bootstrapping . . . . . . . . . . . . . . . . . 4		4.1. BIER OAM Bootstrapping . . . . . . . . . . . . . . . . . 4
	4.2. IGP protocol Bootstrapping . . . . . . . . . . . . . . . 4		4.2. IGP protocol Bootstrapping . . . . . . . . . . . . . . . 4
	4.2.1. IS-IS extension for BIER BFD . . . . . . . . . . . . 4		4.2.1. IS-IS extension for BIER BFD . . . . . . . . . . . . 4
	4.2.2. OSPF extension for BIER BFD . . . . . . . . . . . . . 5		4.2.2. OSPF extension for BIER BFD . . . . . . . . . . . . . 5
	5. Discriminators and Packet Demultiplexing . . . . . . . . . . 6		5. Discriminators and Packet Demultiplexing . . . . . . . . . . 6
	6. Active Tail in BIER BFD . . . . . . . . . . . . . . . . . . . 6		6. Active Tail in BIER BFD . . . . . . . . . . . . . . . . . . . 6
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 7		6.1. Unsolicited Head Notification Mode . . . . . . . . . . . 7
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
	9.1. BIER OAM Message Type . . . . . . . . . . . . . . . . . . 7		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	9.2. BFD Discriminator TLV . . . . . . . . . . . . . . . . . . 7		9.1. BIER OAM Message Type . . . . . . . . . . . . . . . . . . 8
			9.2. BFD Discriminator TLV . . . . . . . . . . . . . . . . . . 8
	9.3. BIER BFD Sub-sub-TLV . . . . . . . . . . . . . . . . . . 8		9.3. BIER BFD Sub-sub-TLV . . . . . . . . . . . . . . . . . . 8
	9.4. BIER BFD Sub-TLV . . . . . . . . . . . . . . . . . . . . 8		9.4. BIER BFD Sub-TLV . . . . . . . . . . . . . . . . . . . . 9
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	10.1. Normative References . . . . . . . . . . . . . . . . . . 8		10.1. Normative References . . . . . . . . . . . . . . . . . . 9
	10.2. Informative References . . . . . . . . . . . . . . . . . 9		10.2. Informative References . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	Bit Index Explicit Replication (BIER) [RFC8279] provides forwarding		Bit Index Explicit Replication (BIER) [RFC8279] provides the
	of multicast data packets through a multicast domain. It does so		forwarding of multicast data packets through a multicast domain. It
	without requiring any explicit tree-building protocol and without		does so without requiring any explicit tree-building protocol and
	requiring intermediate nodes to maintain any per-flow state.		without requiring intermediate nodes to maintain any per-flow state.
	[RFC8562] defines a method of using Bidirectional Forwarding		[RFC8562] defines a method of using Bidirectional Forwarding
	Detection (BFD) to monitor and detect unicast failures between the		Detection (BFD) to monitor and detect unicast failures between the
	sender (head) and one or more receivers (tails) in multipoint or		sender (head) and one or more receivers (tails) in multipoint or
	multicast networks. [RFC8563] describes active tail extensions to		multicast networks. [RFC8563] describes active tail extensions to
	the BFD protocol for multipoint networks.		the BFD protocol for multipoint networks.
	This document describes the procedures for using such mode of BFD		This document describes the procedures for using such mode of BFD
	protocol to monitor connectivity between a multipoint sender, Bit-		protocol to monitor connectivity between a multipoint sender, Bit-
	Forwarding Ingress Router (BFIR), and a set of one or more multipoint		Forwarding Ingress Router (BFIR), and a set of one or more multipoint
	receivers,Bit-Forwarding Egress Routers (BFERs). The BIER BFD only		receivers, Bit-Forwarding Egress Routers (BFERs). The BIER BFD only
	supports the unidirectional multicast. This document defines the use		supports the unidirectional multicast. This document defines the use
	of P2MP BFD as per [RFC8562], and active tail as per [RFC8563] for		of P2MP BFD as per [RFC8562], and active tail as per [RFC8563] for
	BIER-specific domain.		BIER-specific domain.
	2. Conventions used in this document		2. Conventions used in this document
	2.1. Terminology		2.1. Terminology
	This document uses the acronyms defined in [RFC8279] along with the		This document uses the acronyms defined in [RFC8279] along with the
	following:		following:
	skipping to change at page 3, line 31 ¶		skipping to change at page 3, line 31 ¶
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	3. BIER BFD Encapsulation		3. BIER BFD Encapsulation
	BIER BFD encapsulation uses the BIER OAM packet format defined in		BIER BFD encapsulation uses the BIER OAM packet format defined in
	[I-D.ietf-bier-ping]. The value of the Messasge Type field MUST be		[I-D.ietf-bier-ping]. The value of the Message Type field MUST be
	set to BIER BFD (TBD1 by IANA ). BFD Control Packet, defined in		set to BIER BFD (TBD1 by IANA ). BFD Control Packet, defined in
	Section 4 [RFC5880] immediately follows the BIER OAM header. The		Section 4 [RFC5880] immediately follows the BIER OAM header. The
	operation of Multipoint BFD with the BFD Control Packet is described		operation of Multipoint BFD with the BFD Control Packet is described
	in [RFC8562].		in [RFC8562].
	4. BIER BFD Session Bootstrapping		4. BIER BFD Session Bootstrapping
	As defined in [RFC8562], BIER BFD session MAY be established to		As defined in [RFC8562], BIER BFD session MAY be established to
	monitor the state of the multipoint path. The BIER BFD session could		monitor the state of the multipoint path. The BIER BFD session could
	be created for each multipoint path and the set of BFERs over which		be created for each multipoint path and the set of BFERs over which
	the BFIR wishes to run BIER BFD. The BFIR MUST advertise the BFD		the BFIR is requested to run BIER BFD. The BFIR MUST advertise the
	Discriminator along with the corresponding multipoint path to the set		multipoint path and the value of My Discriminator associated with the
	of BFERs. Bootstrapping a BIER BFD session MAY use BIER OAM message		path to the set of BFERs. Bootstrapping a BIER BFD session MAY use
	section 4.1 or the control plane section 4.2.		BIER OAM message Section 4.1 or the control plane Section 4.2.
	The BIER BFD bootstrapping MUST be repeated when the value of this		The BIER BFD bootstrapping MUST be repeated when the value of this
	discriminator being changed.		discriminator being changed.
	4.1. BIER OAM Bootstrapping		4.1. BIER OAM Bootstrapping
	The BIER OAM could be used for bootstrapping the BIER BFD session.		The BIER OAM could be used for bootstrapping the BIER BFD session.
	The BFIR sends the BIER OAM Echo request message carrying a BFD		The BFIR sends the BIER OAM Echo request message carrying a BFD
	discriminator TLV which immediately follows the Target SI-Bitstring		discriminator TLV which immediately follows the Target SI-Bitstring
	TLV (section 3.3.2 [I-D.ietf-bier-ping]).		TLV (section 3.3.2 [I-D.ietf-bier-ping]).
	The Target SI-Bitstring TLV MUST be used to carry the set of BFER		The Target SI-Bitstring TLV MUST be used to carry the set of BFER
	information (including Sub-domain-id, Set ID, BS Len, Bitstring) for		information (including Sub-domain-id, Set ID, BS Len, Bitstring) for
	the purpose of session establishment.		the purpose of the session establishment.
	The BFD discriminator TLV is a new TLV for BIER OAM TLV with the type		The BFD discriminator TLV is a new TLV for BIER OAM TLV with the type
	(TBD2 by IANA) and the length of 4. The value contains the 4-byte		(TBD2 by IANA) and the length of 4. The value contains the 4-byte
	local discriminator generated by BFIR for this session. This		local discriminator generated by BFIR for this session. This
	discriminator MUST subsequently be used as the My Discriminator field		discriminator MUST subsequently be used as the My Discriminator field
	in the BIER BFD session packets sent by BFIR. The format is as		in the BIER BFD session packets sent by BFIR. The format is as
	follows.		follows.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	skipping to change at page 4, line 36 ¶		skipping to change at page 4, line 36 ¶
	| Type=TBD2 | Length |		| Type=TBD2 | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| My Discriminator |		| My Discriminator |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: BFD discriminator TLV		Figure 1: BFD discriminator TLV
	4.2. IGP protocol Bootstrapping		4.2. IGP protocol Bootstrapping
	An alternative option to bootstrap the BIER BFD is to advertise the		An alternative option to bootstrap the BIER BFD is to advertise the
	BFD information in control plane. This document defines a new BIER		BFD information in the control plane. This document defines a new
	BFD Sub-sub-TLV carried in IS-IS and OSPF protocol.		BIER BFD Sub-sub-TLV carried in IS-IS and OSPF protocol.
	The BFIR generates the My Discriminator value for each multicast flow		The BFIR generates the My Discriminator value for each multicast flow
	and advertises it to the expecting BFERs which is indicated by the		and advertises it to the expecting BFERs which is indicated by the
	Bitstring which is carried in BIER BFD sub-sub-TLV. The		Bitstring which is carried in BIER BFD sub-sub-TLV. The
	corresponding BFERs SHOULD store the My Discriminator value for		corresponding BFERs SHOULD store the My Discriminator value for
	packet Demultiplexing.		packet Demultiplexing.
	4.2.1. IS-IS extension for BIER BFD		4.2.1. IS-IS extension for BIER BFD
	The new BIER BFD Sub-sub-TLV is carried within the BIER Info sub-TLV		The new BIER BFD Sub-sub-TLV is carried within the BIER Info sub-TLV
	skipping to change at page 5, line 32 ¶		skipping to change at page 5, line 32 ¶
	Type: TBD3 by IANA.		Type: TBD3 by IANA.
	Length: Length of the BIER BFD Sub-sub-TLV for IS-IS extension, in		Length: Length of the BIER BFD Sub-sub-TLV for IS-IS extension, in
	bytes.		bytes.
	My Discriminator: A unique, nonzero discriminator value generated by		My Discriminator: A unique, nonzero discriminator value generated by
	BFIR for each multipoint path.		BFIR for each multipoint path.
	The BitString field carries the set of BFR-IDs of BFER(s) that the		The BitString field carries the set of BFR-IDs of BFER(s) that the
	BFIR expects to establish BIER BFD session.		BFIR expects to establish the BIER BFD session.
	The BIFT-id represents a particular Bit Index Forwarding Table (BIFT)		The BIFT-id represents a particular Bit Index Forwarding Table (BIFT)
	as per [RFC8279].		as per [RFC8279].
	4.2.2. OSPF extension for BIER BFD		4.2.2. OSPF extension for BIER BFD
	The new BIER BFD Sub-TLV is a sub-TLV of the BIER Sub-TLV defined in		The new BIER BFD Sub-TLV is a sub-TLV of the BIER Sub-TLV defined in
	[RFC8444]. The format is as follows.		[RFC8444]. The format is as follows.
	0 1 2 3		0 1 2 3
	skipping to change at page 6, line 38 ¶		skipping to change at page 6, line 38 ¶
	5. Discriminators and Packet Demultiplexing		5. Discriminators and Packet Demultiplexing
	As defined in [RFC8562], the BFIR sends BFD Control packets over the		As defined in [RFC8562], the BFIR sends BFD Control packets over the
	multipoint path via the BIER BFD session with My Discriminator set to		multipoint path via the BIER BFD session with My Discriminator set to
	the value assigned by the BFIR and the value of the Your		the value assigned by the BFIR and the value of the Your
	Discriminator set to zero. The set of BFERs MUST demultiplex BFD		Discriminator set to zero. The set of BFERs MUST demultiplex BFD
	packets based on a combination of the source address, My		packets based on a combination of the source address, My
	Discriminator value. The source address is BFIR-id and BIER MPLS		Discriminator value. The source address is BFIR-id and BIER MPLS
	Label (MPLS network) or BFIR-id and BIFT-id (Non-MPLS network) for		Label (MPLS network) or BFIR-id and BIFT-id (Non-MPLS network) for
	BIER BFD. The My Discriminator value is advertised in BIER BFD		BIER BFD. My Discriminator value is advertised in BIER BFD
	bootstrapping using one of options described in section 4.		bootstrapping using one of the options described in Section 4.
	6. Active Tail in BIER BFD		6. Active Tail in BIER BFD
	[RFC8563] defined an extension for Multipoint BFD, which allows the		[RFC8563] defined an extension for Multipoint BFD, which allows the
	head to discover the state of a multicast distribution tree for any		head to discover the state of a multicast distribution tree for any
	sub-set of tails. For BIER BFD in active tail mode, the BFIR may		sub-set of tails. For BIER BFD in the active tail mode, the BFIR may
	learn the state and connectivity of the BFERs through allowing the		learn the state and connectivity of the BFERs through allowing the
	BFERs to notify the BFIR. As per [RFC8563] provides detailed		BFERs to notify the BFIR. As per [RFC8563] provides detailed
	information on how the BFIR can use multipoint Poll sequence message		information on how the BFIR can use multipoint Poll sequence message
	or a combination of multicast and unicast Poll sequence messages to		or a combination of multicast and unicast Poll sequence messages to
	determine the state of multicast tree. Also, [RFC8563] describes		determine the state of the multicast tree. Also, [RFC8563] describes
	that a BFER can transmit an unsolicited unicast Poll sequence message		that a BFER can transmit an unsolicited unicast Poll sequence message
	to the BFIR (note that a unicast message must be sent over a path		to the BFIR (note that a unicast message must be sent over a path
	which is disjoint from the multicast distribution tree).		which is disjoint from the multicast distribution tree).
			6.1. Unsolicited Head Notification Mode
	[I-D.mirsky-mpls-p2mp-bfd] provides detailed information on using the		[I-D.mirsky-mpls-p2mp-bfd] provides detailed information on using the
	unsolicited notification method for P2MP MPLS LSP which is also		unsolicited notification method for P2MP MPLS LSP which is also
	applicable to BIER over MPLS case.		applicable to BIER.
			In Section 5.2.1 [RFC8563] is noted that "the tail sends unsolicited
			BFD packets in response to the detection of a multipoint path
			failure" but without the specifics on the information in the packet
			and frequency of transmissions. This document defines the procedure
			of the active tail with unsolicited notifications for BIER as
			specified below.
			Upon detecting the failure, a BFER sends a BFD control packet with
			the following settings:
			o the Poll (P) bit is set;
			o the Status (Sta) field set to Down value;
			o the Diagnostic (Diag) field set to Control Detection Time Expired
			value;
			o the value of the Your Discriminator field is set to the value the
			BFER has been using to demultiplex that BFD multipoint session;
			o BFD Control packet is encapsulated in IP/UDP with the destination
			IP address of the BFIR and the UDP destination port number set to
			4784 per [RFC5883]
			o the BFD Control packets are transmitted at the rate of one per
			second until either the BFER receives valid for this BFD session
			control packet with the Final (F) bit set from the BFIR or the
			defect condition clears.
			To improve the likelihood of notifying the BFIR of the failure, the
			BFER SHOULD transmit three BFD Control packets defined above in short
			succession.
			A BFIR that has received the BFD Control packet, as described above,
			sends the unicast IP/UDP encapsulated BFD control packet with the
			Final (F) bit set to the BFER.
	7. Security Considerations		7. Security Considerations
	For BIER OAM packet procssing security considerations, see		For BIER OAM packet processing security considerations, see
	[I-D.ietf-bier-ping].		[I-D.ietf-bier-ping].
	For general multipoint BFD security considerations, see [RFC8562].		For general multipoint BFD security considerations, see [RFC8562].
	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.
	8. Acknowledgements		8. Acknowledgements
	Authors would like to thank the comments and suggestions from Sandy		The authors would like to thank the comments and suggestions from
	Zhang, Jeffrey (Zhaohui) Zhang, Donald Eastlake 3rd.		Sandy Zhang, Jeffrey (Zhaohui) Zhang, Donald Eastlake 3rd.
	9. IANA Considerations		9. IANA Considerations
	9.1. BIER OAM Message Type		9.1. BIER OAM Message Type
	IANA is requested to assign a new type from the BIER OAM Message Type		IANA is requested to assign a new type from the BIER OAM Message Type
	registry as follows:		registry as follows:
	+--------+--------------+------------------+		+--------+--------------+------------------+
	| Value | Description | Reference |		| Value | Description | Reference |
	skipping to change at page 8, line 36 ¶		skipping to change at page 9, line 31 ¶
	| TBD4 | BIER BFD Sub-TLV | [this document] |		| TBD4 | BIER BFD Sub-TLV | [this document] |
	+--------+------------------+------------------+		+--------+------------------+------------------+
	Table 4		Table 4
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[I-D.ietf-bier-ping]		[I-D.ietf-bier-ping]
	Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M.,		Nainar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M.,
	and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier-		and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier-
	ping-06 (work in progress), October 2019.		ping-07 (work in progress), May 2020.
	[I-D.mirsky-mpls-p2mp-bfd]
	Mirsky, G., "BFD for Multipoint Networks over Point-to-
	Multi-Point MPLS LSP", draft-mirsky-mpls-p2mp-bfd-10 (work
	in progress), April 2020.
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://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, DOI 10.17487/RFC5880, June 2010,		(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
	<https://www.rfc-editor.org/info/rfc5880>.		<https://www.rfc-editor.org/info/rfc5880>.
			[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
			(BFD) for Multihop Paths", RFC 5883, DOI 10.17487/RFC5883,
			June 2010, <https://www.rfc-editor.org/info/rfc5883>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,		[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
	Przygienda, T., and S. Aldrin, "Multicast Using Bit Index		Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
	Explicit Replication (BIER)", RFC 8279,		Explicit Replication (BIER)", RFC 8279,
	DOI 10.17487/RFC8279, November 2017,		DOI 10.17487/RFC8279, November 2017,
	<https://www.rfc-editor.org/info/rfc8279>.		<https://www.rfc-editor.org/info/rfc8279>.
	skipping to change at page 9, line 38 ¶		skipping to change at page 10, line 34 ¶
	Multipoint Networks", RFC 8562, DOI 10.17487/RFC8562,		Multipoint Networks", RFC 8562, DOI 10.17487/RFC8562,
	April 2019, <https://www.rfc-editor.org/info/rfc8562>.		April 2019, <https://www.rfc-editor.org/info/rfc8562>.
	[RFC8563] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,		[RFC8563] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,
	Ed., "Bidirectional Forwarding Detection (BFD) Multipoint		Ed., "Bidirectional Forwarding Detection (BFD) Multipoint
	Active Tails", RFC 8563, DOI 10.17487/RFC8563, April 2019,		Active Tails", RFC 8563, DOI 10.17487/RFC8563, April 2019,
	<https://www.rfc-editor.org/info/rfc8563>.		<https://www.rfc-editor.org/info/rfc8563>.
	10.2. Informative References		10.2. Informative References
	[ISO9577] ISO/IEC TR 9577:1999,, "International Organization for		[I-D.mirsky-mpls-p2mp-bfd]
	Standardization "Information technology -		Mirsky, G., "BFD for Multipoint Networks over Point-to-
	Telecommunications and Information exchange between		Multi-Point MPLS LSP", draft-mirsky-mpls-p2mp-bfd-10 (work
	systems - Protocol identification in the network layer"",		in progress), April 2020.
	1999.
	Authors' Addresses		Authors' Addresses
	Quan Xiong		Quan Xiong
	ZTE Corporation		ZTE Corporation
	No.6 Huashi Park Rd		No.6 Huashi Park Rd
	Wuhan, Hubei 430223		Wuhan, Hubei 430223
	China		China
	Phone: +86 27 83531060		Phone: +86 27 83531060
	Email: xiong.quan@zte.com.cn		Email: xiong.quan@zte.com.cn
	Greg Mirsky		Greg Mirsky
	ZTE Corporation		ZTE Corporation
	USA		USA
	Email: gregimirsky@gmail.com		Email: gregimirsky@gmail.com
	Fangwei Hu		Fangwei Hu
	Individual		Individual
	Email: hufwei@gmail.com		Email: hufwei@gmail.com
End of changes. 26 change blocks.
	49 lines changed or deleted		88 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/