Re: [Teas] IETF TE Topology YANG Model Design Meeting Notes - 2016-05-23

Igor Bryskin <Igor.Bryskin@huawei.com> Thu, 26 May 2016 16:44 UTC

Return-Path: <Igor.Bryskin@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A923612D654 for <teas@ietfa.amsl.com>; Thu, 26 May 2016 09:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9-QEtxT1iRgi for <teas@ietfa.amsl.com>; Thu, 26 May 2016 09:44:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9998D12D0A7 for <teas@ietf.org>; Thu, 26 May 2016 09:44:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CPQ67777; Thu, 26 May 2016 16:44:40 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 26 May 2016 17:44:36 +0100
Received: from DFWEML501-MBX.china.huawei.com ([10.193.5.178]) by dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0235.001; Thu, 26 May 2016 09:44:24 -0700
From: Igor Bryskin <Igor.Bryskin@huawei.com>
To: Leeyoung <leeyoung@huawei.com>, Xufeng Liu <xliu@kuatrotech.com>, Vishnu Pavan Beeram <vbeeram@juniper.net>, Oscar Gonzalez De Dios <oscar.gonzalezdedios@telefonica.com>, Tarek Saad <tsaad@cisco.com>, Himanshu Shah <hshah@ciena.com>, Lou Berger <lberger@labn.net>, "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>, Susan Hares <shares@ndzh.com>, "Zafar Ali (zali)" <zali@cisco.com>, "Khaddam, Mazen (CCI-Atlanta)" <Mazen.Khaddam@cox.com>, Tony Le <tonyle@juniper.net>, "BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com>, "Beller, Dieter (Dieter)" <dieter.beller@alcatel-lucent.com>, Rajan Rao <rrao@infinera.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, "xufeng.liu.ietf@gmail.com" <xufeng.liu.ietf@gmail.com>, "Belotti, Sergio (Nokia - IT)" <sergio.belotti@nokia.com>, Anurag Sharma <AnSharma@infinera.com>
Thread-Topic: IETF TE Topology YANG Model Design Meeting Notes - 2016-05-23
Thread-Index: AdG3XGalY3SICAUtQf2LvT1Umc0SGwABG4MAAALVFfA=
Date: Thu, 26 May 2016 16:44:24 +0000
Message-ID: <0C72C38E7EBC34499E8A9E7DD007863908EDD175@dfweml501-mbx>
References: <DBXPR06MB623990C55CF493EFF51421EB1410@DBXPR06MB623.eurprd06.prod.outlook.com> <7AEB3D6833318045B4AE71C2C87E8E172A88ECF3@dfweml501-mbx>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E172A88ECF3@dfweml501-mbx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.253.100]
Content-Type: multipart/alternative; boundary="_000_0C72C38E7EBC34499E8A9E7DD007863908EDD175dfweml501mbx_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.574727F8.0254, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d1c10d952ca2cdf6985ba037fa1f913d
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/jx0qQYullQjfR9155h_qTOPMxPQ>
Cc: "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] IETF TE Topology YANG Model Design Meeting Notes - 2016-05-23
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 16:44:47 -0000

Hi Young,

Please, see in-line,

Igor

From: Leeyoung
Sent: Thursday, May 26, 2016 11:31 AM
To: Xufeng Liu; Vishnu Pavan Beeram; Igor Bryskin; Oscar Gonzalez De Dios; Tarek Saad; Himanshu Shah; Lou Berger; BRUNGARD, DEBORAH A (ATTLABS); Susan Hares; Zafar Ali (zali); Khaddam, Mazen (CCI-Atlanta); Tony Le; BELOTTI, SERGIO (SERGIO); Beller, Dieter (Dieter); Rajan Rao; Zhangxian (Xian); xufeng.liu.ietf@gmail.com; Belotti, Sergio (Nokia - IT); Anurag Sharma
Cc: teas@ietf.org
Subject: RE: IETF TE Topology YANG Model Design Meeting Notes - 2016-05-23

Hi Xufeng,

Thanks for this update. Your notes are always very helpful to understand the latest progress of this draft.

I have a few questions on the potentially adding model for labels for the connectivity matrix.


1.      You said:


               For each label
               o exclusivity (true/false)

Do you mean this bitmap?


2.      Are you aware of label restrictions applied for the connectivity matrix other than WSON? If so, then this model addition makes sense; if not, then we can add the label model for the connectivity matrix in the WSON YANG model. If the extent to which label model addition is not really a major constraint in the switching technologies other than WSON, it would be worthwhile to evaluate if we should do label restriction model in a generic way (per this draft) or do it in WSON specific way?  I am not aware of any label restriction model for the connectivity matrix for GMPLS other than WSON.
IB>> We had this discussion many time already. There are physical OTN switches that have constraints on the ODUk type level. For example, a switch can switch ODU2 from link 1 to link2, but ODU2e from link 1 to only link3. This is especially true for abstract compound nodes which may represent entire network domains. As you know abstract TE modes are very important for this model. So, no, connectivity restriction on a label level does not apply only to WDM.



3.       If we were to extend the label model for the connectivity matrix, I would think we also need to have label restriction model for TTP LLCL as well. What do you think?
IB>> This is actually a good point. Thanks for pointing out.

Cheers,
Igor


Thanks.
Young


From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Xufeng Liu
Sent: Thursday, May 26, 2016 9:48 AM
To: Vishnu Pavan Beeram; Igor Bryskin; Oscar Gonzalez De Dios; Tarek Saad; Himanshu Shah; Lou Berger; BRUNGARD, DEBORAH A (ATTLABS); Susan Hares; Zafar Ali (zali); Khaddam, Mazen (CCI-Atlanta); Tony Le; BELOTTI, SERGIO (SERGIO); Beller, Dieter (Dieter); Rajan Rao; Zhangxian (Xian); xufeng.liu.ietf@gmail.com; Belotti, Sergio (Nokia - IT); Anurag Sharma
Cc: teas@ietf.org
Subject: [Teas] IETF TE Topology YANG Model Design Meeting Notes - 2016-05-23

Participants:
Igor, Xufeng, Pavan, Dieter, Sergio, Himanshu

- Information sources
  > Discussed two use cases related to information sources:
    1) Provider applies policies to pick the most preferred.
    2) Provider does not apply policies and the decision is done by customer.
  > The model currently supports 1) well, but is not clear on 2).
  > Agreed to clarify the model by:
    1) Change "alt-information-sources" to "information-sources" to
       include all sources, including the selected one.
    2) For use case 1), the applied attribute has the selected value, and
       "information-sources" list all available sources.
       For use case 2), the applied attribute does not have value, and
       "information-sources" list all available sources.

- Connectivity Matrix
  > Discussed the comment from Cyril "to add a Label (Following
    RFC7579) restrictions".
  > Participants agreed that such constraint information is useful.
  > Participants agreed that such constraint information is generic
    enough to be used in various layers and use cases, including optical
    OTN, and abstract network topologies.
  > Participants agreed to send the suggestion TEAS WG to add such
    information to te-topology model.
  > The potential model change can be:
    For each connectivity-matrix entry, add:
      list of labels
        list types
               o inclusive-list
               o exclusive-list
               o inclusive-range
               o exclusive-range
               For each label
               o exclusivity (true/false)

Working members: please provide any comments.

Thanks,

- Xufeng

Note: Please drop me an email if you need an invite for joining the weekly call.

PS. Meeting on May 30 will be canceled for US holiday.