Re: [vnfpool] new VNFPool draft charter

"King, Daniel" <d.king@lancaster.ac.uk> Wed, 04 June 2014 21:27 UTC

Return-Path: <d.king@lancaster.ac.uk>
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 3A03F1A032B for <vnfpool@ietfa.amsl.com>; Wed, 4 Jun 2014 14:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 GfQjVewO5Z4Z for <vnfpool@ietfa.amsl.com>; Wed, 4 Jun 2014 14:27:44 -0700 (PDT)
Received: from sideburn.lancs.ac.uk (sideburn.lancs.ac.uk [148.88.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 06FCA1A0309 for <vnfpool@ietf.org>; Wed, 4 Jun 2014 14:27:44 -0700 (PDT)
Received: from ex-0-ht0.lancs.ac.uk ([10.42.18.47] helo=EX-0-HT0.lancs.local) by sideburn.lancs.ac.uk with esmtp (Exim 4.72) (envelope-from <d.king@lancaster.ac.uk>) id 1WsIif-0004QO-4M for vnfpool@ietf.org; Wed, 04 Jun 2014 22:27:37 +0100
Received: from EX-0-MB2.lancs.local ([fe80::9d98:936b:54d1:c531]) by EX-0-HT0.lancs.local ([fe80::7d10:114a:53b0:7f2f%12]) with mapi id 14.03.0174.001; Wed, 4 Jun 2014 22:27:36 +0100
From: "King, Daniel" <d.king@lancaster.ac.uk>
To: "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: new VNFPool draft charter
Thread-Index: AQFwGVvugwpODgVrmfjspyYPiWDwQ5wgOpuQ
Date: Wed, 04 Jun 2014 21:27:36 +0000
Message-ID: <65174429B5AF4C45BD0798810EC48E0A3234ED45@EX-0-MB2.lancs.local>
References: <B0D29E0424F2DE47A0B36779EC6667796614030A@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B0D29E0424F2DE47A0B36779EC6667796614030A@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [88.97.23.122]
x-iss-local-domain: 1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/rSKcc1ZLCRm7G65g7J_9O8ggWSk
Subject: Re: [vnfpool] new VNFPool draft 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: Wed, 04 Jun 2014 21:27:46 -0000

Hi All, 

Thanks Ning and Melinda for the draft charter text, overall the direction and work items look great to me. 

Still, being overly opinionated, I do have a few comments:

Charter Text
- Maybe break existing bullet, into two bullets (and minor grammar fix - "the Pool Manager": 

o Analysis of pooling security characteristics and requirements to identify and mitigate threats against the pooling mechanism. 
o Identification of an appropriate trust model between pool members, and between pool members and the Pool Manager.

- Also, does Trust imply Policy, or vice versa?     

- Adding [secure] as requirement in the transport protocol selection. Or maybe I am predetermining the protocol requirements, but then again we already state "reliable" mechanism:

o Investigate and select a [secure] and reliable transport protocol, such as MPTCP and SCTP, for delivery of the messages associated with the redundancy management within a VNF Pool.

Charter Milestones
- Perhaps specify a security should be investigated along with manageability in the following milestone:

"August 2015 - Submit VNFPool Requirements, including the manageability and security of VNF Pools to the IESG for publication as an Informational document."

- Slight clean up (grammar and adding the word "document") on the charter milestones, these would become (note the inclusion of "security"):

December 2014 - Submit VNFPool Problem Statement to IESG for publication as an Informational document.
April 2015 - Submit VNFPool Use Cases to IESG for publication as an Informational document.
August 2015 - Submit VNFPool Requirements, including the manageability and security of VNF Pools to the IESG for publication as an Informational document.
August 2015 - Submit VNFPool Architecture to IESG for publication as a Proposed Standard
December 2015 - Submit Applicability and Gap Analysis of RSerPool to IESG for publication as Informational document.

Spelling NITs in Charter Text
- "Conceptionally" to "Conceptually"
- " envisoned " to "envisioned"

Br, Dan.