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

Melinda Shore <melinda.shore@nomountain.net> Wed, 15 January 2014 04:34 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 94DA01AE1BE for <vnfpool@ietfa.amsl.com>; Tue, 14 Jan 2014 20:34:24 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 aw5CBwGh1GPS for <vnfpool@ietfa.amsl.com>; Tue, 14 Jan 2014 20:34:22 -0800 (PST)
Received: from homiemail-a66.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id D43FD1AE1CA for <vnfpool@ietf.org>; Tue, 14 Jan 2014 20:34:22 -0800 (PST)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id 4E948350078 for <vnfpool@ietf.org>; Tue, 14 Jan 2014 20:34:11 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=nomountain.net; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=nomountain.net ; b=d1CyfKntoOrYdC9GVvyMnndzirkLsSiqPEdQc43p4jPGUfkZZl+PW9GJtacc qLip1HNRTxz4VWBXouGZ4Fz5TgJf6i5NDyCE4A0VUxGCt7T/PCZR7QuCID64kN2A sOMrYHO81bqvtAfIRUzKx7KuNv5XG8hKblLeHkZ8V+3rLVs=
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=THEXVLN4MD4bcx7AlWwPDB+a1jo=; b=Z0wUW1VSEF4VM /Yyy9/vqO74ywei2sZMIdhRZgVfGutzs7CR4jSkYGZccPRmTWoAOElvLp3sSLyJ/ ahRNw2Xn6X+CmWVnTjwxz79Kq/Gtu9GwGhAGN7KiEutPCwiNJgQYDGgL8st4bEcf 89kBdWt5rscu54vr0MoxdHVWAfZQP0=
Received: from spandex.local (209-112-136-197-rb1.nwc.dsl.dynamic.acsalaska.net [209.112.136.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: melinda.shore@nomountain.net) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id 000BB350058 for <vnfpool@ietf.org>; Tue, 14 Jan 2014 20:34:10 -0800 (PST)
Message-ID: <52D60FC0.4080302@nomountain.net>
Date: Tue, 14 Jan 2014 19:34:08 -0900
From: Melinda Shore <melinda.shore@nomountain.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: 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>
In-Reply-To: <009b01cf11a2$86ccb310$94661930$@ndzh.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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:34:24 -0000

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