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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 27 August 2019 15:14 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 B62CB1200CD for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 08:14:09 -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=XlDoEd7K; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=VjpVAbSs
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 i2mxrAyHLZUI for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 08:14:07 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6E3C12006F for <i2rs@ietf.org>; Tue, 27 Aug 2019 08:14:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8380; q=dns/txt; s=iport; t=1566918846; x=1568128446; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=jxIfkflLxQl3KRhUM77/g9LXk2DteTiP2e+poH8tA6Y=; b=XlDoEd7KpLgGsQIV9i7a54AAySHh1ARGw05MdTH30sqI6HAsX4tQPxIA JfWB6J71s/P5OOq6XAHYq1dhDebsj+Sj4VzPB7F1FC0WAelD0s+vuAi/v FDfFwJPyjcmVjJ1BqhxOzUslSh9Wkv2S28vLU6U5+lpd8LYQrUqSQ5IH0 M=;
IronPort-PHdr: =?us-ascii?q?9a23=3AwrImlBIC4E+1Z38XddmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXFfkLfr2aCoSF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CrAABcSGVd/4QNJK1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBZ4FFUANtViAECyoKhBeDRwOKc4JcfpZrgUKBEANUCQEBAQw?= =?us-ascii?q?BARgLCgIBAYQ/AheCLyM4EwIKAQEEAQEBAgEGBG2FLgyFSgEBAQMBAQEQERE?= =?us-ascii?q?MAQEsCwELBAIBBgIRBAEBAwIjAwICAiULFAEICAEBBAENBQgBGYMBgWoDDg8?= =?us-ascii?q?BAgyPBJBhAoE4iGFzgTKCewEBBYEyARNBgwAYghYJgQwoi3UYgUA/gRFGghc?= =?us-ascii?q?1PoJWCwEBAQEBARaBFAESAQcagwkygiaMUyGCKoU3lx4JAoIehmqNeYIybYZ?= =?us-ascii?q?DjnSNa4E2hjiEZ4tVAgQCBAUCDgEBBYFnIWdxcBUaIYJsCYI5DBeDT4UUhT9?= =?us-ascii?q?yAYEoi1uBIgGBIAEB?=
X-IronPort-AV: E=Sophos;i="5.64,437,1559520000"; d="scan'208";a="401358417"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Aug 2019 15:14:05 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x7RFE5b1018264 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Aug 2019 15:14:05 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 27 Aug 2019 10:14:05 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 27 Aug 2019 10:14:04 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 27 Aug 2019 10:14:04 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PG71HPTXVUe+JFE7BJy9MyOx7sNS89zXo2FBDn9O08UKpxlkHKKN0qwf9TKRSfAhel+XNx/AXLX4sP5RMqt0Odg5T4+PdfhLA4l4sEkPR0L5mgenbXuX2TwGywUknbQuD/+NLiL1gjpSnB5IILY2Uti7Gk0TDSr4IiBmJM/KsBZBbx6Hs2eLIGqzuIg/LJj+85vIdzjbue4iPESvXkJdLQgMGXGvQQC0gtYhk4SUNbB62Vb0YG8Mot1+BDhnkFaRBDDMNiwQRRAeN46c32Fkc79cH+D+QA1+wV1F5e4wczmG2ytuxg6Z/6RPjtZUUkk5XmIvv4yOm45Iuwu3seYwMg==
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=jxIfkflLxQl3KRhUM77/g9LXk2DteTiP2e+poH8tA6Y=; b=UJzWtB0o6fhgJhwv2FS0+B8OTjoTk+qOkWHALBaVd/hbT7wlIRBHeMShljpmiNLbRo0cd75+LnD0xKt0hYaTlH1Xg0lGNTEM1QCsk37PVP/9O20JLzLQ+JzkD0HqjWwNzA4vrWnzo3ds12RT6Fl2aosY2FDPYENFk/0x50ZPKo0DVLm3NnE1y1qrwa8Y3sOHVFIHsQ6caJ61FHI31FcKrr7vcfRAlSayod83LYKGkz8cXggOBAgkUyeJVYxD76/W2n8dCU4ym5z5caRoopZ8BzBfbzSCDv8NjEjST5PWJJpd107L5XtXeKopSphc/fnxYhJM0bKho8NGFL2YZvtUAw==
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=jxIfkflLxQl3KRhUM77/g9LXk2DteTiP2e+poH8tA6Y=; b=VjpVAbSsjvHbDlwbKnn2b/2L5znBx6zccpRF9cCNdy5yEfVa91ioW+E6+DbkAeiua/h//NQ3Cpx3MWr8JZhG1CbjJfsVGC4RMJ6fpvyCWGNAS0zpZYEBpfbcOPgcvs1mKNkjZMJNWI6Kv7Y5UL4F90KSsIX/khiL82D8N2SeS7Y=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3855.namprd11.prod.outlook.com (20.178.253.159) 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 15:14:03 +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 15:14:03 +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+xQQh1QTKUr3SJeEiWDwGXFNBQAAwSM+A=
Date: Tue, 27 Aug 2019 15:14:02 +0000
Message-ID: <MN2PR11MB4366B09AF7B4B89F054435FDB5A00@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA92A6B86@dggeml511-mbx.china.huawei.com> <012a01d559d1$1ff3b580$4001a8c0@gateway.2wire.net> <MN2PR11MB43660602118C1A2D713770CEB5A00@MN2PR11MB4366.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB43660602118C1A2D713770CEB5A00@MN2PR11MB4366.namprd11.prod.outlook.com>
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: 2c3b60a7-e938-4fcc-100f-08d72b013201
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3855;
x-ms-traffictypediagnostic: MN2PR11MB3855:
x-ms-exchange-purlcount: 9
x-microsoft-antispam-prvs: <MN2PR11MB385510AEF76120126CF11B78B5A00@MN2PR11MB3855.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0142F22657
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(39860400002)(376002)(396003)(366004)(199004)(13464003)(189003)(6306002)(26005)(476003)(25786009)(102836004)(446003)(966005)(110136005)(66574012)(2906002)(486006)(6246003)(66476007)(316002)(256004)(2940100002)(76176011)(53546011)(7736002)(4326008)(11346002)(99286004)(14444005)(14454004)(229853002)(52536014)(74316002)(305945005)(66446008)(6116002)(66946007)(66556008)(71200400001)(6436002)(55016002)(66066001)(53936002)(478600001)(71190400001)(296002)(8676002)(5660300002)(81166006)(81156014)(86362001)(9686003)(2501003)(7696005)(8936002)(76116006)(186003)(64756008)(6506007)(33656002)(3846002)(357404004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3855; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: ICyJSVo3iaGh+UR4GpTVgBEGeyiDW9UD4Py6ASTZpVXX4F3GkbAUJPmEOimrJyjMjxSHfriVHnN90IAGo4uxGTzsrQD7dflaQDyoif2cEvi5sicbFJ3yNNOYT9/cMWVNIw+LfSgLfX7Y381yXF9bKw+/DAHXVJ/UQS9sOJpYVpc3fhtcbmZ+ZYc6yFAeUwXVN/90ShAU0QQkdXS0tW2g68PBBXpuNPeXFzzcKetsOJlekbjkvPZ72IL7mtffdmJfwvv8YT3Al+XdjEcBkdf8b5iIV4+5qwTY81sUnRToA43SHcQn7o1V6dJS5zzCWbH1Rt5ncXeWffM9cWJouXVhut62ceSONbbT7j8Juqiok5pPUsKWxqfHvftlsajnWkXFQLGe1e6X06XgB0W3TjsFirQsCFk7hdukxpaSvi8rSqM=
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: 2c3b60a7-e938-4fcc-100f-08d72b013201
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Aug 2019 15:14:02.8357 (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: bRonYOC+4jhlp/2zTQ9ZvvjhgPEFsLC3x/5FzBGM0kbFTp4r9Sq7bckYMUIVXDpzrYKsiteTDXeJTfJjPyxpTg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3855
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.21, xch-rcd-011.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/nVPOs8oBHwk5AFQlwyaVYRvoEnk>
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 15:14:10 -0000

Hi Tom, Qin,

> -----Original Message-----
> From: Rob Wilton (rwilton)
> Sent: 27 August 2019 14:23
> To: tom petch <ietfc@btconnect.com>om>; Qin Wu <bill.wu@huawei.com>om>;
> i2rs@ietf.org
> Cc: Susan Hares <shares@ndzh.com>
> Subject: RE: I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt
> 
> 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>om>; 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.

[RW]
The conclusion from the IEEE 802 YANG folks (on email, and confirmed on the IEEE Yangsters call today) is that the reference should be to "IEEE Std 802.1Qcp-2018".

Thanks,
Rob


> 
> 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-topo
> > lo
> > 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-topol
> > og
> > y/
> > >
> > > There are also htmlized versions available at:
> > >
> > https://tools.ietf.org/html/draft-ietf-i2rs-yang-l2-network-topology-0
> > 9
> > >
> > 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-topo
> > lo
> > 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