Re: [vnfpool] Follow-up question from the BOF

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Thu, 24 July 2014 11:09 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 4567B1A01FF for <vnfpool@ietfa.amsl.com>; Thu, 24 Jul 2014 04:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level:
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] 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 PgNMuCQFFo7F for <vnfpool@ietfa.amsl.com>; Thu, 24 Jul 2014 04:09:47 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E98F1A01EB for <vnfpool@ietf.org>; Thu, 24 Jul 2014 04:09:47 -0700 (PDT)
Received: from dhcp-8cb4.meeting.ietf.org (dhcp-8cb4.meeting.ietf.org [31.133.140.180]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 1124E1C104E6A; Thu, 24 Jul 2014 13:09:43 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <53D0E5F1.9060503@gmail.com>
Date: Thu, 24 Jul 2014 07:09:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F65D00A4-4D37-44A0-9416-F76BFF018BC8@lurchi.franken.de>
References: <53CEC61A.9010104@gmail.com> <CANUuoLof21jpfA8nvktVCusuWmAsWSO8b0yMzVVwjOOwVoqDtw@mail.gmail.com> <53D0E5F1.9060503@gmail.com>
To: Martin Stiemerling <mls.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/jmeJVfQb6O1UtAs-KcVolqJdF4Q
Cc: "vnfpool@ietf.org" <vnfpool@ietf.org>, "Y. Richard Yang" <yry@cs.yale.edu>
Subject: Re: [vnfpool] Follow-up question from the BOF
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, 24 Jul 2014 11:09:52 -0000

On 24 Jul 2014, at 06:54, Martin Stiemerling <mls.ietf@gmail.com> wrote:

> Hi Richard,
> 
> Am 22.07.14 um 17:34 schrieb Y. Richard Yang:
>> Hi Martin,
>> 
>> Here is one point. One constraint of the proposed work, in my view, is
>> that the scope does not consider state management. Most useful NFs are
>> stateful. Hence, removing state management from the scope is not ideal,
>> and hence is a limit. There is interesting recent progress in generic,
>> reusable NF state management, such as Merge/Split
>> (https://www.usenix.org/system/files/conference/nsdi13/nsdi13-final205.pdf).
>> If this is included, I believe that the group can develop a lot more
>> more solutions.
> 
> state management is an interesting topic, but there has been explicit community feedback during the first bof that this is not something the potential wg should be working on, as this is very vendor specific.
... and there are most likely a lot IPRs... That was one of the reasons
state sharing was excluded from the scope of RSerPool...

Best regards
Michael
> 
>  Martin
> 
> _______________________________________________
> vnfpool mailing list
> vnfpool@ietf.org
> https://www.ietf.org/mailman/listinfo/vnfpool
>