Re: [i2rs] I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 27 August 2019 13:23 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DF7120047 for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 06:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=i4R+AZqy; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=edz0aclq
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 cQVkejFONmdW for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 06:23:21 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABD7B120089 for <i2rs@ietf.org>; Tue, 27 Aug 2019 06:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7210; q=dns/txt; s=iport; t=1566912200; x=1568121800; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WEdNdvGtzbPruehPOsup6eXvYa4774xIX3YoKbTUUlA=; b=i4R+AZqyvts5zxLdYtt8THPG+W80If15aGxZtOiPHFqiU04qeAVMGeco CrKZC4+tcOMjhcxAlPriO5tOhjTz1ojdlHS96Us9ty8kvyUVJgxbjVmhX oXZ58O637q4z4ZNL715RGXqWd75mZJfD0Xr63TD7nLkj6HlqJ//8nAWHI E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AI5YeRx2WllzEMNOPsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxKHt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQE1L6KOLtaQQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CrAADaLWVd/5BdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBZ4FFUANtViAECyoKhBeDRwOKcYJcfpZrgUKBEANUCQEBAQw?= =?us-ascii?q?BARgNCAIBAYQ/AheCLyM4EwIKAQEEAQEBAgEGBG2FLgyFSgEBAQMBAQEQERE?= =?us-ascii?q?MAQEsCwELBAIBBgIRBAEBAwIjAwICAiULFAEICAEBBAENBQgBGYMBgWoDDg8?= =?us-ascii?q?BAgyOcJBhAoE4iGFzgTKCewEBBYEyAQMCDkGCexiCFgmBDCiLdRiBQD+BEUa?= =?us-ascii?q?CFzU+glYLAQEBAQEBFoEvGoMJMoImjFOCS4U3lx4JAoIehmqNeYIybYZDjnS?= =?us-ascii?q?Na4E2hjiEZ4tVAgQCBAUCDgEBBYFnIYFYcBUaIYJsCYI5DBeDT4UUhT9yAYE?= =?us-ascii?q?ojH0BgSABAQ?=
X-IronPort-AV: E=Sophos;i="5.64,437,1559520000"; d="scan'208";a="621583084"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Aug 2019 13:23:04 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x7RDN4i5011965 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Aug 2019 13:23:04 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 27 Aug 2019 08:23:04 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 27 Aug 2019 08:23:03 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 27 Aug 2019 08:23:03 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SlIPIZxUeIdu7EBhBj7PqFV9wjWgAElIDRcW7R0EJ1fs/dqObshi8p4TJkMX9Z3Ks62ypzEy08G9fEV29zvOWxR9sFGQCVm4fR9JrlbBi9+ZTX9vrDFNk2zAZzqorc4jP59zf0XfJORE21E9i8ef0PoRCv7m+vVUPTiHSmsse1hgF70fEXqed9ikW9kQm4mOdnVBjTRr38YW3x4kYHWoGsJKm31ScwWxZim9hjfYWGkMJwYCINID8NZ60aa8mILyzclQ6V0+hmx/HGcw3cd9t01aAk7zxiUdCV0oPgvyPrXih3zIWKKcQlUPTdE0YZejV0dfJn2a0Q+zWy+COzsbow==
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=WEdNdvGtzbPruehPOsup6eXvYa4774xIX3YoKbTUUlA=; b=D+cLNN6TZDVDu7Y1bhnM4xRJCXF8lvkfBYBWk4JHuAI8V0w4v0E+C4XIwXrJ7HykEVRdmjLY0xPNWLlckt5K6AR1NJtt69rc5J1qs6vkJbvYnzTad2WXnsg2L0DUcariXj3Knup96ZeDRHmXqrSTQw1giImTddRKdJNoBgqjJKqqY333CtZMsy8N1/v0xwFlAJFXxtgB4SpKSHsPcLaYi3r0bsGqF1fng7W00LeBtnQxsGrbh8MzzNSXZRmrmHfbMwDmA4H2cecYqvOdWIHhrUSMurzITvwJ/Mc7W625OX82+it6JJ0MDIM9TcoxpKgvWCCl8ua7Gz6xRhVgjvSTjQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WEdNdvGtzbPruehPOsup6eXvYa4774xIX3YoKbTUUlA=; b=edz0aclqh4EO34dBqLjTiUUBGzgz/U9CwaqH/oTSPH2xaNGhluN+qjWRLFJa0pWSGkPQE2VF3rPAqArZ+ToUYDYicsnerodwf4ekp5IUmRUL+K6qzoIXN/TtMjSAh2JQwh5H3Qmc8lX+qR+G6uCVBD8JmyLO6+C6fSpJ4CHRN9M=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3919.namprd11.prod.outlook.com (10.255.180.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.21; Tue, 27 Aug 2019 13:23:02 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::6db3:f4c:467b:30f6]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::6db3:f4c:467b:30f6%7]) with mapi id 15.20.2199.021; Tue, 27 Aug 2019 13:23:02 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: tom petch <ietfc@btconnect.com>, Qin Wu <bill.wu@huawei.com>, "i2rs@ietf.org" <i2rs@ietf.org>
CC: Susan Hares <shares@ndzh.com>
Thread-Topic: I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt
Thread-Index: AdVWXNxjYr+xQQh1QTKUr3SJeEiWDwGXFNBQ
Date: Tue, 27 Aug 2019 13:23:01 +0000
Message-ID: <MN2PR11MB43660602118C1A2D713770CEB5A00@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA92A6B86@dggeml511-mbx.china.huawei.com> <012a01d559d1$1ff3b580$4001a8c0@gateway.2wire.net>
In-Reply-To: <012a01d559d1$1ff3b580$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f57e659e-983d-45bb-6dc9-08d72af1afc8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3919;
x-ms-traffictypediagnostic: MN2PR11MB3919:
x-ms-exchange-purlcount: 9
x-microsoft-antispam-prvs: <MN2PR11MB39199B2BD4FC9BFD5E85BBF1B5A00@MN2PR11MB3919.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0142F22657
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(4636009)(366004)(376002)(346002)(136003)(396003)(39860400002)(13464003)(189003)(199004)(99286004)(53546011)(6506007)(81156014)(81166006)(26005)(102836004)(25786009)(2906002)(6116002)(66574012)(186003)(71190400001)(76176011)(7736002)(6246003)(71200400001)(8676002)(8936002)(66066001)(14444005)(256004)(7696005)(9686003)(52536014)(2501003)(110136005)(316002)(14454004)(296002)(229853002)(55016002)(966005)(3846002)(478600001)(33656002)(5660300002)(53936002)(74316002)(6436002)(486006)(476003)(446003)(11346002)(6306002)(66556008)(86362001)(66946007)(66446008)(64756008)(76116006)(66476007)(4326008)(305945005)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3919; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: gPjxZZXlFGv4daDvWqdYU9ftgGAuB9r179UfkDWDPolmZ0FQPXiTG23JQKufFcqV8wFxkaS2m3JVvMd3cvA2i5zgIrPdgXyPA1YT3GwP7qa5rjR4MPLInZAx+X9iUbPtjPLGSDUnD4cuH7esMlckJxlXzv8aUIs8Mb5vqH2gu/QPzd4nvtK9ejrVMMs/EeXXfnLAlVP3Ab+/bHIkcyi6CIo2koV6yIpX/dA0jpKL8yVu+nryRdo+h61dfD44FAPodLQSJ6CQIz0ODVuhZNQrRCQ2ZTR/I1skYYymMhFAZM/ivVaW+jVz5K1gOaHK7DXT0aiz90xMfCutm21eO9pcbTU5C8nOmU67zDHmQ0vcfgCv4if/BeLctQRRREQ583PMvvjSJPmh0OwUoDYxn+Iqq5rOVIkh92FtZAOKkDRnEoc=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f57e659e-983d-45bb-6dc9-08d72af1afc8
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Aug 2019 13:23:01.9138 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8lns8SBKNPyZliqryzlIFElaObohfT87Qvq/9xJsiPWP1CQGu7xK1ARcHFjWcTxrCdg8dFVUq6d0dTqEvgwiVA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3919
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/lNxZssPKz8FMJWg6xKSwQ424Ssg>
Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2019 13:23:24 -0000

