Re: [vnfpool] comments on VNF Pool Charter

"Sood, Kapil" <kapil.sood@intel.com> Tue, 17 June 2014 22:44 UTC

Return-Path: <kapil.sood@intel.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 614BC1A019B for <vnfpool@ietfa.amsl.com>; Tue, 17 Jun 2014 15:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.551
X-Spam-Level:
X-Spam-Status: No, score=-7.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 XG12NvguNfY3 for <vnfpool@ietfa.amsl.com>; Tue, 17 Jun 2014 15:44:13 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7CDF91A0191 for <vnfpool@ietf.org>; Tue, 17 Jun 2014 15:44:13 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 17 Jun 2014 15:38:52 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.01,497,1400050800"; d="scan'208,217";a="530097755"
Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by orsmga001.jf.intel.com with ESMTP; 17 Jun 2014 15:44:12 -0700
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.23]) by ORSMSX103.amr.corp.intel.com ([169.254.2.248]) with mapi id 14.03.0123.003; Tue, 17 Jun 2014 15:44:12 -0700
From: "Sood, Kapil" <kapil.sood@intel.com>
To: Zongning <zongning@huawei.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: comments on VNF Pool Charter
Thread-Index: Ac+JinAslYIvEjumQV6cJDAK11QBoQAQ+BagACugqCA=
Date: Tue, 17 Jun 2014 22:44:11 +0000
Message-ID: <7B96B1DAA4CC63459FB0B17038C6A4744F966A35@ORSMSX102.amr.corp.intel.com>
References: <7B96B1DAA4CC63459FB0B17038C6A4744F9657D9@ORSMSX102.amr.corp.intel.com> <B0D29E0424F2DE47A0B36779EC66677966145C04@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B0D29E0424F2DE47A0B36779EC66677966145C04@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.22.254.140]
Content-Type: multipart/alternative; boundary="_000_7B96B1DAA4CC63459FB0B17038C6A4744F966A35ORSMSX102amrcor_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/nP0WQw01VG6jE3-k6s0qsCNorac
Subject: Re: [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 22:44:15 -0000

Hello Ning,

Thank you for your comments.  Please see below:

Best Regards,

Kapil.

From: Zongning [mailto:zongning@huawei.com]
Sent: Monday, June 16, 2014 7:16 PM
To: Sood, Kapil; vnfpool@ietf.org
Subject: 答复: comments on VNF Pool Charter

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.
[Kapil] ETSI-NFV has defined multiple use cases for NFV placements/migration that depends on the target NFVI (platform) conditions – e.g. available CPU, Memory, Network Capabilities, etc.  So, it makes sense to consider those requirements as we define this charter.  Please share what network information this group is looking to collect and what are the possible sources?  Those might not be too different from some of the VNFI information sources.


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.
[Kapil] OK, thanks.

Best Regards,

Kapil.

Hope my reply helps.

Thanks.

-Ning