Re: [vnfpool] comments on VNF Pool Charter

"Sood, Kapil" <kapil.sood@intel.com> Fri, 20 June 2014 17:52 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 A1F7C1B288C for <vnfpool@ietfa.amsl.com>; Fri, 20 Jun 2014 10:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Level:
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 IVf82T873bKG for <vnfpool@ietfa.amsl.com>; Fri, 20 Jun 2014 10:52:55 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by ietfa.amsl.com (Postfix) with ESMTP id A51C21B2891 for <vnfpool@ietf.org>; Fri, 20 Jun 2014 10:52:55 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 20 Jun 2014 10:47:33 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.01,515,1400050800"; d="scan'208";a="531663762"
Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by orsmga001.jf.intel.com with ESMTP; 20 Jun 2014 10:52:54 -0700
Received: from orsmsx102.amr.corp.intel.com ([169.254.1.23]) by ORSMSX105.amr.corp.intel.com ([169.254.4.10]) with mapi id 14.03.0123.003; Fri, 20 Jun 2014 10:52:54 -0700
From: "Sood, Kapil" <kapil.sood@intel.com>
To: Melinda Shore <melinda.shore@gmail.com>, Zongning <zongning@huawei.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: [vnfpool] comments on VNF Pool Charter
Thread-Index: Ac+JinAslYIvEjumQV6cJDAK11QBoQAQ+BagACugqCAABVSx8ABtBLFgABJznQAACAL1sA==
Date: Fri, 20 Jun 2014 17:52:53 +0000
Message-ID: <7B96B1DAA4CC63459FB0B17038C6A4744F969606@ORSMSX102.amr.corp.intel.com>
References: <7B96B1DAA4CC63459FB0B17038C6A4744F9657D9@ORSMSX102.amr.corp.intel.com> <B0D29E0424F2DE47A0B36779EC66677966145C04@nkgeml501-mbs.china.huawei.com> <7B96B1DAA4CC63459FB0B17038C6A4744F966A35@ORSMSX102.amr.corp.intel.com> <B0D29E0424F2DE47A0B36779EC66677966145F2E@nkgeml501-mbs.china.huawei.com> <7B96B1DAA4CC63459FB0B17038C6A4744F968F00@ORSMSX102.amr.corp.intel.com> <53A3DC1C.4070908@gmail.com>
In-Reply-To: <53A3DC1C.4070908@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.22.254.138]
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/1-LqpFpoZZfEh6Ipj6XrxY39spg
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: Fri, 20 Jun 2014 17:52:59 -0000

Thank you, Melinda.  This helps.  I am just joining the discussion, so just understanding context. 

Best Regards,

Kapil.

-----Original Message-----
From: Melinda Shore [mailto:melinda.shore@gmail.com] 
Sent: Friday, June 20, 2014 12:01 AM
To: Sood, Kapil; Zongning; vnfpool@ietf.org
Subject: Re: [vnfpool] comments on VNF Pool Charter

On 6/19/14 9:17 PM, Sood, Kapil wrote:
> [Kapil] Well, I believe there will be many cases where the VIM/VNFM 
> will need to determine the infrastructure conditions, even for SBY/ACT 
> placements,  so I agree your suggestion to add appropriate text to the 
> charter questions.

Hi, Kapil: at this point in the process we're trying to identify the questions that a working group, should it be chartered, will address, and it seems to me that at this time we're probably more concerned with how to define the question so that it's something we can answer - that is to say, we need to identify which pieces of information will need to be used as the basis for a failover, as well as which pieces of information will need to be transferred or replicated.  (As a side note it's pretty clear that we'll need to identify what's coupled with and dependent on ETSI NFV vs.
what's coupled with and dependent on IETF sfc).

> I do have a follow-up question on the contents of the specific images, 
> more specifically live state including any secrets or sensitive 
> information protection.  Is the charter dealing with the security 
> aspects, too?

Yes, any work undertaken in the IETF needs to address security issues (including privacy), and that's one of our higher-priority concerns given the sensitivity of network state and potentially very serious problems around service state.  We've got people with security expertise involved right now, and may choose to exercise the option of early security review as the documents progress.

Melinda