Re: [NFVCON] a side meeting @ IETF 89

Thomas Nadeau <tnadeau@lucidvision.com> Mon, 24 February 2014 14:15 UTC

Return-Path: <tnadeau@lucidvision.com>
X-Original-To: nfvcon@ietfa.amsl.com
Delivered-To: nfvcon@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC0F31A0872 for <nfvcon@ietfa.amsl.com>; Mon, 24 Feb 2014 06:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level:
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547] 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 dxB3u93rGPyg for <nfvcon@ietfa.amsl.com>; Mon, 24 Feb 2014 06:15:11 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 339641A086A for <nfvcon@ietf.org>; Mon, 24 Feb 2014 06:15:11 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 821272703AA9; Mon, 24 Feb 2014 09:15:10 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_2F7A72BE-6956-4BAC-8FA8-2D2590DD88E8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <E4DE949E6CE3E34993A2FF8AE79131F8290080@DEMUMBX005.nsn-intra.net>
Date: Mon, 24 Feb 2014 09:15:09 -0500
Message-Id: <FA1A9BC2-7FB3-4F72-A599-DA6DBEF3D17F@lucidvision.com>
References: <E33E01DFD5BEA24B9F3F18671078951F2482E117@nkgeml501-mbs.china.huawei.com> <77748736-91BD-4207-8C25-B304FB44308B@lucidvision.com> <53061E3F.4040200@gmail.com> <E33E01DFD5BEA24B9F3F18671078951F2482E436@nkgeml501-mbs.china.huawei.com> <0F95A18E-04EF-4382-B4E3-2815D89B7FF7@tid.es> <E4DE949E6CE3E34993A2FF8AE79131F8290080@DEMUMBX005.nsn-intra.net>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/nfvcon/P7wq8VqD2koV854xerC5_WnqPvA
Cc: "Songhaibin \(A\)" <haibin.song@huawei.com>, "ext Diego R. Lopez" <diego@tid.es>, "nfvcon@ietf.org" <nfvcon@ietf.org>, Melinda Shore <melinda.shore@gmail.com>, ext Andy Bierman <andy@yumaworks.com>
Subject: Re: [NFVCON] a side meeting @ IETF 89
X-BeenThere: nfvcon@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "NFV \(Network Function Virtualization\) Configuration and Modeling" <nfvcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfvcon/>
List-Post: <mailto:nfvcon@ietf.org>
List-Help: <mailto:nfvcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 14:15:13 -0000

On Feb 23, 2014:10:05 AM, at 10:05 AM, Ersue, Mehmet (NSN - DE/Munich) <mehmet.ersue@nsn.com>; wrote:

> Dear Diego, All,
> 
> NETCONF is well-prepared for addressing function configuration on diverse reference points of the NFV architecture.
> The new interface descriptions in ETSI NFV use a producer/consumer paradigm and the interface can be re-exposed practically by any entity.
> RESTCONF would be perfect in such an environment as it can support HTML-based REST-like configuration.

	Take a look at opendaylight.org. We already have a working implementation of a RestConf interface working on the controller as part of the first release (hydrogen) that talks to a variety of routers and switches (real and virtual). 

	--Tom



> Haibin: I would be available through the week, except on Monday.
> 
> Cheers, 
> Mehmet 
> 
>> -----Original Message-----
>> From: NFVCON [mailto:nfvcon-bounces@ietf.org] On Behalf Of ext Diego R.
>> Lopez
>> Sent: Sunday, February 23, 2014 12:41 AM
>> To: Songhaibin (A)
>> Cc: Melinda Shore; nfvcon@ietf.org
>> Subject: Re: [NFVCON] a side meeting @ IETF 89
>> 
>> Hi,
>> 
>> You know I was skeptical about this initiative, but I must say I am
>> starting to see some potential areas of application of specific NFV
>> configuration aspects, at least in what relates to defining properties
>> of the VNF Forwarding Graph (what has some interesting challenges
>> regarding how you deal with dynamic graphs in the interaction of the
>> VNFs with the infrastructure) and the attachment points of a
>> virtualized service. Furthermore, if we could move in the direction of
>> prescribing a single method for dealing with function configuration
>> (NETCONF based, I'd say) it would be a great step.
>> 
>> I guess one of the key things we need to decide is what are the
>> reference points to be addressed in the NFV architectural framework.
>> 
>> Be goode,
>> 
>> On 21 Feb 2014, at 03:39 , Songhaibin (A) <haibin.song@huawei.com>;
>> wrote:
>> 
>>> Hi Tom and Melinda,
>>> 
>>> Thank you for the advice. Substantial progress is most important, and
>> for IETF, it mostly means drafts. Let's see whether we can put some
>> substantial drafts on the table soon after the upcoming IETF meeting.
>>> 
>>> And yes, identifying a issue is indeed needed. NFV Configuration
>> covers a wide range. But if we look at the requirements for
>> provisioning a VNF service, or a VNF graph service , that should be
>> narrow.
>>> 
>>> Best Regards!
>>> -Haibin
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: NFVCON [mailto:nfvcon-bounces@ietf.org] On Behalf Of Melinda
>> Shore
>>>> Sent: Thursday, February 20, 2014 11:25 PM
>>>> To: nfvcon@ietf.org
>>>> Subject: Re: [NFVCON] a side meeting @ IETF 89
>>>> 
>>>> On 2/20/14 5:01 AM, Thomas Nadeau wrote:
>>>>> Let me suggest you consider coming to the Ops Area, NetMod and
>> NetConf
>>>>> to discuss configuration issues and related data models. *)
>>>> 
>>>> This work got time on the agenda at opsawg at IETF 88 and there's
>> been little
>>>> discussion since.  I do think that it's possible to make substantial
>> progress
>>>> without meeting in person, and that it would be worthwhile to take
>> some time
>>>> before the meeting to identify an issues that need resolution or
>> that would
>>>> benefit from face-to- face discussion.
>>>> 
>>>> Melinda
>>>> 
>>>> _______________________________________________
>>>> NFVCON mailing list
>>>> NFVCON@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/nfvcon
>>> 
>>> _______________________________________________
>>> NFVCON mailing list
>>> NFVCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nfvcon
>> 
>> 
>> --
>> "Esta vez no fallaremos, Doctor Infierno"
>> 
>> Dr Diego R. Lopez
>> Telefonica I+D
>> http://people.tid.es/diego.lopez/
>> 
>> e-mail: diego@tid.es
>> Tel:    +34 913 129 041
>> Mobile: +34 682 051 091
>> -----------------------------------------
>> 
>> 
>> ________________________________
>> 
>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> consultar nuestra política de envío y recepción de correo electrónico
>> en el enlace situado más abajo.
>> This message is intended exclusively for its addressee. We only send
>> and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> _______________________________________________
>> NFVCON mailing list
>> NFVCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfvcon
> _______________________________________________
> NFVCON mailing list
> NFVCON@ietf.org
> https://www.ietf.org/mailman/listinfo/nfvcon