[vnfpool] 答复: comments on VNF Pool Charter

Zongning <zongning@huawei.com> Tue, 17 June 2014 02:16 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: vnfpool@ietfa.amsl.com
Delivered-To: vnfpool@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481911A030B for <vnfpool@ietfa.amsl.com>; Mon, 16 Jun 2014 19:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.551
X-Spam-Level:
X-Spam-Status: No, score=-104.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 5sN-xBuP1XPZ for <vnfpool@ietfa.amsl.com>; Mon, 16 Jun 2014 19:16:50 -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 26AB31A02F6 for <vnfpool@ietf.org>; Mon, 16 Jun 2014 19:16:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFM72640; Tue, 17 Jun 2014 02:16:25 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Jun 2014 03:16:24 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Tue, 17 Jun 2014 10:16:18 +0800
From: Zongning <zongning@huawei.com>
To: "Sood, Kapil" <kapil.sood@intel.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: comments on VNF Pool Charter
Thread-Index: Ac+JinAslYIvEjumQV6cJDAK11QBoQAQ+Bag
Date: Tue, 17 Jun 2014 02:16:17 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677966145C04@nkgeml501-mbs.china.huawei.com>
References: <7B96B1DAA4CC63459FB0B17038C6A4744F9657D9@ORSMSX102.amr.corp.intel.com>
In-Reply-To: <7B96B1DAA4CC63459FB0B17038C6A4744F9657D9@ORSMSX102.amr.corp.intel.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.54]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC66677966145C04nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/oJTDixAaPWupsL1xf3yHkp4MGQ8
Subject: [vnfpool] 答复: comments on VNF Pool Charter
X-BeenThere: vnfpool@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <vnfpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vnfpool/>
List-Post: <mailto:vnfpool@ietf.org>
List-Help: <mailto:vnfpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 02:16:52 -0000

Hi, Kapil,

Thanks for the review. Please see inline.

Hello All,

A couple comments, maybe questions, on the VNF Charter:

1.      The point below indicates “to collect network information”…did you consider collecting the platform information as well?  I would suggest to add that.

[Ning] I’d think “platform information” may be too general term to be focused. In our charter, we collect network information for specific purpose, e.g., place a live and backup VNF instances into distributed physical locations, or locations without shared risk in the network. Could you please elaborate more on the purpose of using any specific piece of platform information, or give some use cases? We could then think about how to make it more focused, as required by the charter.


2.      Please clarify the scope of the protocols work within the charter.  Current text says “re-chartering before adopting any work to develop new, or extend existing, protocols”.  But, it also says that group will work on 2 protocols.

[Ning] Current charter lists a set of interfaces/protocols to be standardized, but will only delivers documents such as requirements to these interfaces/protocols, and architecture highlighting the functionalities of these interfaces/protocols. The protocol development, i.e., specifying on-the-wire message format, will be after the re-chartering.

Best Regards,

Kapil.

Hope my reply helps.

Thanks.

-Ning