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

<stephane.litkowski@orange.com> Wed, 11 February 2015 08:43 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF1741A037A; Wed, 11 Feb 2015 00:43:07 -0800 (PST)
X-Quarantine-ID: <KAVyaSPCcY1t>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...@OPEXCLILM34.corporate.adroot.infra.ftgroup>\n
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 KAVyaSPCcY1t; Wed, 11 Feb 2015 00:43:03 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DCA1A036C; Wed, 11 Feb 2015 00:43:02 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id AB7113B4503; Wed, 11 Feb 2015 09:43:01 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 82CE94C066; Wed, 11 Feb 2015 09:43:01 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.53]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Wed, 11 Feb 2015 09:43:01 +0100
From: stephane.litkowski@orange.com
To: "isis-wg@ietf.org list (isis-wg@ietf.org)" <isis-wg@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: [mpls] Survey for YANG model design : routing protocols CLI implementation
Thread-Index: AdBFLLfJ87T7mg7qSBKOVExsw2JGuwAqVntQAAAnGkA=
Date: Wed, 11 Feb 2015 08:43:00 +0000
Message-ID: <7138_1423644181_54DB1615_7138_3898_1_9E32478DFA9976438E7A22F69B08FF920C7A12CC@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <12023_1423571161_54D9F8D8_12023_1801_1_9E32478DFA9976438E7A22F69B08FF920C7A0F1A@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: multipart/related; boundary="_004_9E32478DFA9976438E7A22F69B08FF920C7A12CCOPEXCLILM34corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.2.11.73029
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/k3tQcAA6P1-3gsKISzrN_EF-zoc>
Subject: Re: [Idr] [mpls] Survey for YANG model design : routing protocols CLI implementation
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 08:43:08 -0000

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>
Sent: Tuesday, February 10, 2015 13:26
To: ospf@ietf.org<mailto:ospf@ietf.org>; isis-wg@ietf.org<mailto:isis-wg@ietf.org> list (isis-wg@ietf.org<mailto:isis-wg@ietf.org>); mpls@ietf.org<mailto:mpls@ietf.org>; idr@ietf.org<mailto:idr@ietf.org>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Cc: Rtg-yang-coord@ietf.org<mailto:Rtg-yang-coord@ietf.org>
Subject: [mpls] Survey for YANG model design : routing protocols CLI implementation
Importance: High

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. This is a cross protocol discussion, as we would like to apply the same design to all.

Example of routing-instance centric CLI : (Typically Juniper, ALU)
routing-instance R1 {
                protocol isis {};
                protocol ospf {};
                protocol ldp {};
}
routing-instance R2 {
                protocol isis {};
                protocol ospf {};
                protocol ldp {};
}

Example of protocol centric CLI : (Typically CISCO)
protocol isis {
routing-instance R1 {}
routing-instance R2 {}
}
protocol ospf {
routing-instance R1 {}
routing-instance R2 {}
}



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: +33 2 23 28 49 83 <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: +33 6 37 86 97 52 <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>
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>



_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________

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.