Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network-topology-07.txt
tom petch <ietfc@btconnect.com> Fri, 16 August 2019 12:00 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 18B6E120089 for <i2rs@ietfa.amsl.com>; Fri, 16 Aug 2019 05:00:32 -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 4_qRWK8xrOWY for <i2rs@ietfa.amsl.com>; Fri, 16 Aug 2019 05:00:29 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20092.outbound.protection.outlook.com [40.107.2.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D6EA120072 for <i2rs@ietf.org>; Fri, 16 Aug 2019 05:00:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Eaes9Hxos82CKNnLNWeoOFbpNyO/UkQg2Og0DQOTC1WweE1q3vWuH7L+XCwOuxPTsXseOGsALtTLyfwsfZoBW3CfIau8ToXI1Z8Bud8/BwtWDIACZyk9L6q6ZmbJQktaRrH7ED5ij3X3i9sM6+mYJYQDxChjWt9nZllvdQ0tWvtdtHpNwSmbeJoWVpMBQbEqptzDW3yZbMW/8GtpWuuo/O5HekvJ9uaRZLHhebwoTD24DvJmFDc3J68ko6uT7JsO2ik+Fukml0SohfRjTSp7LH6vtP5TP0VVdbX1AbaVq5OrEJ9p8RuE1BayzDH57j9HyZFgglrVkfdxAnNE4IDWsg==
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=03dzntOoViFGm3+hir62zXDjgacGFWKXWwzs6RZYU2A=; b=IWeLz/cMym//G588Em3zucVdUy4+lP/WKLVfCK7SA5HtdgBP4sohAS3rLKMc8iWrTBCBOzqpDpniI04b1JMy142XHaZdXyflsbkwrlpcZ4aXlu32rqZx1Y/C92dzgxHRWKn66p5Hff0S3gPz8KLwuEonqVXy/pGmegAiJUp5SCWbcE0r0owlheDk4B/pJberMJqkuYpGjCUyzKLizOeTXitB+V3e80rZWnuwPZ0aI6ODGuejW/qo83S/irzLhc3Ug3YSoY5l9ZhvSy2NSToNRLonS2Nqv3kHtRwxD+1xo4LvSP+JxBJtVLVm8RsiI5ksA6WJFZpwbn4USqMDLDGzhA==
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=03dzntOoViFGm3+hir62zXDjgacGFWKXWwzs6RZYU2A=; b=guiTcrdrx21F5lMrEDqDXee8WYZaLOZ+LxuFefvfKZ9BJqAH0D6dcShE+NdpRCQ2X9AmLX5sxx5/DaC054TuNvAFPUayGUnwSl1h8NFhYph3f7QsARJ+7JgXenjW6LlSRlcPGkp0fAHE18pc8EMnbvB9I13QP9RmVyUaV29WRo8=
Received: from AM4PR07MB3204.eurprd07.prod.outlook.com (10.171.188.157) by AM4PR07MB3076.eurprd07.prod.outlook.com (10.171.188.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.16; Fri, 16 Aug 2019 12:00:27 +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.2178.016; Fri, 16 Aug 2019 12:00:27 +0000
From: tom petch <ietfc@btconnect.com>
To: 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: AQHVVCoxDpM09nApkUOB7XQcxUVY7A==
Date: Fri, 16 Aug 2019 12:00:26 +0000
Message-ID: <041701d5542a$0d1a88a0$4001a8c0@gateway.2wire.net>
References: <024e01d54ec9$09a97070$1cfc5150$@ndzh.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P123CA0045.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600::33) 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: d4cfac3f-46de-4b08-8a27-08d7224153a0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:AM4PR07MB3076;
x-ms-traffictypediagnostic: AM4PR07MB3076:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <AM4PR07MB3076561C88E7C090966FE288A0AF0@AM4PR07MB3076.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0131D22242
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(39860400002)(396003)(376002)(346002)(189003)(199004)(13464003)(6116002)(71200400001)(50226002)(81686011)(53936002)(76176011)(66066001)(81156014)(81816011)(4326008)(478600001)(71190400001)(6506007)(386003)(25786009)(6246003)(14454004)(316002)(66556008)(86362001)(66946007)(66446008)(64756008)(66476007)(102836004)(7736002)(966005)(305945005)(6512007)(9686003)(26005)(4720700003)(486006)(186003)(6306002)(476003)(14496001)(5660300002)(446003)(6436002)(1556002)(61296003)(229853002)(256004)(2501003)(3846002)(62236002)(110136005)(2906002)(8936002)(44736005)(8676002)(6486002)(52116002)(44716002)(99286004)(81166006)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB3076; H:AM4PR07MB3204.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Xn0HxiNbgCL2ykZ7hWDzzPkgXHcztrZQf/6w29j5xyDOCf2F8bVB1qf2iSm+/Te2dQGK8ui0ht6oEZcl0AxjCRnKwJ269HarH1AUT5Bo6pZj06ckXvV0ueR5EzE+U3euSKtfokTfVefMtw2RLz0R6NRA0vsszft13jUXe3yzTbk9/J+t6qAZlpR+lLZS2h4HI+KH+uGb3K4ToUIlZZJVy/zFDq45uNpCkHeZR4JzhEnEelsqo/X0lyMmKlEhJQMxBE09AGIQo8z2GHBx8iHt/7b3Fqg3B4kKWhN1sM6k8EIRFIglCvsTgHsAhveR2NTj/q8HzfkCLTZzHtd2W9SgKNDanoFwo/qczHMG1L34B6uZb+pp9iW+GpfgTCnnZP/tn1BhzVucSgw1UUJ5IsqMYcq67bRk7Z9WTIL9sm75MoE=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3896E65BCF6F144185B642B511F961CD@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d4cfac3f-46de-4b08-8a27-08d7224153a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2019 12:00:26.9472 (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: xWtMG5zLYm84GSQZAIH3NGpXP56Sd+vAyFbvwloWml0LYqWRP21B4HC2Q9R074LeQga4hkxMPPzTm01k9ui1Sw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB3076
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/0NtIKuMlCJvcyxdtDL92k0dz0Rs>
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: Fri, 16 Aug 2019 12:00:32 -0000
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. 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 IANA considerations references RFC7950 - RFC 6020 is better here as all that RFC7950 says is go see RFC6020. 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" You also have this unsuitable reference twice in the state module The state module lacks references for the imports The state module description clause seems misleading; it is only the state part of a module when NMDA is not supported. Appendix A - is it Normative? The customary convention is the Appendices are not unless stated otherwise and there is no statement here. 'An Example' does not use the addresses set aside for documentation 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] WG LC: draft-ietf-i2rs-yang-l2-network-top… Susan Hares
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Qin Wu
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Alexander L Clemm
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Dongjie (Jimmy)
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Linda Dunbar
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… tom petch
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Qin Wu
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… tom petch
- Re: [i2rs] WG LC: draft-ietf-i2rs-yang-l2-network… Qin Wu