[nvo3] FW: New Version Notification for draft-yizhou-nvo3-hpvr2nve-cp-req-00.txt
Liyizhou <liyizhou@huawei.com> Fri, 16 May 2014 05:52 UTC
Return-Path: <liyizhou@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96BF41A0130 for <nvo3@ietfa.amsl.com>; Thu, 15 May 2014 22:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RtMPf82Stvi3 for <nvo3@ietfa.amsl.com>; Thu, 15 May 2014 22:52:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B5921A011C for <nvo3@ietf.org>; Thu, 15 May 2014 22:52:54 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEF03337; Fri, 16 May 2014 05:52:45 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 16 May 2014 06:52:02 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 16 May 2014 06:52:42 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.113]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 16 May 2014 13:52:36 +0800
From: Liyizhou <liyizhou@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: New Version Notification for draft-yizhou-nvo3-hpvr2nve-cp-req-00.txt
Thread-Index: AQHPcMp4Wccg0VwE6EWE9VjWMMOxyptCs4Vw
Date: Fri, 16 May 2014 05:52:36 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8F5E8821E4@nkgeml503-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.136.38]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/bmrl8TkMUAiCxt0LF85BIr_A6Wc
Subject: [nvo3] FW: New Version Notification for draft-yizhou-nvo3-hpvr2nve-cp-req-00.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2014 05:52:57 -0000
Hi all, We appreciate your comments and suggestions on the following draft which is a merger of draft-kreeger-nvo3-hypervisor-nve-cp, draft-gu-nvo3-tes-nve-mechanism and draft-kompella-nvo3-server2nve. It covers the control plane requirements in split NVE architecture. Thanks, Yizhou -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Friday, May 16, 2014 1:48 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-yizhou-nvo3-hpvr2nve-cp-req-00.txt A new version of I-D, draft-yizhou-nvo3-hpvr2nve-cp-req-00.txt has been successfully submitted by Yizhou Li and posted to the IETF repository. Name: draft-yizhou-nvo3-hpvr2nve-cp-req Revision: 00 Title: Hypervisor to NVE Control Plane Requirements Document date: 2014-05-16 Group: Individual Submission Pages: 20 URL: http://www.ietf.org/internet-drafts/draft-yizhou-nvo3-hpvr2nve-cp-req-00.txt Status: https://datatracker.ietf.org/doc/draft-yizhou-nvo3-hpvr2nve-cp-req/ Htmlized: http://tools.ietf.org/html/draft-yizhou-nvo3-hpvr2nve-cp-req-00 Abstract: This document describes the control plane protocol requirements when NVE is not co-located with the hypervisor on a server. A control plane protocol (or protocols) between a hypervisor and its associated external NVE(s) is used for the hypervisor to populate its virtual machines states to the NVE(s) for further handling. This document illustrates the functionalities required by such control plane signaling protocols and outlines the high level requirements to be fulfiled. Virtual machine states and state transitioning are summarized to help clarifying the needed 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