Re: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

Qin Wu <> Thu, 09 July 2020 02:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 020FC3A0C0D; Wed, 8 Jul 2020 19:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URG_BIZ=0.573, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0saZUGks_JvX; Wed, 8 Jul 2020 19:06:16 -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 123623A0C0C; Wed, 8 Jul 2020 19:06:16 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 18B21EFDC6F671D31AF0; Thu, 9 Jul 2020 03:06:13 +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, 9 Jul 2020 03:06:12 +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, 9 Jul 2020 03:06:12 +0100
Received: from ([]) by ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0487.000; Thu, 9 Jul 2020 10:06:08 +0800
From: Qin Wu <>
To: Glenn Parsons <>, Susan Hares <>, "" <>
CC: "" <>
Thread-Topic: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14
Thread-Index: AdZVlV9atFR63w/7S9StKyNxYHPZ2Q==
Date: Thu, 9 Jul 2020 02:06:08 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAAD819002dggeml531mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jul 2020 02:06:18 -0000

Confused with your statement, a few clarifications:
1.L2 Topology model is not L2 configuration model overlapping with IEEE work, L2 Topology is built on topo of network topology YANG data model (i.e.,RFC8345)defined by IETF.
2.L2 topology model has already respected IEEE work and reuse data types defined by IEEE 802.1 related YANG data model work.

·¢¼þÈË: Glenn Parsons []
·¢ËÍʱ¼ä: 2020Äê7ÔÂ9ÈÕ 9:57
ÊÕ¼þÈË: Susan Hares <>om>;
Ö÷Ìâ: RE: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

I will start by expressing my disappointment.

There has been a YANG item on our coordination list for years.  We have been updating IETF on our YANG module work and our issues.  We have been integrating IEEE work into the IETF YANG catalog as drafts and final approved modules.  This IETF L2 YANG module clearly overlaps with IEEE 802.1 and yet as far as I can tell this is the first indication of that to us.  It is not even in your YANG catalog as a draft.  Hours before your final approval, there is an urgent request for comment.    I would instead request that this be deferred by IESG to give 802.1 time to review the module at our plenary next week.

That said, all the IEEE 802.1 YANG modules are  on our website:
And they are also in the YANG catalog github repository.
Published modules:
802.1 Draft modules per project:

Clause 12.4 in 802.1Q-2018 is the bridge management entity clause, I suspect you are asking about the bridges/bridge/address in the YANG module.

IEEE 802.1Qcp-2018 should be normative (it is freely available  The document should be clearer than just looking at the modules, for example Table 48-7 shows Generic bridge management information.


Glenn Parsons
Chair, IEEE 802.1 WG<>

From: ieee-ietf-coord <<>> On Behalf Of Susan Hares
Sent: Wednesday, July 8, 2020 1:33 PM
Subject: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

Greetings IEEE and IETF coordination team:

is being reviewed by the IESG for publication as an RFC.  It is being proposed by the I2RS WG.
This draft provides a Yang model for L2 logical topologies that is being combined with L3 logical network models.  This model is being implemented by 3+ vendors.   In this process, we have the following questions that overlap between IEEE and IETF.

1) Regarding system management  MAC Address ¨C

Where in 802.1Q-2018 do I find the Yang model for the system management port for a switch?

By system management, I mean that port that configuration information is exchanged about.   I do not mean the port that sends LLDP packets.<>

2)  Where can I find the latest status of yang models for the time sensitive work in 802.1?

This model considers an L2 port as a termination point which is ¡°in  use¡± for traffic, blocking traffic, down (due to hardware) or some other function.   We wish to determine if time sensitive configurations will provide another concept for port.  A general explanation would be helpful.

3) Would liaison give me  reading on what status the following references should be in


Ben Kaduk suggests that:

  a) Normative --> informative   RFC3688 and RFC7951

  b) Informative--> normative: [IEEE802.1Qcp], RFC7348

I¡¯d appreciate your joint opinion on these matters.   We are trying to follow the best common practices of both IEEE and IETF in this draft.

Susan Hares
Co-chair I2RS
Shepherd for draft-ietf-i2rs-yang-l2-network-topology