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

"Susan Hares" <> Thu, 24 July 2014 14:15 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4FF0B1A0343 for <>; Thu, 24 Jul 2014 07:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kH3Ex6cP6i1e for <>; Thu, 24 Jul 2014 07:15:17 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1C2C11A035B for <>; Thu, 24 Jul 2014 07:15:15 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=;
From: Susan Hares <>
To: 'DIEGO LOPEZ GARCIA' <>, "'Y. Richard Yang'" <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Date: Thu, 24 Jul 2014 10:15:11 -0400
Message-ID: <010501cfa749$ae746ab0$0b5d4010$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0106_01CFA728.2765B0E0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQHW3qJ/Qxoju7WZpU2Z62WJkt0QZQGeKOhuAvy2AJgCDYYXVwGii+dFAi00kmObTRQmUA==
Cc:, 'Michael Tuexen' <>,
Subject: Re: [vnfpool] Follow-up question from the BOF
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Jul 2014 14:15:19 -0000

Diego and Richard:


As another supporter of including state management in scope, I support Richard’s proposal. 




From: vnfpool [] On Behalf Of DIEGO LOPEZ GARCIA
Sent: Thursday, July 24, 2014 10:06 AM
To: Y. Richard Yang
Cc:; Michael Tuexen;
Subject: Re: [vnfpool] Follow-up question from the BOF




As one of the supporters of the idea of not leaving state management out of scope, I am glad to see Richard's proposal and happy to support the idea of exploring a solution able to encompass vendor specific approaches.


Be goode,


On 24 Jul 2014, at 07:47 , Y. Richard Yang <> wrote:

Martin, Michael,

IPR concerns are valid, but if they are crucial to solve the problem, and the solution provides higher benefit, they could be addressed, right?

Regarding vendor specific solution, this is a very good point! Please take a look at approaches such as merge/split. They allow vendor specific packaging of NF state. Hence, transfers of state can be only among NFs of the same vendor. The advance, however, is that at least the controller can be different from the NF vendors. This is a good progress, in my view. Make sense?


On Jul 24, 2014 7:09 AM, "Michael Tuexen" <> wrote:

On 24 Jul 2014, at 06:54, Martin Stiemerling <> 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
>> (
>> 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
>  Martin
> _______________________________________________
> vnfpool mailing list

vnfpool mailing list


"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

Tel:    +34 913 129 041
Mobile: +34 682 051 091




Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição