Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt

tom petch <ietfc@btconnect.com> Tue, 20 August 2019 09:31 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 6076C1200C5 for <i2rs@ietfa.amsl.com>; Tue, 20 Aug 2019 02:31:14 -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 DMfo3UaKdfLz for <i2rs@ietfa.amsl.com>; Tue, 20 Aug 2019 02:31:11 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140119.outbound.protection.outlook.com [40.107.14.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17201120026 for <i2rs@ietf.org>; Tue, 20 Aug 2019 02:31:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CYMH+2Bjj8Rsd9L9H6rAQ8Tvxb6ozE8BIsZlhFC8r8XevWspvkbHGxyXEB5gXn5i5MRbjUm84ZzckkbAh3XxIeSwMFri+ztRMQ5ORXiSRqVXcEFMSszZzIYrZX6sp+61mBIoXwZRpWaZG0VLAMwvm54ricEzenWnB7umOVj++0gulQSZ8OYTAcZXwzUcSa9X8Qb3ZX7y/IaPWeutViLkUTGlIxDampapPo1gFbWNOMhS1RJzrRBXG6H/eKRnEsk83g3obqtBmIZ6nGZcUl3sLErm2l20sFOr7fvk+JnCc1fasPhhJpqLw1iLGYwvr7dxKnCrUO1iDIBmVlFY/o1Ixw==
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=Jk7Q7zaFrub8Kg1gfV9Ttxzp4CgrTahVw+qEzpC92XY=; b=CcJ/GMjfDIPopoALQoiU3M7PuSxOXy7SP7+auU8U2Vr7OwpJWN0csdzeMbXxWSKJ6iJIv8Xec3mNv3wTBrjRZSChZz+2wERAyf8NJB/M4yoALJ0VS1l231B2VFgpPgpG+gDwnV9sza6v2US5f0H886PDcAZlS1sgWs8Nrgen8iU9vCct6zYNjcsXO64452zkAA0Oyr6tSpZ6THn6ozbmGS2fEAcaFZMxmVOYhKEv62izF62ere8o5LHoDha8efxz3aduRi/OTGXZp4x0r0bSOtvK2IkSkkPx4S01T2FdBdgFLK278z+ihVfFROtawBdTD5nELe31JNtmMicVTayfpQ==
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=Jk7Q7zaFrub8Kg1gfV9Ttxzp4CgrTahVw+qEzpC92XY=; b=Ab5E7Fft5ooifVgnT0NDnjv3WdXt+oUp7kQ69BD7GIZJ4FJr5oltdGRrcqF+MILLQrx4ukeES0157Ie+OK5GCcRpxhdff6o+JNm13iaBywv6WnOs+0lD+PQ5LL57B9T0dCfMuyusSv9dc7d5BZS2d9QWLfSF5uV5Osx54HYjZZY=
Received: from AM4PR07MB3204.eurprd07.prod.outlook.com (10.171.188.157) by AM4PR07MB3121.eurprd07.prod.outlook.com (10.171.191.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.13; Tue, 20 Aug 2019 09:31:07 +0000
Received: from AM4PR07MB3204.eurprd07.prod.outlook.com ([fe80::a06e:f865:67f9:9199]) by AM4PR07MB3204.eurprd07.prod.outlook.com ([fe80::a06e:f865:67f9:9199%5]) with mapi id 15.20.2199.011; Tue, 20 Aug 2019 09:31:06 +0000
From: tom petch <ietfc@btconnect.com>
To: Qin Wu <bill.wu@huawei.com>, Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
CC: "russ@riw.us" <russ@riw.us>
Thread-Topic: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt
Thread-Index: AQHVVzn92OEKJ/SIHk+achT7ktgHxQ==
Date: Tue, 20 Aug 2019 09:31:06 +0000
Message-ID: <045f01d55739$d6b5f8e0$4001a8c0@gateway.2wire.net>
References: <B8F9A780D330094D99AF023C5877DABAA92A60AA@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: LO2P265CA0138.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9f::30) To AM4PR07MB3204.eurprd07.prod.outlook.com (2603:10a6:205:8::29)
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: 9dcc071c-2d67-495c-e2d2-08d725512012
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:AM4PR07MB3121;
x-ms-traffictypediagnostic: AM4PR07MB3121:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <AM4PR07MB3121680B02705C071C332626A0AB0@AM4PR07MB3121.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 013568035E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39860400002)(396003)(136003)(366004)(13464003)(199004)(189003)(256004)(446003)(2906002)(62236002)(478600001)(2501003)(7736002)(4720700003)(61296003)(110136005)(44716002)(8936002)(316002)(26005)(305945005)(386003)(6506007)(102836004)(14444005)(186003)(6306002)(9686003)(6512007)(229853002)(44736005)(6486002)(81686011)(8676002)(6436002)(52116002)(6246003)(81156014)(81166006)(81816011)(76176011)(86362001)(14454004)(66066001)(4326008)(3846002)(486006)(50226002)(99286004)(71190400001)(6116002)(53936002)(66946007)(1556002)(66556008)(25786009)(5660300002)(14496001)(66446008)(66476007)(64756008)(476003)(966005)(71200400001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB3121; H:AM4PR07MB3204.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: ctrfIMwAbW9y1um2bUfCscNN6FqMBPT5p566IMr2DD6A1hydbGy2eiZNBo1fHTAi+ebUgmo+7vvYhTY7RNy5gxwnZF/qNlskxjGW3n9g7pDa7vsVcwKxWl1GgZHlNLyMCkKO4sZ2Odyti836QlGcPeYXS756XHhlZruaLMP6cqXyOTKmaiPM+ehvSrHAD8ky0wjVQsh9vfzIFcHIjtdbfSDO4U5IkqaZw7U8G12caoi9N/QBm5PWZyBO3vKF1LHooBKmVZFkchUocAM14FvEfrV6Xnk+fmlsn7n0bVsF/HQAOijgfaTKlUzuVFIEDmkenBmgo2VIFt47dYuVJOeRns3aRADk1KbLztL5wdlHOrT/aZiZZvqYFUyi5JPhBcRRE6G32nmXOrB3rM0wT/gNrTwLpJS+JSrfSHcaacNhR7U=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="gb2312"
Content-ID: <5C11EA3AF4B43F469DEDCA6ABA0C9B56@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9dcc071c-2d67-495c-e2d2-08d725512012
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Aug 2019 09:31:06.1429 (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: nLLDXVVn4dntGpAnzjpeJ/AoC9oeT6aqFcAcsGrkQZvVdNmYCUin1NYWBzAjx2KttjY+70pqJTXZk/Oa041Qyg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB3121
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/v6l-fVXxoysMKhDZUhiXtycAR5U>
Subject: Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.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, 20 Aug 2019 09:31:14 -0000

Qin

Thank you for the revised module; top posting on two points I do not see
fixed in -09.

I see no reference for

802.1ad
802.1ah

And the example uses a 10. address rather than the documentation range
in RFC5737

I hope to look some more at the technicalities and so may have some more
comments - I would not post another revision just yet:-)

Tom Petch


----- Original Message -----
From: "Qin Wu" <bill.wu@huawei.com>
To: "tom petch" <ietfc@btconnect.com>om>; "Susan Hares" <shares@ndzh.com>om>;
<i2rs@ietf.org>
Cc: <russ@riw.us>
Sent: Monday, August 19, 2019 6:03 AM

> Hi, Tom:
> Thank for your valuable review. See comments inline below.
> -----邮件原件-----
> 发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 tom petch
> 发送时间: 2019年8月16日 20:00
> 收件人: Susan Hares <shares@ndzh.com>om>; i2rs@ietf.org
> 抄送: russ@riw.us
> 主题: Re: [i2rs] WG LC:
draft-ietf-i2rs-yang-l2-network-topology-07.txt
>
> Not ready
>
> The text says
>     /*Consider udpating this part to make use of
draft-ietf-softwire-iftunnel*/ Well yes, consider it and come to a
conclusion otherwise I cannot see how this is ready to advance.
> [Qin]: Good catch, will fix this. The idea is to align with RFC7224
and reuse iana-interface-type.
>
> The YANG module contains many references - good - but they are not in
the I-D references; again, not ready to advance.  I see
>
> 4761
> 4762
> 6325
> 6326
> 7348
>
> 802.1ad
> 802.1ah
> 802.1Q
>
> [Qin]:Fixed.
> IANA considerations references RFC7950 - RFC 6020 is better here as
all that RFC7950 says is go see RFC6020.
> [Qin]:Agree, will update based on your suggestion.
>
> OLD
>
>        This version of this YANG module is part of
>        draft-ietf-i2rs-yang-l2-network-topo-07;
>
> NEW
>        This version of this YANG module is part of
>         "RFC XXXX: A YANG Data Model for Layer-2 Network Topologies"
>
> [Qin]:Fixed.
> You also have this unsuitable reference twice in the state module
> [Qin]:Fixed.
> The state module lacks references for the imports
> [Qin]:Fixed.
> The state module description clause seems misleading; it is only the
state part of a module when NMDA is not supported.
> [Qin]:Fixed.
> Appendix A - is it Normative?  The customary convention is the
Appendices are not unless stated otherwise and there is no statement
here.
> [Qin]:No, will make this clear.
> 'An Example' does not use the addresses set aside for documentation
> [Qin]:Good catch, will use RFC7042 recommended address range.
> What is the closing date for this Last call?
>
> Tom Petch
>
> ----- Original Message -----
> From: "Susan Hares" <shares@ndzh.com>
> To: <i2rs@ietf.org>
> Cc: <russ@riw.us>
> Sent: Friday, August 09, 2019 4:42 PM
>
>
> > Greetings:
> >
> >
> >
> > This draft on L2 network topology has been reviewed by the I2RS WG 3
> times.
> >
> > However, in discussion with the ADs it is deemed appropriate to do
one
> more
> >
> > WG LC and include any input from rtgwg or grow.
> >
> >
> >
> > Please indicate whether you support publication of this document.
> >
> > In your comments, please indicate "support" or no "support".
> >
> >
> >
> > If you feel there issues that need to be resolved,
> >
> > Please indicate whether these issues are editorial,
> >
> > Yang syntax, or technical content.
> >
> >
> >
> > It would be helpful to indicate whether you know of
> >
> > Network deployments or potential network deployments of this draft.
> >
> >
> >
> > Cheerily,
> >
> >
> >
> > Sue Hares
> >
> >
> >
> >
>
>
> ----------------------------------------------------------------------
--
> --------
>
>
> > _______________________________________________
> > 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
>