Hi Tom,

Please see inline ...

> -----Original Message-----
> From: i2rs <i2rs-bounces@ietf.org> On Behalf Of tom petch
> Sent: 23 August 2019 17:39
> To: Qin Wu <bill.wu@huawei.com>; i2rs@ietf.org
> Cc: Susan Hares <shares@ndzh.com>
> Subject: Re: [i2rs] I-D Action: draft-ietf-i2rs-yang-l2-network-topology-
> 09.txt
> 
> Qin
> 
> I said that I might look some more and I have.
> 
> I still think that you need references for 802.1ad and 802.1ah.  It is not
> a question of whether or not they are imported, it is where does the
> reader go to find out more about e.g. QinQ and that needs nailing down to
> a specific document, and in the case of the IEEE, that needs a date, as
> you give for 802.1Q.
> 
> Talking of which, I find that Rob imports that IEEE module from a
> different document; 802.1Qcp; um.
[RW] 
802.1Qcp (https://standards.ieee.org/standard/802_1Qcp-2018.html) is the amendment to 802.1Q-2018 (https://standards.ieee.org/standard/802_1Q-2018.html) that defines some bridging YANG models and the ieee802-dot1q-types.yang YANG models.

I've emailed the relevant folks at IEEE to ask what the correct reference is, and then presumably we can be consistent for all RFCs.

Thanks,
Rob


> 
> And, in the same vein, I would like a reference for LLDP.
> 
> /defned/defined/
> 
> leaf rate
> what are the units?
> 
>         leaf maximum-frame-size {
> what is a frame, what headers are included and what not?  This is a
> fraught topic
> 
> /ternimation point/termination point/
> 
>      leaf vlan-name {
> any constraints on length or character set?  I like them although am
> conscious that some YANG doctors do not.
> 
>      leaf encapsulation {
> the description exceeds the permissible line length for an RFC
> 
>           type enumeration {
>             enum in-use {
>              value 0;
> again a personal preference - I like to see zero kept for a special
> purpose (e.g. cannot be determined) unless there is a strong reason to use
> it (e.g. it is what the protocol has been using for years)
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Qin Wu" <bill.wu@huawei.com>
> Sent: Monday, August 19, 2019 8:08 AM
> 
> > v-09 is posted to address Tom's comments.
> > The diff is:
> >
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-yang-l2-network-topolo
> gy-09
> > Becuase datatracker pyang integration tool issue, Data model
> "ieee802-dot1q-types" can not been found
> > And imported into the model defined in this draft.
> >
> > -Qin
> > -----邮件原件-----
> > 发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表
> internet-drafts@ietf.org
> > 发送时间: 2019年8月19日 15:04
> > 收件人: i-d-announce@ietf.org
> > 抄送: i2rs@ietf.org
> > 主题: I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Interface to the Routing System WG of
> the IETF.
> >
> >         Title           : A YANG Data Model for Layer-2 Network
> Topologies
> >         Authors         : Jie Dong
> >                           Xiugang Wei
> >                           Qin Wu
> >                           Mohamed Boucadair
> >                           Anders Liu
> > Filename        : draft-ietf-i2rs-yang-l2-network-topology-09.txt
> > Pages           : 31
> > Date            : 2019-08-19
> >
> > Abstract:
> >    This document defines a YANG data model for Layer 2 network
> >    topologies.
> >
> > Editorial Note (To be removed by RFC Editor)
> >
> >    Please update these statements within the document with the RFC
> >    number to be assigned to this document:
> >
> >    o  "This version of this YANG module is part of RFC XXXX;"
> >
> >    o  "RFC XXXX: A YANG Data Model for Layer-2 Network Topologies";
> >
> >    o  reference: RFC XXXX
> >
> >    Please update the "revision" date of the YANG module.
> >
> >
> > The IETF datatracker status page for this draft is:
> >
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l2-network-topolog
> y/
> >
> > There are also htmlized versions available at:
> >
> https://tools.ietf.org/html/draft-ietf-i2rs-yang-l2-network-topology-09
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-yang-l2-network-to
> pology-09
> >
> > A diff from the previous version is available at:
> >
> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-yang-l2-network-topolo
> gy-09
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> 
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs