< draft-ietf-nvo3-hpvr2nve-cp-req-04.txt		draft-ietf-nvo3-hpvr2nve-cp-req-05.txt >
	NVO3 Working Group Yizhou Li		NVO3 Working Group Yizhou Li
	INTERNET-DRAFT Lucy Yong		INTERNET-DRAFT Lucy Yong
	Intended Status: Informational Huawei Technologies		Intended Status: Informational Huawei Technologies
	Lawrence Kreeger		Lawrence Kreeger
	Cisco		Cisco
	Thomas Narten		Thomas Narten
	IBM		IBM
	David Black		David Black
	EMC		EMC
	Expires: August 22, 2016 February 19, 2016		Expires: February 25, 2017 August 24, 2016
	Split-NVE Control Plane Requirements		Split-NVE Control Plane Requirements
	draft-ietf-nvo3-hpvr2nve-cp-req-04		draft-ietf-nvo3-hpvr2nve-cp-req-05
	Abstract		Abstract
	In a Split-NVE architecture, the functions of the NVE are split		In a Split-NVE architecture, the functions of the NVE are split
	across a server and an external network equipment which is called an		across a server and an external network equipment which is called an
	external NVE. The server-resident control plane functionality		external NVE. The server-resident control plane functionality
	resides in control software, which may be part of a hypervisor or		resides in control software, which may be part of a hypervisor or
	container management software; for simplicity, this draft refers to		container management software; for simplicity, this draft refers to
	the hypervisor as the location of this software.		the hypervisor as the location of this software.
End of changes. 2 change blocks.
	2 lines changed or deleted		2 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/