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

Glenn Parsons <glenn.parsons@ericsson.com> Thu, 09 July 2020 16:40 UTC

Return-Path: <glenn.parsons@ericsson.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2044A3A0D39; Thu, 9 Jul 2020 09:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.428
X-Spam-Level:
X-Spam-Status: No, score=-1.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URG_BIZ=0.573, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 sWcnOWiUDFtm; Thu, 9 Jul 2020 09:40:50 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2044.outbound.protection.outlook.com [40.107.236.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354343A0D32; Thu, 9 Jul 2020 09:40:46 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kvxPKWxrPjQYwgXAyqjdFu6JaGNi+fU2L6BRjLdzg6HT6iU99N5h1BNaQ5wobkAXeb25FUK9ySOqNMiOEYmtvTsAzWNc6l0P3rr9+aRUtWgyYGL1SJbO+VC/g+jAIHonsLucqZ0PMwwFBUgLJ1+XvfMTorXEdvI220gC5q4zwH5pgVdsOh9nT4taymaLUHuH2+Xg9abKeZ/QkWAjejgyYvqXXELqQlBfXkgqN/2P7cQlxjPCw4oCb7cG5DXiKU3jFDPy4wfn5OoISUuS4lutxG/nWv5sZfDpK1P3hjm7btHWBdrXMmeWkEZ7f8Tma38KOVzj7tCMaal2zPDx33LwhQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wxrs9vf06+ytrHg9/bwGIHYNfQWZfVraudeb6zqkQqg=; b=GVgxYWpLCLX59qegT7iqHe1mZ2zmA7E6XgOHENtQlhqYz/Uoocpy3iszZ6hkPdViOjIn6lY1V2JAjvHGYlKU2RAZkM14c1bmwoyRZ3Vk5OD9RJSSTH2hUuD/EJ2FDU2Fax/Li2lc8fLjT4KLhipHISJKUXmhKlPbwfgZTf0q/SIM8NiGIsflyaeXlgMpe7HXkU5wt3GmiWgTPAB8skyILFOB76WIiM+RE2LLQLeJrjyc8cg1vvfRtQCHPOqs51nh9a/mm3JoTn5figme3WcI1KqhOF8P88Ky6YVA0SAZ98Lohf2pQr5wlaFvzS9yMo+OrFFgtR3mHbrNZysH8+M6PA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wxrs9vf06+ytrHg9/bwGIHYNfQWZfVraudeb6zqkQqg=; b=h3VRsTjFRI2BFdrXWz3yTZxUAomkVkqpj0sKK1GhLL+sDWOx+JwJtrA4LC4Cre2EZ5bszKc0KdGr8hsfcL5vVGEeOZadswQ39HKxBlHUPNC1O0TOOFtQGJ+mLdGdLVAwggb60qoG2ETtJMcxtd77MhI/iR/ZPcJLNZOzbI1SCiQ=
Received: from CY4PR15MB1270.namprd15.prod.outlook.com (2603:10b6:903:10b::15) by CY4PR15MB1159.namprd15.prod.outlook.com (2603:10b6:903:107::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.22; Thu, 9 Jul 2020 16:40:45 +0000
Received: from CY4PR15MB1270.namprd15.prod.outlook.com ([fe80::115e:f3a5:92d6:c019]) by CY4PR15MB1270.namprd15.prod.outlook.com ([fe80::115e:f3a5:92d6:c019%4]) with mapi id 15.20.3174.022; Thu, 9 Jul 2020 16:40:45 +0000
From: Glenn Parsons <glenn.parsons@ericsson.com>
To: Susan Hares <shares@ndzh.com>, 'Qin Wu' <bill.wu@huawei.com>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
CC: "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology@ietf.org>
Thread-Topic: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14
Thread-Index: AdZVlV9atFR63w/7S9StKyNxYHPZ2QANcy0AABDAqCA=
Date: Thu, 9 Jul 2020 16:40:44 +0000
Message-ID: <CY4PR15MB127026454EA4B9A67DF682D38B640@CY4PR15MB1270.namprd15.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAAD819002@dggeml531-mbs.china.huawei.com> <007001d655cb$2cf53dc0$86dfb940$@ndzh.com>
In-Reply-To: <007001d655cb$2cf53dc0$86dfb940$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ndzh.com; dkim=none (message not signed) header.d=none;ndzh.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [174.112.20.41]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 59437e20-edd0-4716-c926-08d82426d3aa
x-ms-traffictypediagnostic: CY4PR15MB1159:
x-microsoft-antispam-prvs: <CY4PR15MB1159178256B12C12F3A9EB4C8B640@CY4PR15MB1159.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kpIvjhrOMq9z1hv16gRWXWKP12YTQP5CXKD4kztdZVbkH9NEXRzPQXdQkER9EwfPc19T8YfP+271cKaz36chDPWtZBuE0QGjqHVVOH8YoP/OEFSrMaM8wD8KSDQ0cO5jAptazqvDwxvQpi/FnzM0Af51z/ESWD56cdPwADPWUcCGOnLqcoERNGC6c/wwOsWes/iz9YLGsCPv2GnMuu/o3w9WqHrYUVGvbtLj9JIddgqPGsXtDGG2I9C3Yj2TvB0F6OeRwM218J0g9iF3DRDps1l0Aeuw4CWmmTAAblJ8DMB0gJQnrQ+GBX8fvQHyEjIUFsYLmQWWsJpFo8BJaAp/wbY7Gt+Ml3wfYjIPbxPnbbb0SOzA4P55Ig3cM3ZL3TLheLbgi5qINBeh8K/Dl4fNbg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CY4PR15MB1270.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(396003)(376002)(39860400002)(366004)(346002)(71200400001)(8676002)(33656002)(4326008)(44832011)(52536014)(66446008)(110136005)(316002)(64756008)(55016002)(66476007)(66556008)(966005)(7696005)(2906002)(76116006)(83380400001)(66946007)(186003)(8936002)(478600001)(9686003)(6506007)(86362001)(166002)(53546011)(5660300002)(26005); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: OSJxn9xmuGDcgm2J9CALUjyzD9abgsONinINKT4GCqrdciWcF008VKzIdiz5lhQ0AJ0U8QLY9tkUA8V0i1A/toPKm5T/CInB2qYrSU+v6PdB9pCeXkgc5xWq/0uhxZByQPWbIVXEKyjxAophDLyDXgFGBDLOgaHWa0iByFSaeRFuuleZWmVlW1rCoxNo1FIkUjhrLz79G+6GZmVufQPKHvQo/LRX58RtscWsJEYQjkljhDeJqv9lPlVHBCzUOkhtJhneg2gRdf2UH7UT3Piw3gxlmJeWzkwHDiFf2imZgOc3066d1fWJqD0oNpzf7ILgWHy0w3yBwlVt1WBpZZzB7OFyIpPoyWrn/2tdOB9v7fDCbHJ48T0JI/yG4wX36O5s//vo3zjSAK6s9irGBrPx8+bb0alEaH+Q50sbAPrYE59Do9FkZY3VOQJl4lpCpeTnux1kGCmMxooeQRIwDDV7eSbs+Wbi1EeNx2/azGGFG6t6zTZ3NKN90scN5uoa5TKz
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR15MB127026454EA4B9A67DF682D38B640CY4PR15MB1270namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR15MB1270.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 59437e20-edd0-4716-c926-08d82426d3aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2020 16:40:44.9898 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Db9o8ZvxqGmKzey4vD+VBU3PUYJn5WEoascHLwc1pZh+GYKixZ7+MozYffVenMhJyCQWPOxvLM4yD0QoW93zwhEPw/L6VmCHGwVoHrn83fI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR15MB1159
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/rldLmOvuYllGAIn7m5XCa7kCZjA>
Subject: Re: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 16:40:53 -0000

Sue,

I do appreciate you checking if there was coordination on this document.  As I noted we had not been previously aware of it.

I answered your questions to the best of my ability yesterday.

The 802.1 YANGsters group meets next Thursday and can provide a fuller review of the document (including more complete answers to your questions) than I can as the WG chair.

Cheers,
Glenn.

From: Susan Hares <shares@ndzh.com>
Sent: Thursday, July 9, 2020 4:30 AM
To: 'Qin Wu' <bill.wu@huawei.com>om>; Glenn Parsons <glenn.parsons@ericsson.com>om>; ieee-ietf-coord@ietf.org
Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org
Subject: RE: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

Glen:

I’m sorry you feel disappointed in the coordination between IETF and IEEE.

Please note that this work predates your work with the Yang modules (first WG draft is April, 2015), and should have been mentioned in these discussions since that time.  This WG draft is not a recent event.  Where and how the coordination teams missed this draft is something you can discuss with IETF leadership.   From my viewpoint, my understanding is that the IETF-IEEE interactions were to be placed through this IETF-IEEE committee for liaison.   Members of the IESG were to pass information regarding our drafts to this committee.

Since I was asked to double check this coordination, I went directly to the email list (per Alvaro Retana).  In my work as a WG chair, I have repeatedly tried to get the IETF side of this IETF-IEEE committee to validate our work, and to coordinate with IEEE 802.1.

If you are going to review this document at your IEEE meeting,  please be aware it is a logical topology that creates a virtual model of layer 2 networks for network management purposes.  This virtual model attaches to a virtual layer 3 model.   As Qin mentioned, I recommend you RFC 8345 and send me questions if the difference between the physical construct (IEEE) and this virtual topology (IETF NM) is unclear.   As Qin states, this is not an overlap with IEEE models but an virtual topology built on top of an existing IETF NM model.  We have used IEEE Yang models and definitions where ever possible as IEEE models came into being (2015-2018) in the L2 model.

Prior to sending this query, I found and downloaded the files you mentioned.  (I’m an IEEE member and a past participant in IEEE 802.1) .

On my question 1:   I am asking for clarity on Table 48-7, page 29-30 in 802.1Q-2018.

The Bridge structure has “name” (r-w), “address” (r-w), type (r-w), ports (12.4) and uptime (12.4).   This structure is required for bridges.

In deployed switches, there is a sys-mac-address with the ability to have a VLAN-ID attached.   How does IEEE 802.1 view this difference?   As far as the Yang module (dated 2018), is this functional a vendor augmentation to the base model?

Do you wish to provide input on my questions 2 and 3?

Thank you, Susan Hares



From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: Wednesday, July 8, 2020 10:06 PM
To: Glenn Parsons; Susan Hares; ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>
Cc: draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>
Subject: RE: [ieee-ietf-coord] Aid with draft-ietf-i2rs-yang-l2-network-topology-14

Glenn:
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.

-Qin
发件人: Glenn Parsons [mailto:glenn.parsons@ericsson.com]
发送时间: 2020年7月9日 9:57
收件人: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>
抄送: draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>
主题: 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:  http://ieee802.org/1/files/public/YANGs/<https://protect2.fireeye.com/v1/url?k=726f4484-2cdfd91c-726f041f-861fcb972bfc-60c7268723bc795b&q=1&e=2850473c-7f5a-4262-ac44-3fbb1fd4b400&u=http%3A%2F%2Fieee802.org%2F1%2Ffiles%2Fpublic%2FYANGs%2F>
And they are also in the YANG catalog github repository.
Published modules: https://github.com/YangModels/yang/tree/master/standard/ieee/published/802.1<https://protect2.fireeye.com/v1/url?k=97bad733-c90a4aab-97ba97a8-861fcb972bfc-43b5646805477fde&q=1&e=2850473c-7f5a-4262-ac44-3fbb1fd4b400&u=https%3A%2F%2Fgithub.com%2FYangModels%2Fyang%2Ftree%2Fmaster%2Fstandard%2Fieee%2Fpublished%2F802.1>
802.1 Draft modules per project: https://github.com/YangModels/yang/tree/master/standard/ieee/draft/802.1<https://protect2.fireeye.com/v1/url?k=f12c16d4-af9c8b4c-f12c564f-861fcb972bfc-bd8dd64710685976&q=1&e=2850473c-7f5a-4262-ac44-3fbb1fd4b400&u=https%3A%2F%2Fgithub.com%2FYangModels%2Fyang%2Ftree%2Fmaster%2Fstandard%2Fieee%2Fdraft%2F802.1>

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 https://ieeexplore.ieee.org/document/8467507).  The document should be clearer than just looking at the modules, for example Table 48-7 shows Generic bridge management information.

Cheers,
Glenn.

--
Glenn Parsons
Chair, IEEE 802.1 WG
glenn.parsons@ericsson.com<mailto:glenn.parsons@ericsson.com>
+1-613-963-8141



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

Greetings IEEE and IETF coordination team:

https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topology/

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 –



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.



http://ieee802.org/1/files/public/YANGs/ieee802-dot1q-bridge.yang<https://protect2.fireeye.com/v1/url?k=516a7d20-0fcac74e-516a3dbb-866038973a15-2c9158d6b703682e&q=1&e=42b15d09-5d4e-483a-812a-dffdf64a4195&u=http%3A%2F%2Fieee802.org%2F1%2Ffiles%2Fpublic%2FYANGs%2Fieee802-dot1q-bridge.yang>



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

draft-ietf-i2rs-yang-l2-network-topology?



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