Re: [CCAMP] Connectivity-matrix in YANG models for WSON devices

Leeyoung <> Sat, 22 July 2017 07:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B93BA131B3B for <>; Sat, 22 Jul 2017 00:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, 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, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZL6NqmdgTLB6 for <>; Sat, 22 Jul 2017 00:09:16 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BFEE6131B3E for <>; Sat, 22 Jul 2017 00:09:15 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DLA95030; Sat, 22 Jul 2017 07:09:13 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 22 Jul 2017 08:09:12 +0100
Received: from ([]) by ([]) with mapi id 14.03.0301.000; Sat, 22 Jul 2017 00:08:55 -0700
From: Leeyoung <>
To: Igor Bryskin <>, "" <>, "" <>
Thread-Topic: [CCAMP] Connectivity-matrix in YANG models for WSON devices
Thread-Index: AQHTAhNiGpWmdPizXUijLmQfE/y8MaJeP8MggADwTICAADubQA==
Date: Sat, 22 Jul 2017 07:08:54 +0000
Message-ID: <>
References: <>, <> <etPan.5972b74c.75686250.2b65@localhost>
In-Reply-To: <etPan.5972b74c.75686250.2b65@localhost>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E172B3EFD38SJCEML702CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5972FA1A.0031, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 4e6c7914e5c4e8eee25984945f39bd77
Archived-At: <>
Subject: Re: [CCAMP] Connectivity-matrix in YANG models for WSON devices
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 22 Jul 2017 07:09:18 -0000

Hi Igor,

I understand your proposal for moving generic property like b/w, labels and others such as C.M. to TE:type where you specify all technology specific details in the groupings. My doubt is if you can capture all tech specific properties for Optical (WSON/Flexi-grid) Device model in one type. For instance, C.M. in Optical is a node property in which we have interfaces for WAN ports and may have interfaces to other elements within the node such as resource pools, etc.

But before we get into details, I'd like to see your proposed TE:Type for Connectivity Matrix; then Jorge and I can provide more meaningful feedback to you.

Another question I have (similar to Italo's) is that would it be more sensible to keep techn specific TE types in each tech-specific layer rather than lumping all in one TE: type Yang model. If we need to add unforeseeable technology specific technology model later, tech specific TE: Type might have some benefit.


From: Igor Bryskin
Sent: Friday, July 21, 2017 10:25 PM
To: Leeyoung <>om>;;
Subject: Re: [CCAMP] Connectivity-matrix in YANG models for WSON devices

When you said you wanted to  augment  basic connectivity matrix to include, for example, application code on per CM entry basis, you really meant to augment TE path proprties with things like application code, OSNR at the edgges, etc. -detailed CM entry attributes.
This means that the same augmentation will be needed every time when a TE path is involved. This happens in multiple places in both TE Topology and Tunnel models. Thus it is much better to provide somehow just once layer specific choice statements for TE path properties and then use the grouping everywhere in both models - exactly the same argunent for defining the bandwidth  the way we did.

To:Dieter Beller,,
Date:2017-07-21 09:12:16
Subject:Re: [CCAMP] Connectivity-matrix in YANG models for WSON devices

Hi Dieter,

Please see inline for my comment.


From: CCAMP [] On Behalf Of Dieter Beller
Sent: Friday, July 21, 2017 1:20 PM
Subject: [CCAMP] Connectivity-matrix in YANG models for WSON devices

Hi CCAMPers,

during the joint session an YANG and the CCAMP session yesterday, I commented that the following two drafts are defining a connectivity matrix in the
YANG models for WSON devices:

I was suggesting to have a look at the definition of the connectivity-matrix in and re-use
that definition unless there are good reasons to define the connectivity matrix for WSON devices differently.
YL>> We have not finished the model. We will add a few items to the Conn. Matrix which are physical layer specific information augmentation. I can foresee the ports/interfaces in and out of the device may be associated with FEC/Modulation constraints and other impairment aspect as well. I also foresee within a device, we may have embedded resource pool models, etc. But as you say, anything has defined in the TE-topo will be augmented and we will only describe additional properties peculiar to optical.

Moreover, the connectivity-matrix of a WSON device (e.g. a ROADM) typically reflects the connectivity limitations of the wavelength selective switching
fabric of the device and hence should be read-only (ro) as opposed to read-writable (rw). Why would an operator further restrict  the connectivity
capabilities of a WSON device?
YL>> With the physical data added, there may be administrative issues where some restriction would apply. We don't have specific use-case at this moment, but leaving +rw may be sensible thing.