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

Qin Wu <bill.wu@huawei.com> Wed, 28 August 2019 06:57 UTC

Return-Path: <bill.wu@huawei.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 9B57E120871 for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 23:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9YltiHzgqiDB for <i2rs@ietfa.amsl.com>; Tue, 27 Aug 2019 23:57:13 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 001B51208D9 for <i2rs@ietf.org>; Tue, 27 Aug 2019 23:57:12 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A41679E51C247573E3FA for <i2rs@ietf.org>; Wed, 28 Aug 2019 07:57:10 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 28 Aug 2019 07:57:10 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.9]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0439.000; Wed, 28 Aug 2019 14:57:06 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, tom petch <ietfc@btconnect.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: AdVdbarGDQHObMs8QaKkT58Yb2HpSA==
Date: Wed, 28 Aug 2019 06:57:05 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA92B40A5@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.31.203]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/9URPIXxlePaK8YNc3JkpfMWxe3E>
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: Wed, 28 Aug 2019 06:57:16 -0000

Rob, Thanks for the update.

-Qin
-----邮件原件-----
发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 Rob Wilton (rwilton)
发送时间: 2019年8月27日 23:14
收件人: tom petch <ietfc@btconnect.com>om>; Qin Wu <bill.wu@huawei.com>om>; i2rs@ietf.org
抄送: Susan Hares <shares@ndzh.com>
主题: Re: [i2rs] I-D Action: draft-ietf-i2rs-yang-l2-network-topology-09.txt

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-to
> > po
> > 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-top
> > ol
> > 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-networ
> > k-
> > to
> > pology-09
> > >
> > > A diff from the previous version is available at:
> > >
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-yang-l2-network-to
> > po
> > 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
_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs