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

tom petch <ietfc@btconnect.com> Wed, 21 August 2019 08:53 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 6131412088E for <i2rs@ietfa.amsl.com>; Wed, 21 Aug 2019 01:53:26 -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 tZrLFewo9YF0 for <i2rs@ietfa.amsl.com>; Wed, 21 Aug 2019 01:53:24 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00133.outbound.protection.outlook.com [40.107.0.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1992120122 for <i2rs@ietf.org>; Wed, 21 Aug 2019 01:53:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Vp4Apjt1C49A7kGkbOKtCs6MexuvA6uDjNLiIChSgLpz7PMO7hsf+rl2/JymMpKfasv0yxh4cTYfc6E33YSwxCtATxZ6MV9yKnMKojdy4t0xjsKf9bdUi2lZ+yl5S73CogbalF6r/CNUkh9Zc2f43no8qijp3L6Ad42Vhu0L2eq3nwmWDpQKTTma8752mR67X6XhPS1INtXIZqgysRZ/GWrd8xUnxXXeN2MVXMkR4PDb/p9av8ab7qjldMhkckAWUnPlvgTFiEO9hW23d86C/G5ElIjR7GVgI8qBXvfMi2g1tABzAt2Z+TrYHw+inxUNAEjG4hqTkkvrspbPnqEmCw==
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=eOF3yCDKk2f2J/OO+dPksH71u+q+Ab2SHxzTtlmAT0k=; b=LMhvE88peA2ofkLSuWUTQLxEfUxADLJ1DoMMPpa38LVPlzCSJVgogqCpROX28rvtdrBIT/OUZ/kdHpMCKLE88ZRlwHttVNjRFp0pMb2OZNP1umgxioQFe+2xiON03sVFOhRUcanlp252WODXEu1bNafs946XNYb4HViXkXbr19ctpFarK8+U3Qt9Vwmwwz9YlBjoqkyb/oQhQxF3eobdPiZyjpoa3gVbu9EIhUX+1/yJ9NqUdkiA5iroKEl805n/p/XtEbEgPtOjDoI1CIGJ8fRz6hNyQVfO+JrdJpazdRTFMbVIyiwtzi1NKAIHXP+7XjjhQTWkjTh9WJvGwNgwnQ==
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=eOF3yCDKk2f2J/OO+dPksH71u+q+Ab2SHxzTtlmAT0k=; b=ALQAbW7m42KJehCQwXJYu+++IEKhWrNeCheaQRvvjz51j5WAi1MTyJolczqFMAhIyylu0SwyeHliyWAjnnqQx8jxKhEg2XdlThPlsMIBIuIEj3QltLaW3c/Yf6ySbaZRprkDJGsGQlMl1ULWTOW990QkFsVnqZ+CZToBjl2lr6I=
Received: from HE1PR0701MB2283.eurprd07.prod.outlook.com (10.168.36.20) by HE1PR0701MB2140.eurprd07.prod.outlook.com (10.168.35.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.15; Wed, 21 Aug 2019 08:53:20 +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; Wed, 21 Aug 2019 08:53:20 +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: AQHVV/3hO7vGRJjHZE6wpjtZc1pCJg==
Date: Wed, 21 Aug 2019 08:53:20 +0000
Message-ID: <00b701d557fd$b9fcea00$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: LO2P123CA0009.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:a6::21) 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: ecfef02f-f794-4e52-840a-08d72615040a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR0701MB2140;
x-ms-traffictypediagnostic: HE1PR0701MB2140:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <HE1PR0701MB2140AAE3FEEF6AD3110938A9A0AA0@HE1PR0701MB2140.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-forefront-prvs: 0136C1DDA4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(376002)(366004)(39860400002)(346002)(51444003)(13464003)(189003)(199004)(966005)(61296003)(44736005)(6436002)(229853002)(8676002)(8936002)(81166006)(71200400001)(81156014)(71190400001)(478600001)(6486002)(6512007)(9686003)(6306002)(14444005)(316002)(14454004)(256004)(99286004)(2501003)(50226002)(86362001)(305945005)(7736002)(53936002)(3846002)(6116002)(66556008)(66476007)(64756008)(66446008)(66946007)(6246003)(2906002)(4326008)(25786009)(44716002)(62236002)(66066001)(4720700003)(1556002)(5660300002)(110136005)(26005)(66574012)(52116002)(102836004)(486006)(186003)(476003)(81816011)(81686011)(76176011)(446003)(6506007)(14496001)(386003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2140; H:HE1PR0701MB2283.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: RGIbxgFQXIl6dt6LQ/dYb9i07RErRDhOrhwqsR3aw7TaUh/SQiTiyS59WT+SuoIq1j2JWRFSJxPw/j5uZ8V0eXZ+XdbH9fQE/Opmd7LJ0IgbAhQJ/HmKQcs9jX/1I8ihtsfgkoORssMGKwqWBhyHlpGzSJM2cfd414BLiKiyxVTy+TLwGH0mMKc5sk80DZqTIX8DjvSZD7lyXdlr6Ya5sK1FTlwN5C8Ekf9ciV1oOD6OwFeFvxC3O1V9Iz0Omb9PEeH7Gl0QIOSuPe2rH+mfjT/o/ZSirw16vpBpU60ESRPedE4OwWAvKVL8anXdt7ym0KVXazenPyfjAzagXtNs+PLj1qu8Knt2CnJNRSTc5VJkEmF2DaoLhFge7kEwUo5gdWJLvNYRbBfVPn+OYBRbPbswrzXi16ceGbK2NwRVVU4=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="gb2312"
Content-ID: <43B82C8BB72BD9479B35146B8AA7CE76@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ecfef02f-f794-4e52-840a-08d72615040a
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2019 08:53:20.4679 (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: O35NuJwl3CqH2y5HNoFBhdwYlvylP+XoiAtU05V5ysSREtvFuGzEy8rgiMhrSWwkZIqm5loz8CCQgfQ6glrB1w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2140
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/B5pV_B5_fX0K_SxLHp4K1ZYFtT8>
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, 21 Aug 2019 08:53:27 -0000

Qin

You had a note in -07 about whether or not to import definitions from
draft-ietf-softwire; and now I see that -09 imports definitions from
IEEE 802.1Q.

Um.  Different.

I have seen this before but in an I-D that AFAICT never progressed.

I am uncertain what the implications of this are, in terms of the
evolution of the model, of the YANG language and so on, given the
different philosophies of the IETF and IEEE.  I think that it needs a
wider review than it will get on this list so I will flag this to NETMOD
and perhaps again at IETF Last call.

Tom Petch


----- Original Message -----
From: "Qin Wu" <bill.wu@huawei.com>
To: <i2rs@ietf.org>
Cc: "Susan Hares" <shares@ndzh.com>; "tom petch" <ietfc@btconnect.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
>