< draft-ietf-nvo3-bfd-geneve-00.txt		draft-ietf-nvo3-bfd-geneve-01.txt >
	NVO3 Working Group X. Min		NVO3 Working Group X. Min
	Internet-Draft G. Mirsky		Internet-Draft G. Mirsky
	Intended status: Standards Track ZTE Corp.		Intended status: Standards Track ZTE Corp.
	Expires: May 19, 2021 S. Pallagatti		Expires: August 25, 2021 S. Pallagatti
	VMware		VMware
	J. Tantsura		J. Tantsura
	Apstra		Juniper Networks
	November 15, 2020		February 21, 2021
	BFD for Geneve		BFD for Geneve
	draft-ietf-nvo3-bfd-geneve-00		draft-ietf-nvo3-bfd-geneve-01
	Abstract		Abstract
	This document describes the use of the Bidirectional Forwarding		This document describes the use of the Bidirectional Forwarding
	Detection (BFD) protocol in point-to-point Generic Network		Detection (BFD) protocol in point-to-point Generic Network
	Virtualization Encapsulation (Geneve) tunnels used to make up an		Virtualization Encapsulation (Geneve) tunnels used to make up an
	overlay network.		overlay network.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 19, 2021.		This Internet-Draft will expire on August 25, 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/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 18 ¶		skipping to change at page 2, line 18 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Conventions Used in This Document . . . . . . . . . . . . . . 3		2. Conventions Used in This Document . . . . . . . . . . . . . . 3
	2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3		2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
	3. BFD Packet Transmission over Geneve Tunnel . . . . . . . . . 3		3. BFD Packet Transmission over Geneve Tunnel . . . . . . . . . 3
	3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header . . . 3		3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header . . . 3
	3.2. BFD Encapsulation With Inner IP/UDP Header . . . . . . . 6		3.2. BFD Encapsulation With Inner IP/UDP Header . . . . . . . 6
	4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 8		4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 8
	4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 9		4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 8
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 9		5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	8.1. Normative References . . . . . . . . . . . . . . . . . . 10		8.1. Normative References . . . . . . . . . . . . . . . . . . 10
	8.2. Informative References . . . . . . . . . . . . . . . . . 10		8.2. Informative References . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	"Generic Network Virtualization Encapsulation" (Geneve)		"Generic Network Virtualization Encapsulation" (Geneve) [RFC8926]
	[I-D.ietf-nvo3-geneve] provides an encapsulation scheme that allows		provides an encapsulation scheme that allows building an overlay
	building an overlay network by decoupling the address space of the		network by decoupling the address space of the attached virtual hosts
	attached virtual hosts from that of the network.		from that of the network.
	This document describes the use of Bidirectional Forwarding Detection		This document describes the use of Bidirectional Forwarding Detection
	(BFD) protocol [RFC5880] to enable monitoring continuity of the path		(BFD) protocol [RFC5880] to enable monitoring continuity of the path
	between two Geneve tunnel endpoints, which may be NVE (Network		between two Geneve tunnel endpoints, which may be NVE (Network
	Virtualization Edge) or other device acting as a Geneve tunnel		Virtualization Edge) or other device acting as a Geneve tunnel
	endpoint. Specifically, the asynchronous mode of BFD, as defined in		endpoint. Specifically, the asynchronous mode of BFD, as defined in
	[RFC5880], is used to monitor a p2p Geneve tunnel, and support for		[RFC5880], is used to monitor a p2p Geneve tunnel, and support for
	BFD Echo function is outside the scope of this document. For		BFD Echo function is outside the scope of this document. For
	simplicity, in this document, NVE is used to represent Geneve tunnel		simplicity, in this document, NVE is used to represent Geneve tunnel
	endpoint, TS (Tenant System) is used to represent the physical or		endpoint, TS (Tenant System) is used to represent the physical or
	virtual device attached to a Geneve tunnel endpoint from the outside.		virtual device attached to a Geneve tunnel endpoint from the outside.
	VAP (Virtual Access Point) is the NVE side of the interface between		VAP (Virtual Access Point) is the NVE side of the interface between
	the NVE and the TS, and a VAP is a logical network port (virtual or		the NVE and the TS, and a VAP is a logical network port (virtual or
	physical) into a specific virtual network. For detailed definitions		physical) into a specific virtual network. For detailed definitions
	and descriptions of NVE, TS and VAP, please refer to [RFC7365] and		and descriptions of NVE, TS and VAP, please refer to [RFC7365] and
	[RFC8014].		[RFC8014].
	The use cases and the deployment of BFD for Geneve are consistent		The use cases and the deployment of BFD for Geneve are consistent
	with what's described in Section 1 and 3 of [I-D.ietf-bfd-vxlan].		with what's described in Section 1 and 3 of [RFC8971] ("Bidirectional
			Forwarding Detection (BFD) for Virtual eXtensible Local Area Network
	The major difference between Geneve and "Virtual eXtensible Local		(VXLAN)"), except for the usage of Management VNI, which is outside
	Area Network" (VXLAN) [RFC7348] encapsulation is that Geneve supports		the scope of this document. The major difference between Geneve and
	multi-protocol payload and variable length options.		VXLAN [RFC7348] is that Geneve supports multi-protocol payload and
			variable length options.
	2. Conventions Used in This Document		2. Conventions Used in This Document
	2.1. Abbreviations		2.1. Abbreviations
	BFD: Bidirectional Forwarding Detection		BFD: Bidirectional Forwarding Detection
			EVPN: Ethernet Virtual Private Networks
	Geneve: Generic Network Virtualization Encapsulation		Geneve: Generic Network Virtualization Encapsulation
	NVE: Network Virtualization Edge		NVE: Network Virtualization Edge
	TS: Tenant System		TS: Tenant System
	VAP: Virtual Access Point		VAP: Virtual Access Point
	VNI: Virtual Network Identifier		VNI: Virtual Network Identifier
	skipping to change at page 3, line 48 ¶		skipping to change at page 3, line 51 ¶
	or an IP packet, this document defines two formats of BFD packet		or an IP packet, this document defines two formats of BFD packet
	encapsulation in Geneve. BFD session is originated and terminated at		encapsulation in Geneve. BFD session is originated and terminated at
	VAP of an NVE, selection of the BFD packet encapsulation is based on		VAP of an NVE, selection of the BFD packet encapsulation is based on
	how the VAP encapsulates the data packets.		how the VAP encapsulates the data packets.
	3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header		3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header
	If the VAP that originates the BFD packets is used to encapsulate		If the VAP that originates the BFD packets is used to encapsulate
	Ethernet data frames, then BFD packets are encapsulated in Geneve as		Ethernet data frames, then BFD packets are encapsulated in Geneve as
	described below. The Geneve packet format over IPv4 is defined in		described below. The Geneve packet format over IPv4 is defined in
	Section 3.1 of [I-D.ietf-nvo3-geneve]. The Geneve packet format over		Section 3.1 of [RFC8926]. The Geneve packet format over IPv6 is
	IPv6 is defined in Section 3.2 of [I-D.ietf-nvo3-geneve]. The Outer		defined in Section 3.2 of [RFC8926]. The Outer IP/UDP and Geneve
	IP/UDP and Geneve headers MUST be encoded by the sender as defined in		headers MUST be encoded by the sender as defined in [RFC8926]. Note
	[I-D.ietf-nvo3-geneve]. Note that the outer IP header and the inner		that the outer IP header and the inner IP header may not be of the
	IP header may not be of the same address family, in other words,		same address family, in other words, outer IPv6 header accompanied
	outer IPv6 header accompanied with inner IPv4 header and outer IPv4		with inner IPv4 header and outer IPv4 header accompanied with inner
	header accompanied with inner IPv6 header are both possible.		IPv6 header are both possible.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Outer Ethernet Header ~		~ Outer Ethernet Header ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Outer IPvX Header ~		~ Outer IPvX Header ~
	skipping to change at page 5, line 19 ¶		skipping to change at page 5, line 19 ¶
	Ethernet Header:		Ethernet Header:
	Source MAC: MAC address of a VAP of the originating NVE.		Source MAC: MAC address of a VAP of the originating NVE.
	Destination MAC: MAC address of a VAP of the terminating NVE.		Destination MAC: MAC address of a VAP of the terminating NVE.
	IP Header:		IP Header:
	Source IP: IP address of a VAP of the originating NVE. If the		Source IP: IP address of a VAP of the originating NVE. If the
	VAP of the originating NVE has no IP address, then the IP		VAP of the originating NVE has no IP address, then the IP
	address of the originating NVE is used.		address 0.0.0.0 for IPv4 or ::/128 for IPv6 SHOULD be used.
	Destination IP: IP address of a VAP of the terminating NVE. If		Destination IP: IP address of a VAP of the terminating NVE. If
	the VAP of the terminating NVE has no IP address, then the IP		the VAP of the terminating NVE has no IP address, then the IP
	address MUST be chosen from the 127/8 range for IPv4, and from		address SHOULD be selected from the range 127/8 for IPv4, or be
	the ::ffff:127.0.0.0/104 range for IPv6.		set to ::1/128 for IPv6.
	TTL or Hop Limit: MUST be set to 255 in accordance with		TTL or Hop Limit: MUST be set to 255 in accordance with
	[RFC5881].		[RFC5881].
	The fields of the UDP header and the BFD Control packet are		The fields of the UDP header and the BFD Control packet are
	encoded as specified in [RFC5881].		encoded as specified in [RFC5881].
	When the BFD packets are encapsulated in Geneve in this way, the		When the BFD packets are encapsulated in Geneve in this way, the
	Geneve header defined in [I-D.ietf-nvo3-geneve] follows the value set		Geneve header defined in [RFC8926] follows the value set below.
	below.
	Opt Len field SHOULD be set to 0, which indicates there isn't any		Opt Len field SHOULD be set to 0, which indicates there isn't any
	variable length option.		variable length option.
	O bit MUST be set to 1, which indicates this packet contains a		O bit MUST be set to 1, which indicates this packet contains a
	control message.		control message.
	C bit MUST be set to 0, which indicates there isn't any critical		C bit MUST be set to 0, which indicates there isn't any critical
	option.		option.
	Protocol Type field MUST be set to 0x6558 (Ethernet frame).		Protocol Type field MUST be set to 0x6558 (Ethernet frame).
	Virtual Network Identifier (VNI) field SHOULD be set to the VNI		Virtual Network Identifier (VNI) field SHOULD be set to the VNI
	number that the originating VAP is mapped to.		number that the originating VAP is mapped to.
	3.2. BFD Encapsulation With Inner IP/UDP Header		3.2. BFD Encapsulation With Inner IP/UDP Header
	If the VAP that originates the BFD packets is used to encapsulate IP		If the VAP that originates the BFD packets is used to encapsulate IP
	data packets, then BFD packets are encapsulated in Geneve as		data packets, then BFD packets are encapsulated in Geneve as
	described below. The Geneve packet format over IPv4 is defined in		described below. The Geneve packet format over IPv4 is defined in
	Section 3.1 of [I-D.ietf-nvo3-geneve]. The Geneve packet format over		Section 3.1 of [RFC8926]. The Geneve packet format over IPv6 is
	IPv6 is defined in Section 3.2 of [I-D.ietf-nvo3-geneve]. The Outer		defined in Section 3.2 of [RFC8926]. The Outer IP/UDP and Geneve
	IP/UDP and Geneve headers MUST be encoded by the sender as defined in		headers MUST be encoded by the sender as defined in [RFC8926]. Note
	[I-D.ietf-nvo3-geneve]. Note that the outer IP header and the inner		that the outer IP header and the inner IP header may not be of the
	IP header may not be of the same address family, in other words,		same address family, in other words, outer IPv6 header accompanied
	outer IPv6 header accompanied with inner IPv4 header and outer IPv4		with inner IPv4 header and outer IPv4 header accompanied with inner
	header accompanied with inner IPv6 header are both possible.		IPv6 header are both possible.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Ethernet Header ~		~ Ethernet Header ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Outer IPvX Header ~		~ Outer IPvX Header ~
	skipping to change at page 8, line 12 ¶		skipping to change at page 8, line 12 ¶
	Destination IP: IP address of a VAP of the terminating NVE.		Destination IP: IP address of a VAP of the terminating NVE.
	TTL or Hop Limit: MUST be set to 255 in accordance with		TTL or Hop Limit: MUST be set to 255 in accordance with
	[RFC5881].		[RFC5881].
	The fields of the UDP header and the BFD Control packet are		The fields of the UDP header and the BFD Control packet are
	encoded as specified in [RFC5881].		encoded as specified in [RFC5881].
	When the BFD packets are encapsulated in Geneve in this way, the		When the BFD packets are encapsulated in Geneve in this way, the
	Geneve header defined in [I-D.ietf-nvo3-geneve] follows the value set		Geneve header defined in [RFC8926] follows the value set below.
	below.
	Opt Len field SHOULD be set to 0, which indicates there isn't any		Opt Len field SHOULD be set to 0, which indicates there isn't any
	variable length option.		variable length option.
	O bit MUST be set to 1, which indicates this packet contains a		O bit MUST be set to 1, which indicates this packet contains a
	control message.		control message.
	C bit MUST be set to 0, which indicates there isn't any critical		C bit MUST be set to 0, which indicates there isn't any critical
	option.		option.
	Protocol Type field MUST be set to 0x0800 (IPv4) or 0x86DD (IPv6),		Protocol Type field MUST be set to 0x0800 (IPv4) or 0x86DD (IPv6),
	depending on the address family of the inner IP packet.		depending on the address family of the inner IP packet.
	Virtual Network Identifier (VNI) field SHOULD be set to the VNI		Virtual Network Identifier (VNI) field SHOULD be set to the VNI
	number that the originating VAP is mapped to.		number that the originating VAP is mapped to.
	4. Reception of BFD packet from Geneve Tunnel		4. Reception of BFD packet from Geneve Tunnel
	Once a packet is received, the NVE MUST validate the packet as		Once a packet is received, the NVE MUST validate the packet as
	described in [I-D.ietf-nvo3-geneve].		described in [RFC8926].
	If the Protocol Type field equals 0x6558 (Ethernet frame), and the		If the Protocol Type field equals 0x6558 (Ethernet frame), and the
	Destination MAC of the inner Ethernet frame matches the MAC		Destination MAC of the inner Ethernet frame matches the MAC
	address of a VAP which is mapped to the same as received VNI, then		address of a VAP which is mapped to the same as received VNI, then
	the Destination IP, the UDP destination port and the TTL or Hop		the Destination IP, the UDP destination port and the TTL or Hop
	Limit of the inner IP packet MUST be validated to determine		Limit of the inner IP packet MUST be validated to determine
	whether the received packet can be processed by BFD.		whether the received packet can be processed by BFD.
	If the Protocol Type field equals 0x0800 (IPv4) or 0x86DD (IPv6),		If the Protocol Type field equals 0x0800 (IPv4) or 0x86DD (IPv6),
	and the Destination IP of the inner IP packet matches the IP		and the Destination IP of the inner IP packet matches the IP
	skipping to change at page 9, line 34 ¶		skipping to change at page 9, line 28 ¶
	IP, the destination MAC, the destination IP, and the source UDP		IP, the destination MAC, the destination IP, and the source UDP
	port number present in the inner Ethernet/IP/UDP header.		port number present in the inner Ethernet/IP/UDP header.
	When the BFD Encapsulation With Inner IP/UDP Header is used, the		When the BFD Encapsulation With Inner IP/UDP Header is used, the
	BFD session MUST be identified using the VNI number, and the inner		BFD session MUST be identified using the VNI number, and the inner
	IP/UDP header, i.e., the source IP, the destination IP, and the		IP/UDP header, i.e., the source IP, the destination IP, and the
	source UDP port number present in the inner IP/UDP header.		source UDP port number present in the inner IP/UDP header.
	If the BFD packet is received with non-zero Your Discriminator, then		If the BFD packet is received with non-zero Your Discriminator, then
	the BFD session MUST be demultiplexed only with Your Discriminator as		the BFD session MUST be demultiplexed only with Your Discriminator as
	the key.		the key. The exchange of BFD discriminators may be achieved by echo
			request/reply, EVPN, etc. The detailed mechanism on how to exchange
			the BFD discriminators is outside the scope of this document.
	5. Security Considerations		5. Security Considerations
	This document does not raise any additional security issues beyond		This document does not raise any additional security issues beyond
	those of the specifications referred to in the list of references.		those of the specifications referred to in the list of references.
	6. IANA Considerations		6. IANA Considerations
	This document has no IANA action requested.		This document has no IANA action requested.
	skipping to change at page 10, line 9 ¶		skipping to change at page 10, line 9 ¶
	The authors would like to acknowledge Reshad Rahman, Jeffrey Haas and		The authors would like to acknowledge Reshad Rahman, Jeffrey Haas and
	Matthew Bocci for their guidance on this work.		Matthew Bocci for their guidance on this work.
	The authors would like to acknowledge David Black for his explanation		The authors would like to acknowledge David Black for his explanation
	on the mapping relation between VAP and VNI.		on the mapping relation between VAP and VNI.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-nvo3-geneve]
	Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
	Network Virtualization Encapsulation", draft-ietf-
	nvo3-geneve-16 (work in progress), March 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>.
	[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection		[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	skipping to change at page 10, line 43 ¶		skipping to change at page 10, line 38 ¶
	[RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T.		[RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T.
	Narten, "An Architecture for Data-Center Network		Narten, "An Architecture for Data-Center Network
	Virtualization over Layer 3 (NVO3)", RFC 8014,		Virtualization over Layer 3 (NVO3)", RFC 8014,
	DOI 10.17487/RFC8014, December 2016,		DOI 10.17487/RFC8014, December 2016,
	<https://www.rfc-editor.org/info/rfc8014>.		<https://www.rfc-editor.org/info/rfc8014>.
	[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>.
	8.2. Informative References		[RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed.,
			"Geneve: Generic Network Virtualization Encapsulation",
			RFC 8926, DOI 10.17487/RFC8926, November 2020,
			<https://www.rfc-editor.org/info/rfc8926>.
	[I-D.ietf-bfd-vxlan]		8.2. Informative References
	Pallagatti, S., Mirsky, G., Paragiri, S., Govindan, V.,
	and M. Mudigonda, "BFD for VXLAN", draft-ietf-bfd-vxlan-16
	(work in progress), October 2020.
	[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,		[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
	L., Sridhar, T., Bursell, M., and C. Wright, "Virtual		L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
	eXtensible Local Area Network (VXLAN): A Framework for		eXtensible Local Area Network (VXLAN): A Framework for
	Overlaying Virtualized Layer 2 Networks over Layer 3		Overlaying Virtualized Layer 2 Networks over Layer 3
	Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,		Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
	<https://www.rfc-editor.org/info/rfc7348>.		<https://www.rfc-editor.org/info/rfc7348>.
			[RFC8971] Pallagatti, S., Ed., Mirsky, G., Ed., Paragiri, S.,
			Govindan, V., and M. Mudigonda, "Bidirectional Forwarding
			Detection (BFD) for Virtual eXtensible Local Area Network
			(VXLAN)", RFC 8971, DOI 10.17487/RFC8971, December 2020,
			<https://www.rfc-editor.org/info/rfc8971>.
	Authors' Addresses		Authors' Addresses
	Xiao Min		Xiao Min
	ZTE Corp.		ZTE Corp.
	Nanjing		Nanjing
	China		China
	Phone: +86 25 88013062		Phone: +86 25 88013062
	Email: xiao.min2@zte.com.cn		Email: xiao.min2@zte.com.cn
	skipping to change at page 11, line 34 ¶		skipping to change at page 11, line 33 ¶
	USA		USA
	Email: gregimirsky@gmail.com		Email: gregimirsky@gmail.com
	Santosh Pallagatti		Santosh Pallagatti
	VMware		VMware
	Email: santosh.pallagatti@gmail.com		Email: santosh.pallagatti@gmail.com
	Jeff Tantsura		Jeff Tantsura
	Apstra		Juniper Networks
	Email: jefftant.ietf@gmail.com		Email: jefftant.ietf@gmail.com
End of changes. 22 change blocks.
	50 lines changed or deleted		54 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/