Re: [vnfpool] comments on VNF Pool Charter

Melinda Shore <melinda.shore@gmail.com> Fri, 20 June 2014 07:00 UTC

Return-Path: <melinda.shore@gmail.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 2DE191B278C for <vnfpool@ietfa.amsl.com>; Fri, 20 Jun 2014 00:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 LU3gYHLSWUEJ for <vnfpool@ietfa.amsl.com>; Fri, 20 Jun 2014 00:00:48 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C3141AD6B1 for <vnfpool@ietf.org>; Fri, 20 Jun 2014 00:00:48 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y10so2651984pdj.19 for <vnfpool@ietf.org>; Fri, 20 Jun 2014 00:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=OuwG+eKiR/JMHBHDcNH9xTpVXw1c7u6yw5JAafH4Bps=; b=awAzpKajBivINYtuzZ2LKVPCR0r+KhkdkNHT/IkhL4MNO9vi2Ky+osZTGhbEeNLdLQ xofe+PakZD8DIgeGdD6YFDp6K8b7N47j0DV+jBk2UvGwE06tg6aRPtVrpvy8X37Fo3l/ QhhP6hohugLwneb0Qs4r7uNuI6jmuDtt4OV0bsFT1BoOjFG6aV9dyactUwvGiO6U1nXR c4h2786cG0AgS/CIqi3wmodp0NVl1dxzgcgCJmfbd3yyJtRg7qxYTWojCikvIqDH4Wwa PZiJf3mEoHBgwgrN9FUE84FBl8pKp1+8CwVmAEoX8NMQV3X7VAubfchu42/ieLYwVuF0 rVpw==
X-Received: by 10.66.146.105 with SMTP id tb9mr2106799pab.157.1403247648051; Fri, 20 Jun 2014 00:00:48 -0700 (PDT)
Received: from spandex.local (216-67-27-62-rb2.nwc.dsl.dynamic.acsalaska.net. [216.67.27.62]) by mx.google.com with ESMTPSA id gg4sm2019972pbb.12.2014.06.20.00.00.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Jun 2014 00:00:47 -0700 (PDT)
Message-ID: <53A3DC1C.4070908@gmail.com>
Date: Thu, 19 Jun 2014 23:00:44 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Sood, Kapil" <kapil.sood@intel.com>, Zongning <zongning@huawei.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
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>
In-Reply-To: <7B96B1DAA4CC63459FB0B17038C6A4744F968F00@ORSMSX102.amr.corp.intel.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/nAui9SBCYbqgHZXq-wlE-RYu_7k
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 07:00:50 -0000

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