Re: [vnfpool] new VNFPool draft charter

Melinda Shore <melinda.shore@nomountain.net> Thu, 05 June 2014 21:03 UTC

Return-Path: <melinda.shore@nomountain.net>
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 5DEA31A02CC for <vnfpool@ietfa.amsl.com>; Thu, 5 Jun 2014 14:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 rbAWtcw1n6Li for <vnfpool@ietfa.amsl.com>; Thu, 5 Jun 2014 14:03:06 -0700 (PDT)
Received: from homiemail-a63.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id C5B961A0126 for <vnfpool@ietf.org>; Thu, 5 Jun 2014 14:03:06 -0700 (PDT)
Received: from homiemail-a63.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTP id 65B692F4060 for <vnfpool@ietf.org>; Thu, 5 Jun 2014 14:03:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nomountain.net; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= nomountain.net; bh=/1EQcABb6PKaNwA69qoCfGjJUT4=; b=E2sz8VpeFLnm5 s7CqzwDCY2GiOV+rFY/eV0Z+cXlFiiz7HxNqSejb6q7kSMsMbgljdfWo0hoEFYcK w7KkJ0BmTWjfhjbxDseXWqMNRulgDmn9HYnee4AZ7vo5+FMw8zFSxvetHHdJWYUn DPgTKQXXU+vL/IaebAjCwWwenSgVgg=
Received: from spandex.local (63-140-85-79.nwc.dsl.dynamic.acsalaska.net [63.140.85.79]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: melinda.shore@nomountain.net) by homiemail-a63.g.dreamhost.com (Postfix) with ESMTPSA id 16D0C2F4059 for <vnfpool@ietf.org>; Thu, 5 Jun 2014 14:02:59 -0700 (PDT)
Message-ID: <5390DB02.6010202@nomountain.net>
Date: Thu, 05 Jun 2014 13:02:58 -0800
From: Melinda Shore <melinda.shore@nomountain.net>
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: vnfpool@ietf.org
References: <B0D29E0424F2DE47A0B36779EC6667796613FC41@nkgeml501-mbs.china.huawei.com> <58B76DBD-F67D-45AC-850B-BDBC67A2443B@tid.es> <538E4DCA.8040004@nomountain.net> <011101cf80fe$f0c22ea0$d2468be0$@ndzh.com>
In-Reply-To: <011101cf80fe$f0c22ea0$d2468be0$@ndzh.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/s62DTaT931AIboPBLIHq1tuHucI
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: Thu, 05 Jun 2014 21:03:07 -0000

On 6/5/14 12:44 PM, Susan Hares wrote:
> Melinda:
> 
> If we leave it scope for this phase,  but open for some future phase I think
> it will help the discussion.  This will allows to build toward this phase.
> Of course, I'm coming from the router/SDN platform view point. 

I think it will help among people who'd like to use it but
hurt us politically, to be frank - this is an issue that always
raises a lot of ire in the quarter of the IETF in which we're
now operating.  We'd also be faced with the difficult of answering
the question of why a vendor would want a customer to be able to fail,
say, their firewall over to another vendor's firewall.  The obvious
answer to that is that customers want it, but that doesn't mean
that vendors will implement that kind of mechanism, and when we've
done polls about this kind of thing we haven't been able to get
any vendor to say they'd do it.  So, if people really want to
include text saying that this is future work, by all means do so
but do so with knowledge of how discussions have gone in the very
recent past.

And to be clear, to say that it's out of scope means that it's out of
scope *now* - as we know all decisions may be revisited in the
future.

Melinda

-- 
Melinda Shore
No Mountain Software
melinda.shore@nomountain.net

"Software longa, hardware brevis."