Re: [Rtg-yang-coord] [mpls] [Teas] Generic LSP Yang

Igor Bryskin <IBryskin@advaoptical.com> Fri, 06 March 2015 13:11 UTC

Return-Path: <IBryskin@advaoptical.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC12C1ACE0A; Fri, 6 Mar 2015 05:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 tDlbta1Zm7Le; Fri, 6 Mar 2015 05:11:46 -0800 (PST)
Received: from mail3.advaoptical.com (mail3.advaoptical.com [74.202.24.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0C71ACE06; Fri, 6 Mar 2015 05:11:39 -0800 (PST)
Received: from atl-srv-mail10.atl.advaoptical.com (atl-srv-mail10.atl.advaoptical.com [172.16.5.39]) by atl-vs-fsmail.advaoptical.com (8.14.5/8.14.5) with ESMTP id t26DBUV7014065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 08:11:30 -0500
Received: from ATL-SRV-MBX2.advaoptical.com (172.16.5.46) by atl-srv-mail10.atl.advaoptical.com (172.16.5.39) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 6 Mar 2015 08:11:30 -0500
Received: from ATL-SRV-MBX1.advaoptical.com (172.16.5.45) by ATL-SRV-MBX2.advaoptical.com (172.16.5.46) with Microsoft SMTP Server (TLS) id 15.0.1076.3; Fri, 6 Mar 2015 08:11:30 -0500
Received: from ATL-SRV-MBX1.advaoptical.com ([fe80::6433:f8f:ea41:a6e1]) by ATL-SRV-MBX1.advaoptical.com ([fe80::6433:f8f:ea41:a6e1%14]) with mapi id 15.00.1076.000; Fri, 6 Mar 2015 08:11:30 -0500
From: Igor Bryskin <IBryskin@advaoptical.com>
To: Dhruv Dhody <dhruv.dhody@huawei.com>, 'Lou Berger' <lberger@labn.net>, Dhruv Dhody <dhruv.ietf@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] [Teas] Generic LSP Yang
Thread-Index: AQHQWAUzsQkQu7Ewm0G1yY1vtfqWpZ0PbO1g
Date: Fri, 06 Mar 2015 13:11:28 +0000
Message-ID: <1c6cb7c87b1d44c880ddabb5947ebcea@ATL-SRV-MBX1.advaoptical.com>
References: <CAB75xn5UZDW-aWaZpQYtu_22b8ts6mOC+tS9wqctWEmx1WY-iw@mail.gmail.com> <54F88FE0.9040206@labn.net> <23CE718903A838468A8B325B80962F9B8705236A@BLREML509-MBX.china.huawei.com>
In-Reply-To: <23CE718903A838468A8B325B80962F9B8705236A@BLREML509-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.16.5.49]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33, 0.0.0000 definitions=2015-03-06_04:2015-03-06,2015-03-06,1970-01-01 signatures=0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/nY0NyJtu2FwZDDMsvDdeKkGDJsI>
X-Mailman-Approved-At: Mon, 09 Mar 2015 18:00:35 -0700
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, TEAS WG <teas@ietf.org>
Subject: Re: [Rtg-yang-coord] [mpls] [Teas] Generic LSP Yang
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 13:11:52 -0000

Druv,

IMHO TE-LSP, LDP-LSP and SPRING-LSP have nothing in common. They should have totally independent models each being developed in respective WG.

Igor

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Dhruv Dhody
Sent: Friday, March 06, 2015 7:00 AM
To: 'Lou Berger'; Dhruv Dhody; mpls@ietf.org
Cc: Rtg-yang-coord@ietf.org; Zhangxian (Xian); TEAS WG
Subject: Re: [mpls] [Teas] Generic LSP Yang

Hi Lou,

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: 05 March 2015 22:48
> To: Dhruv Dhody; mpls@ietf.org
> Cc: Rtg-yang-coord@ietf.org; Zhangxian (Xian); TEAS WG
> Subject: Re: [Teas] [mpls] Generic LSP Yang
> 
> Hi Dhruv,
>     Good stuff!  There's already some related work going on based on 
> the TE LSP drafts/work started in MPLS and now in the TEAS WG.  -- 
> This was mentioned at the TEAS interim too, see
> http://www.ietf.org/proceedings/interim/2014/12/18/teas/minutes/minute
> s-
> interim-2014-teas-1
> 
> It looks like you don't completely overlap as you are also considering 
> non-TE LSPs.

[Dhruv]: Yes, our aim is to go one level up and see if we can have a generic LSP yang model including TE and non-TE, as well any signaling protocol or lack thereof (static, SR).  

> 
> So I guess a basic question to answer is what is the relationship of 
> the models of TE and non-TE LSPs. e.g,
> - a generic LSP model with parallel TE and non-TE sub models
> - a generic LSP model with protocol specific models
> - a generic LSP model with some mix of the above (which I think you 
> are
> proposing)
> - no generic LSP model, and separate  TE and non-TE sub models
> - etc

[Dhruv]: Our aim is to explore and see if we have attributes common to all LSP irrespective of TE/non-TE; signaling protocol, Segment Routing and even PCEP to warrant such a generic LSP model. 

A possible overall relationship with the model is in the draft - 
                 +---------------+
                 | Generic LSPDB |
                 |   ietf-lspdb  |
                 +-------^-------+
                         |
         ---------------------------------------------
        |                |                |           |
        |                |                |           |
   +----+----+   +-------+-------+   +----+----+   +--+--+
   | LDP-LSP |   |    BGP-LSP    |   |  TE-LSP |   | SR  |
   |         |   |               |   |         |   |     |
   +---------+   +---------------+   +----^----+   +--^--+
                                          |           |
                                           -----------
                                          |           |
                                          |           |
                                     +----+----+   +--+--+
                                     | RSVP-TE |   | SR- |
                                     |         |   | TE  |
                                     +----^----+   +--^--+
                                          |           |
                                          |           |
                                           -----------
                                          |
                                     +----+----+
                                     |  PCEP   |
                                     |         |
                                     +---------+


> 
> It's not clear to me how much value a generic model brings, but 
> details always help to clarify the situation.
> 
> My preference would be to have more details on the non-TE models (to 
> compare against the TE model) before deciding on the need for / value 
> of a generic LSP model.

[Dhruv]: Yes, I think that would surely help. 
IMHO the ease of augmentation and having a generic base model is one of the key advantages of YANG, so we hope its a worthwhile exercise to explore the need for such a generic model instead of separate TE and non-TE models. 

Regards,
Dhruv

> 
> Lou
> 
> On 3/5/2015 11:48 AM, Dhruv Dhody wrote:
> > Hi,
> >
> > Xian and I have created generic base yang model for LSPs. This model 
> > is expected to be augmented by seperate data model with specific 
> > signalling protocol and technology.
> >
> > See https://tools.ietf.org/html/draft-zhang-mpls-lspdb-yang-00
> >
> > Comments / Suggestions ?
> >
> > We need to work out the relationship with the rest of MPLS yang 
> > model which can be hashed out in Dallas.
> >
> > Regards,
> > Dhruv / Xian
> >
> > Excuse the obvious nit with the LSP abbreviation expansion :P
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> >
> 
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls