< draft-ietf-nvo3-bfd-geneve-01.txt		draft-ietf-nvo3-bfd-geneve-02.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: August 25, 2021 S. Pallagatti		Expires: September 11, 2021 S. Pallagatti
	VMware		VMware
	J. Tantsura		J. Tantsura
	Juniper Networks		Juniper Networks
	February 21, 2021		March 10, 2021
	BFD for Geneve		BFD for Geneve
	draft-ietf-nvo3-bfd-geneve-01		draft-ietf-nvo3-bfd-geneve-02
	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 August 25, 2021.		This Internet-Draft will expire on September 11, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 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
	skipping to change at page 2, line 16 ¶		skipping to change at page 2, line 16 ¶
	described in the Simplified BSD License.		described in the Simplified BSD License.
	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 . . . . . . . 5
	4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 8		4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 7
	4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 8		4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 8
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 9		5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	8.1. Normative References . . . . . . . . . . . . . . . . . . 10		8.1. Normative References . . . . . . . . . . . . . . . . . . 9
	8.2. Informative References . . . . . . . . . . . . . . . . . 10		8.2. Informative References . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	"Generic Network Virtualization Encapsulation" (Geneve) [RFC8926]		"Generic Network Virtualization Encapsulation" (Geneve) [RFC8926]
	provides an encapsulation scheme that allows building an overlay		provides an encapsulation scheme that allows building an overlay
	network by decoupling the address space of the attached virtual hosts		network by decoupling the address space of the 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
	skipping to change at page 3, line 5 ¶		skipping to change at page 3, line 5 ¶
	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 [RFC8971] ("Bidirectional		with what's described in Section 1 and 3 of [RFC8971] ("Bidirectional
	Forwarding Detection (BFD) for Virtual eXtensible Local Area Network		Forwarding Detection (BFD) for Virtual eXtensible Local Area Network
	(VXLAN)"), except for the usage of Management VNI, which is outside		(VXLAN)"), except for the usage of Management VNI, which in the case
	the scope of this document. The major difference between Geneve and		of Geneve is described in [I-D.ietf-nvo3-geneve-oam], and outside the
			scope of this document. The major difference between Geneve and
	VXLAN [RFC7348] is that Geneve supports multi-protocol payload and		VXLAN [RFC7348] is that Geneve supports multi-protocol payload and
	variable length options.		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		EVPN: Ethernet Virtual Private Networks
	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 0.0.0.0 for IPv4 or ::/128 for IPv6 SHOULD be used.		address 0.0.0.0 for IPv4 or ::/128 for IPv6 MUST 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 SHOULD be selected from the range 127/8 for IPv4, or be		address 127.0.0.1 for IPv4 or ::1/128 for IPv6 MUST be used.
	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 [RFC8926] follows the value set below.		Geneve header defined in [RFC8926] follows the value set below.
	skipping to change at page 10, line 45 ¶		skipping to change at page 9, line 48 ¶
	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>.
	[RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed.,		[RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed.,
	"Geneve: Generic Network Virtualization Encapsulation",		"Geneve: Generic Network Virtualization Encapsulation",
	RFC 8926, DOI 10.17487/RFC8926, November 2020,		RFC 8926, DOI 10.17487/RFC8926, November 2020,
	<https://www.rfc-editor.org/info/rfc8926>.		<https://www.rfc-editor.org/info/rfc8926>.
	8.2. Informative References		8.2. Informative References
			[I-D.ietf-nvo3-geneve-oam]
			Mirsky, G., Boutros, S., Black, D., and S. Pallagatti,
			"OAM for use in GENEVE", draft-ietf-nvo3-geneve-oam-01
			(work in progress), November 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.,		[RFC8971] Pallagatti, S., Ed., Mirsky, G., Ed., Paragiri, S.,
	Govindan, V., and M. Mudigonda, "Bidirectional Forwarding		Govindan, V., and M. Mudigonda, "Bidirectional Forwarding
	Detection (BFD) for Virtual eXtensible Local Area Network		Detection (BFD) for Virtual eXtensible Local Area Network
End of changes. 10 change blocks.
	18 lines changed or deleted		23 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/