< draft-ietf-nvo3-hpvr2nve-cp-req-12.txt		draft-ietf-nvo3-hpvr2nve-cp-req-13.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
	EMC		EMC
	Expires: July 17, 2018 January 13, 2018		Expires: July 28, 2018 January 24, 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-12		draft-ietf-nvo3-hpvr2nve-cp-req-13
	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 20, line 19 ¶		skipping to change at page 20, line 19 ¶
	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		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2236] Fenner, W., "Internet Group Management Protocol, Version
	2", RFC 2236, November 1997.
	[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, May 2017.		2119 Key Words ", BCP 14, RFC 8174, May 2017.
	8.2 Informative References		8.2 Informative References
			[RFC2236] Fenner, W., "Internet Group Management Protocol, Version
			2", RFC 2236, November 1997.
	[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.
	[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",
End of changes. 4 change blocks.
	5 lines changed or deleted		5 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/