[Sdn] Solicit for comments of the draft: New Version Notification for draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt

顾 戎 <gurong_cmcc@outlook.com> Thu, 17 March 2016 05:50 UTC

Return-Path: <gurong_cmcc@outlook.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5B6D112D72C for <sdn@ietfa.amsl.com>; Wed, 16 Mar 2016 22:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id l0G9xxo3sPqR for <sdn@ietfa.amsl.com>; Wed, 16 Mar 2016 22:50:07 -0700 (PDT)
Received: from SNT004-OMC1S39.hotmail.com (snt004-omc1s39.hotmail.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 339CC12D6BF for <sdn@irtf.org>; Wed, 16 Mar 2016 22:50:07 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com ([]) by SNT004-OMC1S39.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 16 Mar 2016 22:50:06 -0700
Received: from SG2APC01FT029.eop-APC01.prod.protection.outlook.com ( by SG2APC01HT008.eop-APC01.prod.protection.outlook.com ( with Microsoft SMTP Server (TLS) id 15.1.434.11; Thu, 17 Mar 2016 05:50:00 +0000
Received: from KL1PR02MB1109.apcprd02.prod.outlook.com ( by SG2APC01FT029.mail.protection.outlook.com ( with Microsoft SMTP Server (TLS) id 15.1.434.11 via Frontend Transport; Thu, 17 Mar 2016 05:49:57 +0000
Received: from KL1PR02MB1109.apcprd02.prod.outlook.com ([]) by KL1PR02MB1109.apcprd02.prod.outlook.com ([]) with mapi id 15.01.0434.019; Thu, 17 Mar 2016 05:49:57 +0000
From: =?gb2312?B?ucsgyNY=?= <gurong_cmcc@outlook.com>
To: "sdn@irtf.org" <sdn@irtf.org>
Thread-Topic: Solicit for comments of the draft: New Version Notification for draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt
Thread-Index: AQHRgA7sH6G08KA/0U2sYt4y8Dagl59dHeOX
Date: Thu, 17 Mar 2016 05:49:56 +0000
Message-ID: <KL1PR02MB1109F373162037B892588A598B8B0@KL1PR02MB1109.apcprd02.prod.outlook.com>
References: <20160317053609.24361.26398.idtracker@ietfa.amsl.com>
In-Reply-To: <20160317053609.24361.26398.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
authentication-results: spf=softfail (sender IP is smtp.mailfrom=outlook.com; chinamobile.com; dkim=none (message not signed) header.d=none;chinamobile.com; dmarc=fail action=none header.from=outlook.com;
received-spf: SoftFail (protection.outlook.com: domain of transitioning outlook.com discourages use of as permitted sender)
x-tmn: [F+xH0UGKT4e1vFc8PitoM0I0Sj/+7IOF]
x-eopattributedmessage: 0
x-forefront-antispam-report: CIP:; IPV:NLI; CTRY:GB; EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:SG2APC01HT008; H:KL1PR02MB1109.apcprd02.prod.outlook.com; FPR:; SPF:SoftFail; MLV:ovrnspm; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: 6364edf3-b70a-424a-3d25-08d34e27f8c8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5061506196)(5061507196); SRVR:SG2APC01HT008;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:SG2APC01HT008; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT008;
x-forefront-prvs: 0884AAA693
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2016 05:49:56.7372 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT008
X-OriginalArrivalTime: 17 Mar 2016 05:50:06.0596 (UTC) FILETIME=[DBCD6C40:01D18010]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sdn/v3fY1fEdcyuY128QHLu-ZF1pAgk>
Cc: "gurong@chinamobile.com" <gurong@chinamobile.com>
Subject: [Sdn] Solicit for comments of the draft: New Version Notification for draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt
X-BeenThere: sdn@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/sdn>, <mailto:sdn-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@irtf.org>
List-Help: <mailto:sdn-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/sdn>, <mailto:sdn-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2016 05:50:09 -0000

Hi, dear all.
I have submitted a draft about the relationship between hypervisor and the SDN network. In this draft, a problem of hypervisor such as VMware ESXI and Xen is presented, as we find it out that there are limitations on such commercial hypervisors rather than KVM. By adopting them, the initial virtual switch is out of control of SDN controller. 

We want to share the experience of such problems with you. Web link of the draft is as follows.

Any comments and suggestions are welcome.

Best regards
Gu Rong

发件人: internet-drafts@ietf.org <internet-drafts@ietf.org>
发送时间: 2016年3月17日 5:36
收件人: Chen Li; Rong Gu
主题: New Version Notification for draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt

A new version of I-D, draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt
has been successfully submitted by Rong Gu and posted to the
IETF repository.

Name:           draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn
Revision:       00
Title:          Decoupling scheme for hypervisor from SDN architecture
Document date:  2016-03-16
Group:          Individual Submission
Pages:          10
URL:            https://www.ietf.org/internet-drafts/draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00.txt
Status:         https://datatracker.ietf.org/doc/draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn/
Htmlized:       https://tools.ietf.org/html/draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00

   Different hypervisors are used in SDN network in cloud datacenters,
   such as KVM, VMware ESXi and Xen. However, different hypervisors are
   not well supported by SDN network to some degrees.  In order to solve
   the problems with hypervisor VMware ESXi and Xen, decoupling schemes
   for hypervisor from SDN architecture are presented.  Through
   different decoupling schemes, we want to find a better way in order
   to get the overall view by the SDN network.

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