[Idr] Survey for YANG model design : routing protocols CLI implementation

[<[e-mail]>]

Hi Folks,

A lot of us are currently working on Yang model drafts. In the framework of routing protocols related drafts, we have some discussion regarding how to model the configuration of routing protocols and especially do it need to be routing-instance centric or protocol centric (see slides for quick explanation of the difference). This is a cross protocol discussion, as we would like to apply the same design to all.

In order to decide how to progress on this major design point, one point  is to evaluate current implementations and how many are routing-instance centric and protocol centric. The famous implementations are well known, but we would like to have a more global view. This metric would be one among others.

In order to help us to do this inventory, could you please respond unicast to me, if you are an implementor and you have an implementation of a routing-protocol (ISIS,OSPF,RIP,BGP, PIM ... but also MPLS-TE, LDP, RSVP ...) and in this case, what is your CLI flavor ?

Please use this sample format, so it would be easier for me to aggregate :
(If you own multiple implementations, you can fill multiple lines.)


Vendor

OS

Protocol Centric

VRF centric

Cisco

IOS/IOS-XE

X





Thanks for your help !


[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: [phone] <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
mobile: [phone] <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
[e-mail]<mailto:[e-mail]>



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.