Re: [NFVCON] a side meeting @ IETF 89

[Thomas Nadeau <[e-mail]>]

On Feb 23, 2014:10:05 AM, at 10:05 AM, Ersue, Mehmet (NSN - DE/Munich) <[e-mail]> 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:[e-mail]] On Behalf Of ext Diego R.
>> Lopez
>> Sent: Sunday, February 23, 2014 12:41 AM
>> To: Songhaibin (A)
>> Cc: Melinda Shore; [e-mail]
>> 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) <[e-mail]>
>> 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:[e-mail]] On Behalf Of Melinda
>> Shore
>>>> Sent: Thursday, February 20, 2014 11:25 PM
>>>> To: [e-mail]
>>>> 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
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/nfvcon
>>> 
>>> _______________________________________________
>>> NFVCON mailing list
>>> [e-mail]
>>> 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: [e-mail]
>> Tel:    [phone]
>> Mobile: [phone]
>> -----------------------------------------
>> 
>> 
>> ________________________________
>> 
>> 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
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/nfvcon
> _______________________________________________
> NFVCON mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nfvcon