IETF Logo Mail Archive

Re: [vnfpool] new VNFPool draft charter

Melinda Shore <melinda.shore@nomountain.net> Tue, 03 June 2014 22:36 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 37B871A01B6 for <vnfpool@ietfa.amsl.com>; Tue, 3 Jun 2014 15:36:03 -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 qyOPVqPzgQld for <vnfpool@ietfa.amsl.com>; Tue, 3 Jun 2014 15:36:01 -0700 (PDT)
Received: from homiemail-a49.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D3B6A1A000B for <vnfpool@ietf.org>; Tue, 3 Jun 2014 15:36:01 -0700 (PDT)
Received: from homiemail-a49.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a49.g.dreamhost.com (Postfix) with ESMTP id 41E502000420D for <vnfpool@ietf.org>; Tue, 3 Jun 2014 15:35:56 -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=KoQK2RwB2wIDShgsC0ixYetHgo8=; b=lMU2xZegzNkZr pQb62gTILstndSmwJ7JzilzDMh6paX9T4XQHtQ3tmz7n8oV9fCNo+eeLwULJFREY kZ0au4cUwCGKEvi7HOSwypBbGizvoEPSdU21kKBmay6Bq5VCvtO5xYvU5o2keJaZ +8RcVQag3bFR9uVhCxtziNgG9cPUUQ=
Received: from spandex.local (63-140-85-79.nwc.dsl.dynamic.acsalaska.net [63.140.85.79]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: melinda.shore@nomountain.net) by homiemail-a49.g.dreamhost.com (Postfix) with ESMTPSA id ED82D20024944 for <vnfpool@ietf.org>; Tue, 3 Jun 2014 15:35:55 -0700 (PDT)
Message-ID: <538E4DCA.8040004@nomountain.net>
Date: Tue, 03 Jun 2014 14:35:54 -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>
In-Reply-To: <58B76DBD-F67D-45AC-850B-BDBC67A2443B@tid.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/4r6t7nmHhpOuUNiPBO1597JyJ8c
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: Tue, 03 Jun 2014 22:36:03 -0000

On 6/3/14 2:23 PM, Diego R. Lopez wrote:
> Hi,
> 
> It looks really good to me, Ning!
> 
> I am just wondering whether we could give state synchronization a 
> special category (of being "out of scope in this phase" or similar) 
> because I think it is a extremely relevant issue.

This is an extremely contested question.  It seems appropriate to me
to view vnfpool as a layered mechanism, where a layer handling the
reliability/redundancy mechanism may carry other traffic, but that
traffic is opaque to the pooling mechanism.  That traffic might
include service state.  But, this is my second go-'round on state
transfer (third, if you include sami, the first one being rserpool
itself) and I really think it's best to be left out of scope with
no specific future plans for the time being, but to allow a generic
transport mechanism in the pooling traffic.

Melinda


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

"Software longa, hardware brevis."

v2.8.7 | Report a Bug | By Email