Re: [vnfpool] State management


Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0F2791A005C for <>; Sun, 27 Jul 2014 23:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R8qCPYsRWwrG for <>; Sun, 27 Jul 2014 23:01:25 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B0ECE1A0233 for <>; Sun, 27 Jul 2014 23:01:22 -0700 (PDT)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 2CB41370093 for <>; Mon, 28 Jul 2014 08:01:19 +0200 (CEST)
Received: from (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0F51837008F for <>; Mon, 28 Jul 2014 08:01:19 +0200 (CEST)
Received: from ([fe80::b818:3976:1351:7896]) by ([fe80::18d2:792c:5932:894c%16]) with mapi id 14.03.0146.002; Mon, 28 Jul 2014 08:01:18 +0200
To: "" <>
Thread-Topic: [vnfpool] State management
Thread-Index: Ac+oVZenuSdQzK7FTsCQOip43tv5wwB07heA
Date: Mon, 28 Jul 2014 06:01:17 +0000
Message-ID: <>
References: <06be01cfa855$9bd1acd0$d3750670$>
In-Reply-To: <06be01cfa855$9bd1acd0$d3750670$>
Accept-Language: es-ES, es-ES, en-US
Content-Language: es-ES
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [vnfpool] State management
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: Mon, 28 Jul 2014 06:01:37 -0000

PS: please note my new email address below. Mails to my old emails
will only be forwarded for a limited period of time
Dr. Pedro A. Aranda Gutiérrez

Technology Exploration -
Network Innovation & Virtualisation

mailto:pedroa.aranda@t <>
Telefónica, Investigación y Desarrollo
C/ D. Ramón de la Cruz,84
28006 Madrid, Spain

Fragen sind nicht da, um beantwortet zu werden.
Fragen sind da, um gestellt zu werden.
Georg Kreisler

El 26/07/14 00:13, "Adrian Farrel" <> escribió:

>I completely understand why people want to work on state management: it
>is a hugely interesting and hard problem, and a lot of fun. But...
>- Learn to walk before you try to run
>- Not doing state management in the first pass at IETF work on this topic
>   does not preclude doing the research in your own labs and bring the
>   ideas to the IETF
>- Draw a distinction between learned/derived state and programmed state.
>   The former is complex to synchronise. The latter is centrally
>controlled and
>   easy to synchronise/manage. I would argue the latter is automagically
>   scope, but is not really "synchronisation", just parallel
>- Don't assume that you can derive a generic solution for synchronising
>   dynamic state across a whole set of different classes of virtual
>And lastly, the question Martin asked interests me:
>"Why do people are not convinced that the technical problem is solveable?"
>The answer so far seems to be to a different question (e.g. "What else
>would you like to see in scope to make the problem interesting or more
>applicable to your deployment models?"). It is fine to answer that
>question and discuss the charter (although in my opinion trying to put
>state synchronisation in from day one will completely turn this from a
>real problem for rapid deployment into a research topic for many years).
>I would *really* like to hear whether there is an answer to Martin's
>question, or did the people who hummed also hum to the wrong question?
>vnfpool mailing list


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