< draft-ietf-nvo3-geneve-oam-01.txt		draft-ietf-nvo3-geneve-oam-02.txt >
	NVO3 Working Group G. Mirsky		NVO3 Working Group G. Mirsky
	Internet-Draft ZTE Corp.		Internet-Draft ZTE Corp.
	Intended status: Standards Track S. Boutros		Intended status: Standards Track S. Boutros
	Expires: May 19, 2021 Ciena		Expires: 18 November 2021 Ciena
	D. Black		D. Black
	Dell EMC		Dell EMC
	S. Pallagatti		S. Pallagatti
	VMware		VMware
	November 15, 2020		17 May 2021
	OAM for use in GENEVE		OAM for use in GENEVE
	draft-ietf-nvo3-geneve-oam-01		draft-ietf-nvo3-geneve-oam-02
	Abstract		Abstract
	This document lists a set of general requirements for active OAM		This document lists a set of general requirements for active OAM
	protocols in the Geneve overlay network. Based on the requirements,		protocols in the Geneve overlay network. Based on the requirements,
	IP encapsulation for active Operations, Administration, and		IP encapsulation for active Operations, Administration, and
	Maintenance protocols in Geneve protocol is defined. Considerations		Maintenance protocols in Geneve protocol is defined. Considerations
	for using ICMP and UDP-based protocols are discussed.		for using ICMP and UDP-based protocols are discussed.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 18 November 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 . . . . . . . . . . . . 3		1.1. Conventions used in this document . . . . . . . . . . . . 3
	1.1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . 3		1.1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . 3
	1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3		1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3
	2. Active OAM Protocols in Geneve Networks . . . . . . . . . . . 3		2. Active OAM Protocols in Geneve Networks . . . . . . . . . . . 3
	2.1. Defect Detection and Troubleshooting in Geneve Network		2.1. Defect Detection and Troubleshooting in Geneve Network with
	with Active OAM . . . . . . . . . . . . . . . . . . . . . 4		Active OAM . . . . . . . . . . . . . . . . . . . . . . . 4
	2.2. OAM Encapsulation in Geneve . . . . . . . . . . . . . . . 6		2.2. OAM Encapsulation in Geneve . . . . . . . . . . . . . . . 6
	3. Echo Request and Echo Reply in Geneve Tunnel . . . . . . . . 7		3. Echo Request and Echo Reply in Geneve Tunnel . . . . . . . . 8
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 8		5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	7.1. Normative References . . . . . . . . . . . . . . . . . . 8		7.1. Normative References . . . . . . . . . . . . . . . . . . 8
	7.2. Informative References . . . . . . . . . . . . . . . . . 9		7.2. Informative References . . . . . . . . . . . . . . . . . 9
	Appendix A. Additional Considerations for OAM Encapsulation		Appendix A. Additional Considerations for OAM Encapsulation Method
	Method in Geneve . . . . . . . . . . . . . . . . . . 10		in Geneve . . . . . . . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	Geneve [RFC8926] is intended to support various scenarios of network		Geneve [RFC8926] is intended to support various scenarios of network
	virtualization. In addition to carrying multi-protocol payload,		virtualization. In addition to carrying multi-protocol payload,
	e.g., Ethernet, IPv4/IPv6, the Geneve message includes metadata.		e.g., Ethernet, IPv4/IPv6, the Geneve message includes metadata.
	Operations, Administration, and Maintenance (OAM) protocols support		Operations, Administration, and Maintenance (OAM) protocols support
	fault management and performance monitoring functions necessary for		fault management and performance monitoring functions necessary for
	comprehensive network operation. Active OAM protocols, as defined in		comprehensive network operation. Active OAM protocols, as defined in
	skipping to change at page 5, line 33 ¶		skipping to change at page 5, line 33 ¶
	+----+		+----+
	|		|
	|		|
	=====================		=====================
	| |		| |
	+--------+ +--------+		+--------+ +--------+
	| Tenant | | Tenant |		| Tenant | | Tenant |
	| VNI 28 | | VNI 35 |		| VNI 28 | | VNI 35 |
	+--------+ +--------+		+--------+ +--------+
	Figure 1: An example of a Geneve domain		Figure 1: An example of a Geneve domain
	In the first case, a communication problem between Network		In the first case, a communication problem between Network
	Virtualization Edge (NVE) device A and NVE C was observed. The		Virtualization Edge (NVE) device A and NVE C was observed. The
	underlay, e.g., IP network, forwarding is working well but the Geneve		underlay, e.g., IP network, forwarding is working well but the Geneve
	connection is unstable for all tenants of NVE A and NVE C.		connection is unstable for all tenants of NVE A and NVE C.
	Troubleshooting and localization of the problem can be done		Troubleshooting and localization of the problem can be done
	irrespective of the VNI value.		irrespective of the VNI value.
	In the second case, traffic on VNI 35 between NVE A and NVE B has no		In the second case, traffic on VNI 35 between NVE A and NVE B has no
	problems, as on VNI 28 between NVE A and NVE C. But traffic on VNI		problems, as on VNI 28 between NVE A and NVE C. But traffic on VNI
	skipping to change at page 10, line 45 ¶		skipping to change at page 10, line 51 ¶
	followed by the GAL label with the S flag set to indicate that GAL is		followed by the GAL label with the S flag set to indicate that GAL is
	the Bottom-of-the-stack label. Then ACH MUST follow the GAL label		the Bottom-of-the-stack label. Then ACH MUST follow the GAL label
	and the value of the Channel Type identifies which of active OAM		and the value of the Channel Type identifies which of active OAM
	protocols being encapsulated in the packet.		protocols being encapsulated in the packet.
	Authors' Addresses		Authors' Addresses
	Greg Mirsky		Greg Mirsky
	ZTE Corp.		ZTE Corp.
	Email: gregimirsky@gmail.com		Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com
	Sami Boutros		Sami Boutros
	Ciena		Ciena
	Email: sboutros@ciena.com		Email: sboutros@ciena.com
	David Black		David Black
	Dell EMC		Dell EMC
	176 South Street		176 South Street
	Hopkinton, MA 01748		Hopkinton, MA, 01748
	United States of America		United States of America
	Email: david.black@dell.com		Email: david.black@dell.com
	Santosh Pallagatti		Santosh Pallagatti
	VMware		VMware
	Email: santosh.pallagatti@gmail.com		Email: santosh.pallagatti@gmail.com
End of changes. 14 change blocks.
	23 lines changed or deleted		22 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/