Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt

"Susan Hares" <shares@ndzh.com> Wed, 15 January 2014 04:47 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 9D0861AE2B8 for <vnfpool@ietfa.amsl.com>; Tue, 14 Jan 2014 20:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 l66dPEcS74dr for <vnfpool@ietfa.amsl.com>; Tue, 14 Jan 2014 20:47:07 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA081AE2B2 for <vnfpool@ietf.org>; Tue, 14 Jan 2014 20:47:07 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=64.112.195.202;
From: "Susan Hares" <shares@ndzh.com>
To: "'Melinda Shore'" <melinda.shore@nomountain.net>, <vnfpool@ietf.org>
References: <B0D29E0424F2DE47A0B36779EC66677925866ACB@nkgeml501-mbs.china.huawei.com> <00b701cf116e$a0386940$e0a93bc0$@ndzh.com> <B0D29E0424F2DE47A0B36779EC66677925867072@nkgeml501-mbs.china.huawei.com> <009b01cf11a2$86ccb310$94661930$@ndzh.com> <52D60FC0.4080302@nomountain.net>
In-Reply-To: <52D60FC0.4080302@nomountain.net>
Date: Tue, 14 Jan 2014 23:46:47 -0500
Message-ID: <00f601cf11ac$cd0026a0$670073e0$@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: AQKO3sLtjaMIetI/q7gvl2/3BVETXgGNaT15AKEFDJABS799rQFTCSScmN8vtIA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Subject: Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt
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, 15 Jan 2014 04:47:08 -0000

Melinda:

Thank you for accepting my suggestion on the VNF Set information. 

I agree that it is too early to setting on a state-synchronization method or
a data model.  My question was intended to again probe the scope of the
problem to help me revise a use case draft I am working on.

The use cases within a financial world or mobile phone application systems
that back-end to VNFs systems (to perform spam filtering, DPI, or other
specific applications), will need the rapid failover.  Certain institutions
may be willing to pay for the systems that do more state synchronization and
less queries for VNF placement.  

So, with explanation may I conclude that a description of these use case fit
within the VNF Pool operation. 

If I'm unclear, please ask questions.  Our discussions work to clarify the
work. 

Sue 


-----Original Message-----
From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Tuesday, January 14, 2014 11:34 PM
To: vnfpool@ietf.org
Subject: Re: [vnfpool] FW: New Version Notification for
draft-zong-vnfpool-problem-statement-02.txt

Hi, Sue:

Thanks for continuing to review this document.  I do think that we could be
clearer about what a "set" is and what characteristics it has, and that's
something we'll work on for the next revision.

In terms of state synchronization I feel pretty strongly that it's premature
to be describing a data model.  Discussing, yes, and possibly starting to
work through, but I'd be really reluctant to commit to paper (or electrons)
in the absence of an architecture.  I certainly think we need to be talking
about metadata, first, since the functions we're talking about span a wide
range of technologies and consequently may have varying requirements.  I
think we don't have enough of a handle on the specifics of what we're doing
to do much beyond, perhaps, data structures.

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