< draft-mtm-rtgwg-bfd-mc-lag-01.txt		draft-mtm-rtgwg-bfd-mc-lag-02.txt >
	RTG Working Group G. Mirsky		RTG Working Group G. Mirsky
	Internet-Draft ZTE Corp.		Internet-Draft ZTE Corp.
	Intended status: Standards Track J. Tantsura		Intended status: Standards Track J. Tantsura
	Expires: May 22, 2021 Apstra		Expires: 27 September 2021 Juniper Networks
	G. Mishra		G. Mishra
	Verizon Inc.		Verizon Inc.
	November 18, 2020		26 March 2021
	Bidirectional Forwarding Detection (BFD) on Multi-chassis Link		Bidirectional Forwarding Detection (BFD) on Multi-chassis Link
	Aggregation Group (MC-LAG) Interfaces		Aggregation Group (MC-LAG) Interfaces
	draft-mtm-rtgwg-bfd-mc-lag-01		draft-mtm-rtgwg-bfd-mc-lag-02
	Abstract		Abstract
	This document describes the use of Bidirectional Forwarding Detection		This document describes the use of Bidirectional Forwarding Detection
	for Multi-chassis Link Aggregation Group to provide faster than Link		for Multi-chassis Link Aggregation Group to provide faster than Link
	Aggregation Control Protocol convergence. This specification		Aggregation Control Protocol convergence. This specification
	enhances RFC 7130 "Bidirectional Forwarding Detection (BFD) on Link		enhances RFC 7130 "Bidirectional Forwarding Detection (BFD) on Link
	Aggregation Group (LAG) Interfaces".		Aggregation Group (LAG) Interfaces".
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 May 22, 2021.		This Internet-Draft will expire on 27 September 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		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 . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Conventions used in this document . . . . . . . . . . . . 2		1.1. Conventions used in this document . . . . . . . . . . . . 2
	1.1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . 2		1.1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . 2
	1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3		1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3
	2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3		2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
	3. BFD on MC-LAG with IP-only Data Plane . . . . . . . . . . . . 3		3. BFD on MC-LAG with IP-only Data Plane . . . . . . . . . . . . 3
	4. BFD on MC-LAG with IP/MPLS Data Plane . . . . . . . . . . . . 3		4. BFD on MC-LAG with IP/MPLS Data Plane . . . . . . . . . . . . 3
	skipping to change at page 3, line 37 ¶		skipping to change at page 3, line 36 ¶
	Protocol Label Switching (MPLS) data plane encapsulation.		Protocol Label Switching (MPLS) data plane encapsulation.
	3. BFD on MC-LAG with IP-only Data Plane		3. BFD on MC-LAG with IP-only Data Plane
	As described in [RFC7130], a micro-BFD session on the LAG interfaces		As described in [RFC7130], a micro-BFD session on the LAG interfaces
	may use IPv4 or IPv6 address family. In some cases, two sessions,		may use IPv4 or IPv6 address family. In some cases, two sessions,
	one with IPv4 and one with IPv6 addresses, may run concurrently.		one with IPv4 and one with IPv6 addresses, may run concurrently.
	This document doesn't change any of these but specifies the selection		This document doesn't change any of these but specifies the selection
	of the destination IP address in the MC-LAG use case:		of the destination IP address in the MC-LAG use case:
	o if IPv4 address family is used for the micro-BFD session, then an		* if IPv4 address family is used for the micro-BFD session, then an
	address from the link-local multicast address 224.0.0.0/24 range		address from the link-local multicast address 224.0.0.0/24 range
	SHOULD be used as the destination IP address. The subnet		SHOULD be used as the destination IP address. The subnet
	broadcast address MAY be used as the destination IP address as		broadcast address MAY be used as the destination IP address as
	well;		well;
	o if the address family used is IPv6, then the IPv6 All Routers		* if the address family used is IPv6, then the IPv6 All Routers
	address with the link scope, as defined in [RFC4291], FF02::2/128		address with the link scope, as defined in [RFC4291], FF02::2/128
	MUST be used as the destination IP address.		MUST be used as the destination IP address.
	4. BFD on MC-LAG with IP/MPLS Data Plane		4. BFD on MC-LAG with IP/MPLS Data Plane
	IP/UDP is the most natural encapsulation format for the case of		IP/UDP is the most natural encapsulation format for the case of
	micro-BFD on MC-LAG over IP/MPLS data plane as displayed in Figure 1.		micro-BFD on MC-LAG over IP/MPLS data plane as displayed in Figure 1.
	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 23 ¶		skipping to change at page 4, line 23 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Header		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Header
	| Source IP address | |		| Source IP address | |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------
	| UDP header |		| UDP header |
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	~ BFD Control Packet ~		~ BFD Control Packet ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: BFD on MC-LAG member link on IPv4/MPLS data plane		Figure 1: BFD on MC-LAG member link on IPv4/MPLS data plane
	An IP and UDP headers immediately follow an MPLS label stack. The		An IP and UDP headers immediately follow an MPLS label stack. The
	destination IP address MUST be set to the loopback address		destination IP address MUST be set to the loopback address
	127.0.0.1/32 for IPv4 [RFC1812], or the loopback address ::1/128 for		127.0.0.1/32 for IPv4 [RFC1812], or the loopback address ::1/128 for
	IPv6 [RFC4291]. TTL or Hop Limit field value MUST be set to 255,		IPv6 [RFC4291]. TTL or Hop Limit field value MUST be set to 255,
	according to [RFC5881].		according to [RFC5881].
	5. IANA Considerations		5. IANA Considerations
	This document makes no requests for IANA allocations. This section		This document makes no requests for IANA allocations. This section
	skipping to change at page 5, line 40 ¶		skipping to change at page 5, line 40 ¶
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 4291, DOI 10.17487/RFC4291, February		Architecture", RFC 4291, DOI 10.17487/RFC4291, February
	2006, <https://www.rfc-editor.org/info/rfc4291>.		2006, <https://www.rfc-editor.org/info/rfc4291>.
	Authors' Addresses		Authors' Addresses
	Greg Mirsky		Greg Mirsky
	ZTE Corp.		ZTE Corp.
	Email: gregimirsky@gmail.com		Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com
	Jeff Tantsura		Jeff Tantsura
	Apstra		Juniper Networks
	Email: jefftant.ietf@gmail.com		Email: jefftant.ietf@gmail.com
	Gyan Mishra		Gyan Mishra
	Verizon Inc.		Verizon Inc.
	Email: gyan.s.mishra@verizon.com		Email: gyan.s.mishra@verizon.com
End of changes. 11 change blocks.
	18 lines changed or deleted		17 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/