Subject: [nvo3] FW: New Version Notification for draft-ietf-nvo3-hpvr2nve-cp-req-01.txt

From: Liyizhou <[email-masked]>
Date: Tue, 18 Nov 2014 07:20:11 +0000

We have updated the document as per the offline discussions and mailing list feedback.

Basically it
1. Improved the terminologies. Make the definition of Split-NVE consistent with other docs.
2. Refined the bulleted requirements. 

Comments are welcome.

Thanks,
Yizhou

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Tuesday, November 18, 2014 3:10 PM
To: David L. Black; Liyizhou; Lawrence Kreeger; Lucy yong; David Black; Lucy yong; Thomas Narten; Liyizhou; Dr. Thomas Narten; Lawrence Kreeger
Subject: New Version Notification for draft-ietf-nvo3-hpvr2nve-cp-req-01.txt

A new version of I-D, draft-ietf-nvo3-hpvr2nve-cp-req-01.txt
has been successfully submitted by Yizhou Li and posted to the IETF repository.

Name:		draft-ietf-nvo3-hpvr2nve-cp-req
Revision:	01
Title:		Hypervisor to NVE Control Plane Requirements
Document date:	2014-11-18
Group:		nvo3
Pages:		21
URL:            http://www.ietf.org/internet-drafts/draft-ietf-nvo3-hpvr2nve-cp-req-01.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-nvo3-hpvr2nve-cp-req/
Htmlized:       http://tools.ietf.org/html/draft-ietf-nvo3-hpvr2nve-cp-req-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-hpvr2nve-cp-req-01

Abstract:
   In a Split-NVE architructure, the functions of the NVE are split
   across the hypervisor/container on a server and an external network
   equipment which is called an external NVE. A control plane
   protocol(s) between a hypervisor and its associated external NVE(s)
   is used for the hypervisor to distribute its virtual machine
   networking state to the external NVE(s) for further handling. This
   document illustrates the functionality required by this type of
   control plane signaling protocol and outlines the high level
   requirements. Virtual machine states as well as state transitioning
   are summarized to help clarifying the needed protocol requirements.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat