Re: [vnfpool] new VNFPool draft charter

"Susan Hares" <shares@ndzh.com> Thu, 05 June 2014 21:19 UTC

Return-Path: <shares@ndzh.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 E4EBC1A0334 for <vnfpool@ietfa.amsl.com>; Thu, 5 Jun 2014 14:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.345
X-Spam-Level: **
X-Spam-Status: No, score=2.345 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DOS_OUTLOOK_TO_MX=2.845] 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 A0eG1oNgDztv for <vnfpool@ietfa.amsl.com>; Thu, 5 Jun 2014 14:19:09 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5D01E1A0325 for <vnfpool@ietf.org>; Thu, 5 Jun 2014 14:19:09 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.189.161;
From: "Susan Hares" <shares@ndzh.com>
To: "'Melinda Shore'" <melinda.shore@nomountain.net>, <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> <5390DB02.6010202@nomountain.net>
In-Reply-To: <5390DB02.6010202@nomountain.net>
Date: Thu, 5 Jun 2014 17:18:59 -0400
Message-ID: <013901cf8103$c463bef0$4d2b3cd0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHEnxnLhmHu94KlDv9FDMBQ6pt93gIdkVqVAhnOl7oBhAKLngHXoWPLmzwwi1A=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/EOkUsmp2wpuyAHUPUmwmsoxkygI
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:19:11 -0000

Melinda:

If it is a layer 9 issue (politics) to get the work started, then it out of
scope. I really just want to get going on this work. 

Sue 

-----Original Message-----
From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Thursday, June 05, 2014 5:03 PM
To: vnfpool@ietf.org
Subject: Re: [vnfpool] new VNFPool draft charter

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."

_______________________________________________
vnfpool mailing list
vnfpool@ietf.org
https://www.ietf.org/mailman/listinfo/vnfpool