Subject: Re: [Supa] FW: New charter of YMCA

From: LUIS MIGUEL CONTRERAS MURILLO <[email-masked]>
Date: Fri, 17 Oct 2014 12:28:45 +0000

Hi Guang, thanks for your comments. Please see my answers in line.
El 17/10/2014 09:17, Guang Yao <[email-masked]> escribió:
>
>
>
> Hi,
>
>
>
> Some quick questions:
>
>
>
> 1.       Why YANG? Are there any alternatives?
YANG is a work produced in IETF, then is straightforward to explore YANG capabilities for addressing this topic. However it would be nice to take into account some other alternatives. Please, could your indicate what other alternatives do your have in mind?
>
> 2.       Is YANG capable to accomplish the object?
Our first impression is yes, but we need to really work on the topic to realise if something is missing.
>
> 3.       Some SDN controllers (e.g., ONIX) make use of NIB (network information base) to store the network view. How can the NIB and YANG model be related?
>
>
I'm not familiar with NIB. Definitely I need to look at that for having an answer.
> Best regards,
> Guang
Thanks!!
>
>
> From: Liushucheng (Will) [mailto:[email-masked]]
> Sent: Friday, October 17, 2014 2:51 PM
> To: sunqiong; xiechf; Kostas Pentikousis; [email-masked]; JF Tremblay; [email-masked]'; Jun Bi; Guang Yao; [email-masked]; [email-masked]
> Subject: FW: New charter of YMCA
>
>
>
> Hi all,
>
>
>
> Would you please review the new charter below and send your comments to the list? Thank you!
>
>
>
> Regards,
>
> Will (Shucheng LIU)
>
>
>
> From: Supa [mailto:[email-masked]] On Behalf Of Tina TSOU
> Sent: Wednesday, October 15, 2014 11:15 PM
> To: [email-masked]
> Cc: [email-masked]; LUIS MIGUEL CONTRERAS MURILLO
> Subject: [Supa] New charter of YMCA
>
>
>
> Dear Benoit, Parviz, Eric, Andrew et al,
>
>
>
> Luis, Ying, Georgios and I sat together today, came out with the following new charter, hoping to accomadate the comments received these days.
>
>
>
> Juergen said we really need a better name, so Luis suggested YMCA.
>
>
>
> -------------
>
> Yang Models for Configuration and topology Abstraction (YMCA) charter
>
>
>
> Description of Working Group:
>
>
>
> As the underlying network infrastructure grows, and new services/traffic are rapidly increased, it becomes significantly more challenging than in the past to maintain the network and deploy new services. Programmatic ways to configure and operate networks, often called software-defined, are considered by many network operators in order to provide significant benefits in deployment agility. Yang Models for Configuration and topology Abstraction (YMCA) attempts to achieve this configuration automation by introducing multi-level and multi-technology network abstractions. It plans to create YANG model of general network topology and YANG model of application-specific configuration to provide topology information as applications expect and map network-wide configuration/topology into individual device-recognized configuration. As a result, standardized interfaces between applications and network controllers of all types could be established and automatic and programmable configuration can be achieved based on these interfaces. Although several organizations outside and inside of the IETF have defined various schemes for the configuration of network devices and specific network controllers, none of them offer a vendor-neutral and technology-wide (i.e., L0 to L7) standardized way for applications to transmit their needs to controllers.
>
>
>
> The main goal of YMCA is to provide Yang models of vendor neutral service specific abstractions for the VPN and Inter-DCs traffic steering and tunneling network services, which allow applications to request these network services from network controllers of all types, e.g., single or multiple controllers, to be quickly and dynamically created/deleted/modified, using mechanisms for exchanging information to and from the NEs.
>
>
>
> Work items for YMCA include:
>
> 1) Yang Models of views of L0-L7 Network topology with bi-directional and uni-directional links
>
> 2) Using Yang Models defined in 1), map Service Specific Yang Models of VPN and DDC virtual links Network Configuration to NE Specific configuration of Tunnel Policy and Traffic Steering Policy
>
> 3) Specify how NEs can interact with local or remote network controllers (e.g., exchange configuration information, status, etc)
>
>
>
> Deliverables:
>
> =============
>
> o) Produce an informational RFC "Problem Statement".
>
> o) Produce a standards-track RFC that specifies YANG models of different views of L0-L7 Network topology
>
> o) Produce standards-track RFCs that specify extensions for the generic YANG models defined above for VPN and Inter-DCs traffic steering and tunneling network services
>
> o) Produce an informational RFC that provides the guidelines for mechanisms that can map the Service Specific Yang Models of VPN and DDC virtual links Network Configuration to NE Specific configuration of Tunnel Policy and Traffic Steering Policy.
>
> o) Produce a standards-track RFCs that specify how NEs can interact with local or remote network controllers (e.g., exchange configuration information, status, etc)
>
>
>
> Milestones:
>
> ===========
>
> Mar 2015  Initial "Problem Statement" WG I-D
>
> May 2015  Initial "L0-L7 network topology view YANG Model" WG I-D
>
> Jul 2015  Initial “VPN service specific data model” WG I-D
>
> Jul 2015  Initial “Inter-DC service specific data model” WG I-D
>
> Aug 2015  Initial "Mapping Guidelines" WG I-D
>
> Oct 2015  Initial "NE to/from Controllers information exchange" WG I-D
>
> Sep 2015  Submit "Problem Statement" I-D to IESG
>
> Dec 2015  Submit "L0-L7 network topology view YANG Model" I-D to IESG
>
> Feb 2016  Submit “VPN service specific data model " I-D to IESG
>
> Feb 2016  Submit “Inter-DC service specific data model “ I-D to IESG
>
> May 2016  Submit "Mapping Guidelines" I-D to IESG
>
> May 2016 Submit "NE to/from Controllers information exchange" I-D to IESG
>
> -----------------
>
>
>
>
>
> Thank you,
>
> Tina
>
>

________________________________

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