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

tom petch <ietfc@btconnect.com> Fri, 23 August 2019 16:39 UTC

Return-Path: <ietfc@btconnect.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 2CF37120105 for <i2rs@ietfa.amsl.com>; Fri, 23 Aug 2019 09:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 90F9QA0gKBLw for <i2rs@ietfa.amsl.com>; Fri, 23 Aug 2019 09:39:13 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130128.outbound.protection.outlook.com [40.107.13.128]) (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 A681B120020 for <i2rs@ietf.org>; Fri, 23 Aug 2019 09:39:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DO9W0/qrkEmcj0qiskHG9Ac8d3ZTCDhaMBtw/vjxa7nOclyi6o5RDOB8rTz5UNoEBQzqaSuSeGpIMtZmUCn7qaCHz1qmZueoQf6E28fYNObPvVejKp+Z46DPhnb9x9+2nxbGuXUbagxY4k1ofOFVj4yXrof/nRN7Qw3O5mLmdCj7/hUl94jcWpUd0DDfzHGLuGetsq5lnqH5oGwW7BlzN4rHdRkhCoTSZeavCcZf6523m7qgP9af2sBmilgIqA/22Vh8w9ue7wxCXKSD2lY7TTztuT9qYFdSy1QukphDqUO2g6Lln0Wtq7HD/181frKafoHnWoNjccg5Mm4NQPdcXg==
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=mOPZRwXBS2/sA3zJ/WWEk1PiUeRKClTeLoWHVzkbFtY=; b=bsqCRhXYYSzPU0cxWOEZmCDCTiZh35prV5NAB9QL215sxpw5GDrSTcE1/+HvdLRVVgwxQIBLp19aAGFP1NVzR5aTVEKNLoDk3v6VvO4Orxmd5h/eCyHkqPJ+xS6/Hx3RFpNZmTV5xrtAn+9TmH4p3d79GM/6PUqeTwrPL3XMKV35QaillqX3lvOvSvUPHzTM9jQR4u+q6zejJKbjMchBg7GI0eHv60zlqa3S91UMkkaXKMvq8h/aV1OFUfd0gUBzm46LE6UZ0vmNG4SOYMPfivdLemLEAfoZ2lSdv/AUtz/SPuoHm8yzOcDod4GSk1e4dlux+OwAlCERXiVViii2tw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mOPZRwXBS2/sA3zJ/WWEk1PiUeRKClTeLoWHVzkbFtY=; b=a4SxSGIQMMUBBAtJdPwwm71/AyuRPbDHt67pcenIG90/r6kgdfNec002Km/l23EX5StajGQxxG40SGht1DX1Cg//qc7/waGUOAl6iZoaTolUOb4IrrRmav2fCjtw1rYHIRXBRcJNlRaEFV1UWy/4kb7neqwIxrZ29vOgpHQmYRI=
Received: from HE1PR0701MB2283.eurprd07.prod.outlook.com (10.168.36.20) by HE1PR0701MB3033.eurprd07.prod.outlook.com (10.168.95.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.10; Fri, 23 Aug 2019 16:39:09 +0000
Received: from HE1PR0701MB2283.eurprd07.prod.outlook.com ([fe80::a55b:4fb9:4253:2d1c]) by HE1PR0701MB2283.eurprd07.prod.outlook.com ([fe80::a55b:4fb9:4253:2d1c%6]) with mapi id 15.20.2199.011; Fri, 23 Aug 2019 16:39:09 +0000
From: tom petch <ietfc@btconnect.com>
To: 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: AQHVWdEcO7vGRJjHZE6wpjtZc1pCJg==
Date: Fri, 23 Aug 2019 16:39:09 +0000
Message-ID: <012a01d559d1$1ff3b580$4001a8c0@gateway.2wire.net>
References: <B8F9A780D330094D99AF023C5877DABAA92A6B86@dggeml511-mbx.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0080.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:8::20) To HE1PR0701MB2283.eurprd07.prod.outlook.com (2603:10a6:3:2b::20)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 48f3af93-a657-4b9c-3912-08d727e86bd9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR0701MB3033;
x-ms-traffictypediagnostic: HE1PR0701MB3033:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <HE1PR0701MB30339C0AE33754E466143403A0A40@HE1PR0701MB3033.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0138CD935C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(366004)(136003)(396003)(39860400002)(199004)(189003)(13464003)(44716002)(44736005)(1556002)(62236002)(26005)(6116002)(3846002)(66066001)(446003)(50226002)(476003)(86362001)(2501003)(76176011)(81816011)(81686011)(52116002)(99286004)(5660300002)(2906002)(186003)(81166006)(110136005)(8936002)(14496001)(102836004)(71200400001)(386003)(6506007)(316002)(66574012)(71190400001)(53936002)(7736002)(4720700003)(478600001)(4326008)(14444005)(256004)(8676002)(81156014)(6246003)(305945005)(486006)(66446008)(64756008)(66476007)(66556008)(6306002)(66946007)(6436002)(9686003)(6512007)(966005)(61296003)(25786009)(229853002)(14454004)(6486002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB3033; H:HE1PR0701MB2283.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: QOEIf8+KZZe5ZrF4Y+lEvlyM/DhHixdhvJS2cNWa6GYjXDXZT/mAX6trcGeqLS/2QaT3Cc9oM4NEVSjGJ19yQvbzYDmfKVaXJrHayX7mGlWcHVFd9oopBYHU1j8PositAJB0y1/EEzGL9FbF6VdB0qp8THbP8n9E2gvyB211Z0/FIfQmEoPJYQA3jGcaNJr4HE2HRro2leSR+GHMd5EHBjejeZVGZrWDpfCC2MEU6mmZvbu3oh6/LV94bUgRTKjR1T29+e3wgZYfZZSqDA1MNDrYZHHIoN1QX6uS04IsZwx4CGg1wxBVroHDKAWbxtDa3qfOydKg42mCk3cggb4bdy3KCwuoYKF7Ub/0+Blqs/h0r1BoS/BwZ1d7dw5l/3Qg48Qb7xvWYhfG88H1yPoNAXXc+YafYrS5hVMbY8BlEas=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="gb2312"
Content-ID: <86BFCFB1BF7A9C499FFA678517009298@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 48f3af93-a657-4b9c-3912-08d727e86bd9
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2019 16:39:09.6696 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: z0Owt99b7ZklmwoCvcGpmHs+qsAOwQI7jJ+OJKhXTOnvPC7jRPOqpyKHL31V3Y48dIUpV1EBDPId11/N2UylVA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB3033
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/D1K34v8tlMf28_jti6pjJr8vYCw>
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: Fri, 23 Aug 2019 16:39:15 -0000

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.

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
>