Re: [i2rs] 'network type' placement and RFC8345

Qin Wu <> Thu, 24 September 2020 12:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5E3EC3A0E0A for <>; Thu, 24 Sep 2020 05:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AoW1RZ-3keae for <>; Thu, 24 Sep 2020 05:18:06 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ED30A3A0ADF for <>; Thu, 24 Sep 2020 05:17:38 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 7216CBA8E01B9AAB3E0A for <>; Thu, 24 Sep 2020 13:17:37 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 24 Sep 2020 13:17:36 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Thu, 24 Sep 2020 13:17:36 +0100
Received: from ([]) by ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0487.000; Thu, 24 Sep 2020 20:17:31 +0800
From: Qin Wu <>
To: tom petch <>, Sue Hares <>
CC: "''" <>
Thread-Topic: [i2rs] 'network type' placement and RFC8345
Thread-Index: AdaSbKw6zvFFmq6tTgmFrPhUzSeWyA==
Date: Thu, 24 Sep 2020 12:17:31 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [i2rs] 'network type' placement and RFC8345
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Sep 2020 12:18:15 -0000

发件人: tom petch [] 
发送时间: 2020年9月24日 16:45
收件人: Qin Wu <>om>; Sue Hares <>
抄送: '' <>
主题: Re: [i2rs] 'network type' placement and RFC8345

From: Qin Wu <>
Sent: 24 September 2020 03:22

Hi, Tom:
Layer2, Layer 3, TE are all base modules which other modules can extend from.
I am not sure we have Layer 1 base module, WSON and flexi-grid, if my understanding is correct, are TE technology specific and WSON and flexi-grid module can be seem as extension to TE module or a module derived from TE module Therefore we could follow OSPF example defined in the L3 topology module or L3 TE module defined in draft-ietf-teas-yang-l3-te-topo-08.
   module: ietf-l3-te-topology
     augment /nw:networks/nw:network/nw:network-types
       +--rw l3-te!
   module example-ospf-topology
   augment "/nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology"
       +--rw ospf!
I might be wrong if a generic layer 1 can be defined without adding dependency to TE technology. But at least layer 1 type or layer 0 type are common building block that can be reused.

In addition, base model, in my opinion doesn't need to limit to layer 1, layer 2, layer 3, service layer, TE layer this angle, we may classify network topology from other angle, e.g., classify network topology into UNI topology and NNI topology, One relevant model is UNI topology model that is proposed in the opsawg
such models are also base model which other modules can derive from.

For network type, if we can define it as identity, it may be another design option.
But comparing with presence container design, I think the only difference is one is explicit way, the other is implicit way.

My starting point is RFC8345 which for me creates this 'registry' of network type and lays down the ground rules.  It says that a presence container must be defined.  Why not identity, as with routing protocols, I do not know.  It suggests a tree structure and is generally keen on a layered network as in layer 1, layer 2, layer 3, application-related layers and so on which is fine until you get to sub-IP.

But, network layering has nothing to do with YANG modules, with imports, cross-references, dependencies and so on so the fact that the wson module augments te-topo seems an irrelevance where the tree structure of layers is concerned.  There are lots of augments to te-topo and they could be any layer. 

[Qin]: we can have ietf-l3-te-topology module augment to layer 3, but we don't have l3 specific module augment to te module, see draft-ietf-teas-yang-l3-te-topo-08.
I will not see ietf-te-topology-packet as l3 specific module augment to te module. But may be a little bit fuzzy.
For ccamp modules which are classified into layer 0,layer1 and married with te technology, I feel nature they augment from te module, but not other layer module. That's my impression. But I might be wrong.

RFC8345 says a lot but I do not understand what it is saying when it comes to adding a network type beyond what it says about presence container.  What is the point of the tree structure therein? 
[Qin]: The question is whether there are any layer0, layer 2 modules without marriage with TE technology?

 Is it something we want or need to embody in YANG so that we can do something fancy as we can elsewhere with base identity and derivations therefrom as with routing protocols?  

I do not know so my inclination is to say that the structure should be flat until we have a good reason otherwise lest we find ourselves tied up in knots at a later data.  I think it would be quite wrong to build a tree structure of network type based on YANG import which is what I suspect CCAMP are doing.

Tom Petch

发件人: i2rs [] 代表 tom petch
发送时间: 2020年9月23日 17:16
收件人: Sue Hares <>
抄送: '' <>
主题: [i2rs] 'network type' placement and RFC8345

RFC8345 requires that a new network type be given a presence container and suggests a tree structure with layer 1, layer 2, layer 3 and service as top level nodes with OSPF as an example of a node subordinate to layer 3.  te-topology , RFC8795, places its presence container at the top level alongside these four.
Question; where should a network type such as WSON or flexi-grid be placed?  wson-yang, in IETF Last Call, places it under te-topology which is possible but it seems to me more like a layer 1 or layer 0. But then network types do not seem to form a tree, rather a mesh so a tree structure seems wrong.  And wherever layer 1 is defined it is not in a module imported by wson-yang although it might be added to layer0-types (!) which wson-yang does import. I would see it as wrong to define layer 1 in wson forcing others to import wson.


I have posted this to Lou and TEAS but as it is a question that cuts across multiple WG I suspect that I will get multiple contradictory answers or none:-)

Tom Petch
i2rs mailing list