< draft-ietf-nvo3-hpvr2nve-cp-req-14.txt		draft-ietf-nvo3-hpvr2nve-cp-req-15.txt >
	NVO3 Working Group Y. Li		NVO3 Working Group Y. Li
	INTERNET-DRAFT D. Eastlake		INTERNET-DRAFT D. Eastlake
	Intended Status: Informational Huawei Technologies		Intended Status: Informational Huawei Technologies
	L. Kreeger		L. Kreeger
	Arrcus, Inc		Arrcus, Inc
	T. Narten		T. Narten
	IBM		IBM
	D. Black		D. Black
	Dell EMC		Dell EMC
	Expires: August 12, 2018 February 8, 2018		Expires: August 13, 2018 February 9, 2018
	Split Network Virtualization Edge (Split-NVE) Control Plane Requirements		Split Network Virtualization Edge (Split-NVE) Control Plane Requirements
	draft-ietf-nvo3-hpvr2nve-cp-req-14		draft-ietf-nvo3-hpvr2nve-cp-req-15
	Abstract		Abstract
	In a Split Network Virtualization Edge (Split-NVE) architecture, the		In a Split Network Virtualization Edge (Split-NVE) architecture, the
	functions of the NVE (Network Virtualization Edge) are split across a		functions of the NVE (Network Virtualization Edge) are split across a
	server and an external network equipment which is called an external		server and an external network equipment which is called an external
	NVE. The server-resident control plane functionality resides in		NVE. The server-resident control plane functionality resides in
	control software, which may be part of hypervisor or container		control software, which may be part of hypervisor or container
	management software; for simplicity, this document refers to the		management software; for simplicity, this document refers to the
	hypervisor as the location of this software.		hypervisor as the location of this software.
	skipping to change at page 3, line 5 ¶		skipping to change at page 3, line 5 ¶
	3.2 TSI Associate and Activate . . . . . . . . . . . . . . . . . 12		3.2 TSI Associate and Activate . . . . . . . . . . . . . . . . . 12
	3.3 TSI Disassociate and Deactivate . . . . . . . . . . . . . . 15		3.3 TSI Disassociate and Deactivate . . . . . . . . . . . . . . 15
	4. Hypervisor-to-NVE Control Plane Protocol Requirements . . . . . 16		4. Hypervisor-to-NVE Control Plane Protocol Requirements . . . . . 16
	5. VDP Applicability and Enhancement Needs . . . . . . . . . . . . 17		5. VDP Applicability and Enhancement Needs . . . . . . . . . . . . 17
	6. Security Considerations . . . . . . . . . . . . . . . . . . . . 19		6. Security Considerations . . . . . . . . . . . . . . . . . . . . 19
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 19		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 19
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
	8.1 Normative References . . . . . . . . . . . . . . . . . . . 20		8.1 Normative References . . . . . . . . . . . . . . . . . . . 20
	8.2 Informative References . . . . . . . . . . . . . . . . . . 20		8.2 Informative References . . . . . . . . . . . . . . . . . . 20
	Appendix A. IEEE 802.1Q VDP Illustration (For information only) . 20		Appendix A. IEEE 802.1Q VDP Illustration (For information only) . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	In the Split-NVE architecture shown in Figure 1, the functionality of		In the Split-NVE architecture shown in Figure 1, the functionality of
	the NVE (Network Virtualization Edge) is split across an end device		the NVE (Network Virtualization Edge) is split across an end device
	supporting virtualization and an external network device which is		supporting virtualization and an external network device which is
	called an external NVE. The portion of the NVE functionality located		called an external NVE. The portion of the NVE functionality located
	on the end device is called the tNVE and the portion located on the		on the end device is called the tNVE and the portion located on the
	external NVE is called the nNVE in this document. Overlay		external NVE is called the nNVE in this document. Overlay
	skipping to change at page 20, line 16 ¶		skipping to change at page 20, line 16 ¶
	mechanism, and draft-kompella-nvo3-server2nve. Thanks to all the co-		mechanism, and draft-kompella-nvo3-server2nve. Thanks to all the co-
	authors and contributing members of those drafts.		authors and contributing members of those drafts.
	The authors would like to specially thank Lucy Yong and Jon Hudson		The authors would like to specially thank Lucy Yong and Jon Hudson
	for their generous help in improving this document.		for their generous help in improving this document.
	8. References		8. References
	8.1 Normative References		8.1 Normative References
			[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
			Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y.		[RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y.
	Rekhter, "Framework for DC Network Virtualization",		Rekhter, "Framework for DC Network Virtualization",
	October 2014.		October 2014.
	[RFC7666] Asai H., MacFaden M., Schoenwaelder J., Shima K., Tsou T.,		[RFC7666] Asai H., MacFaden M., Schoenwaelder J., Shima K., Tsou T.,
	"Management Information Base for Virtual Machines		"Management Information Base for Virtual Machines
	Controlled by a Hypervisor", October 2015.		Controlled by a Hypervisor", October 2015.
	[RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., Narten,		[RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., Narten,
	T., "An Architecture for Data-Center Network		T., "An Architecture for Data-Center Network
	skipping to change at page 20, line 50 ¶		skipping to change at page 21, line 7 ¶
	[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally		[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
	Unique IDentifier (UUID) URN Namespace", RFC 4122, July		Unique IDentifier (UUID) URN Namespace", RFC 4122, July
	2005.		2005.
	[RFC7364] Narten, T., Gray, E., Black, D., Fang, L., Kreeger, L., and		[RFC7364] Narten, T., Gray, E., Black, D., Fang, L., Kreeger, L., and
	M. Napierala, "Problem Statement: Overlays for Network		M. Napierala, "Problem Statement: Overlays for Network
	Virtualization", October 2014.		Virtualization", October 2014.
	Appendix A. IEEE 802.1Q VDP Illustration (For information only)		Appendix A. IEEE 802.1Q VDP Illustration (For information only)
	The VDP (VSI Discovery and Discovery and Configuration Protocol [IEEE		The VDP (VSI Discovery and Discovery and Configuration Protocol,
	802.1Q]) can be considered as a controlling protocol running between		clause 41 of [IEEE 802.1Q]) can be considered as a controlling
	the hypervisor and the external bridge. VDP association TLV structure		protocol running between the hypervisor and the external bridge. VDP
	are formatted as shown in Figure A.1.		association TLV structure are formatted as shown in Figure A.1.
	+--------+--------+------+-----+--------+------+------+------+------+		+--------+--------+------+-----+--------+------+------+------+------+
	|TLV type|TLV info|Status|VSI |VSI Type|VSI ID|VSI ID|Filter|Filter|		|TLV type|TLV info|Status|VSI |VSI Type|VSI ID|VSI ID|Filter|Filter|
	| |string | |Type |Version |Format| |Info |Info |		| |string | |Type |Version |Format| |Info |Info |
	| |length | |ID | | | |format| |		| |length | |ID | | | |format| |
	+--------+--------+------+-----+--------+------+------+------+------+		+--------+--------+------+-----+--------+------+------+------+------+
	| | |<----VSI type&instance----->|<--Filter--->|		| | |<----VSI type&instance----->|<--Filter--->|
	| | |<-------------VSI attributes------------->|		| | |<-------------VSI attributes------------->|
	|<--TLV header--->|<-----------TLV information string ------------->|		|<--TLV header--->|<-----------TLV information string ------------->|
End of changes. 5 change blocks.
	7 lines changed or deleted		10 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/