Re: [Teas] TE Topology YANG Model: connectivity-matrix definition

Igor Bryskin <Igor.Bryskin@huawei.com> Fri, 21 July 2017 20:00 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 0A6A512ECAD for <teas@ietfa.amsl.com>; Fri, 21 Jul 2017 13:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 OxSw1AVy6Q3i for <teas@ietfa.amsl.com>; Fri, 21 Jul 2017 13:00:15 -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 EC8B6129B25 for <teas@ietf.org>; Fri, 21 Jul 2017 13:00:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLA44331; Fri, 21 Jul 2017 20:00:12 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 21 Jul 2017 21:00:10 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.153]) by SJCEML701-CHM.china.huawei.com ([169.254.3.13]) with mapi id 14.03.0301.000; Fri, 21 Jul 2017 12:59:55 -0700
From: Igor Bryskin <Igor.Bryskin@huawei.com>
To: "Dieter.Beller@nokia.com" <Dieter.Beller@nokia.com>, "xliu@kuatrotech.com" <xliu@kuatrotech.com>, "vbeeram@juniper.net" <vbeeram@juniper.net>, Igor Bryskin <Igor.Bryskin@huawei.com>, "oscar.gonzalezdedios@telefonica.com" <oscar.gonzalezdedios@telefonica.com>, "tsaad@cisco.com" <tsaad@cisco.com>, "hshah@ciena.com" <hshah@ciena.com>, "lberger@labn.net" <lberger@labn.net>, "db3546@att.com" <db3546@att.com>, "shares@ndzh.com" <shares@ndzh.com>, "zali@cisco.com" <zali@cisco.com>, "Mazen.Khaddam@cox.com" <Mazen.Khaddam@cox.com>, "tonyle@juniper.net" <tonyle@juniper.net>, "sergio.belotti@alcatel-lucent.com" <sergio.belotti@alcatel-lucent.com>, "dieter.beller@alcatel-lucent.com" <dieter.beller@alcatel-lucent.com>, "rrao@infinera.com" <rrao@infinera.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, "xufeng.liu.ietf@gmail.com" <xufeng.liu.ietf@gmail.com>, "sergio.belotti@nokia.com" <sergio.belotti@nokia.com>, "AnSharma@infinera.com" <AnSharma@infinera.com>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: TE Topology YANG Model: connectivity-matrix definition
Thread-Index: AQHTAh1Q2Apn41fNC0q3FbgdbaNLc6Jes50s
Date: Fri, 21 Jul 2017 19:59:54 +0000
Message-ID: <etPan.5972b166.57c631e7.f73@localhost>
References: <VI1PR06MB1488321471B9183F07ED5B9DB12C0@VI1PR06MB1488.eurprd06.prod.outlook.com>, <c35c4a0b-a544-1f4f-aa6a-0926136c36d9@nokia.com>
In-Reply-To: <c35c4a0b-a544-1f4f-aa6a-0926136c36d9@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_etPan5972b16657c631e7f73localhost_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.59725D4C.0091, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.153, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 69e6e108376da3ccbd0c1a2de3b3dc7e
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RKmv8pIZI44Ln8r58m4fb3auaGQ>
Subject: Re: [Teas] TE Topology YANG Model: connectivity-matrix definition
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Jul 2017 20:00:17 -0000

Hi Dieter,

Please note that we are modeling not just 1:1 switching, but also 1+1 splitting and merging.

Igor
From:Dieter Beller
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,
Date:2017-07-21 08:31:44
Subject:TE Topology YANG Model: connectivity-matrix definition

Hi Xufeng, Igor, all,

looking again at the connectivity-matrix definition, I have the following question: based on the current definition there are multiple separate entries
for the same "from TP" to all potential "to TPs":

   +--rw connectivity-matrix* [id]
      +--rw id                          uint32
      +--rw from
      |  +--rw tp-ref?              leafref
      |  +--rw label-restriction* [inclusive-exclusive label-start]
      |     +--rw inclusive-exclusive    enumeration
      |     +--rw label-start            rt-types:generalized-label
      |     +--rw label-end?             rt-types:generalized-label
      |     +--rw range-bitmap?          binary
      +--rw to
      |  +--rw tp-ref?              leafref
      |  +--rw label-restriction* [inclusive-exclusive label-start]
      |     +--rw inclusive-exclusive    enumeration
      |     +--rw label-start            rt-types:generalized-label
      |     +--rw label-end?             rt-types:generalized-label
      |     +--rw range-bitmap?          binary

I think that it is more efficient to have a single entry for each "from TP" and a list with all potentially connectable "to TPs"

      +--rw id   uint32
      +--rw from
      |  +--rw tp-ref?   leafref
      |  +--rw label-restriction* [inclusive-exclusive label-start]
      |     +--rw inclusive-exclusive   enumeration
      |     +--rw label-start           rt-types:generalized-label
      |     +--rw label-end?            rt-types:generalized-label
      |     +--rw range-bitmap?         binary
      +--rw to-tp-list* [tp-id]
      |  +--rw tp-id   te-types:te-tp-id
      |  +--rw tp-ref?   leafref
      |  +--rw label-restriction* [inclusive-exclusive label-start]
      |     +--rw inclusive-exclusive   enumeration
      |     +--rw label-start           rt-types:generalized-label
      |     +--rw label-end?            rt-types:generalized-label
      |     +--rw range-bitmap?         binary



If the label restrictions of the "from TP" are the same (or do not exist, which is typically the case) for multiple or all connectable "to TPs", the
connectivity matrix description using the to-tp-list becomes much more compact compared to the description above. (I am not sure whether
the tp-id can be used as list index. So, if this is not correct, it has to be replace it by some other index.)


Thanks,
Dieter