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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 21 August 2019 09:18 UTC

Return-Path: <rwilton@cisco.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 4A4D5120809 for <i2rs@ietfa.amsl.com>; Wed, 21 Aug 2019 02:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=IDh8nJhx; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=XR/cvNow
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 MH6vFzIkPg2Z for <i2rs@ietfa.amsl.com>; Wed, 21 Aug 2019 02:18:15 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 103A1120147 for <i2rs@ietf.org>; Wed, 21 Aug 2019 02:18:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6684; q=dns/txt; s=iport; t=1566379095; x=1567588695; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ly/HvQtMzaGJpKqp/0q88MUxss81bD90jFjZOBCgXc0=; b=IDh8nJhx+UrwABCNy1y1xR7tsZbRBAQgFg1S1ByjhnHVCtbW95rhns6T hYjFe2xnGxg9VjS4SGaasjf0ggM8w6rYbX/Oq7ghBzvPhoiOA3cbX74d0 pwTZvQBshYK8SCP8TfEJ9DU3z5hmRfDZqNLWDQI9mjJNj0KE0K2lAUZX4 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AJo0/3R1tfa2QI7htsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxKHt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQE1L6KOLtaQQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAAANC11d/5pdJa1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVQMBAQEBCwGBRFADbVUgBAsqCoQVg0cDinyCXJdlgS4UgRA?= =?us-ascii?q?DVAkBAQEMAQEYDQgCAQGEPwIXgkMjNgcOAgUBAQQBAQMBBgRthScMhUoBAQE?= =?us-ascii?q?BAgEBARAREQwBASwLAQQHBAIBBgIOAwQBAQMCIwMCAgIlCxQBCAgBAQQBDQU?= =?us-ascii?q?IARmDAYFqAw4PAQIMjlyQYQKBOIhhc4EygnsBAQWBMgEDAg5Bgw4YghQJgQw?= =?us-ascii?q?oAYtoGIFAP4FXghc1PoJWCwEBAQEBARaBLxqDCTKCJoxPgkicQgkCgh2GaI1?= =?us-ascii?q?sgjFthkOOZY1bgTaGLYRgi0sCBAIEBQIOAQEFgVcLJoFYcBUaIYJsCYI5g3K?= =?us-ascii?q?FFIU/cgGBKIwaAYEgAQE?=
X-IronPort-AV: E=Sophos;i="5.64,412,1559520000"; d="scan'208";a="617896230"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Aug 2019 09:18:13 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x7L9IDdK011183 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 21 Aug 2019 09:18:13 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 21 Aug 2019 04:18:13 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 21 Aug 2019 04:18:12 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 21 Aug 2019 05:18:12 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BPdcvtpcBtf4VQwEH15jou5hb8F2YvON83PA5RGu8k6H/bXcFDNTslOjoizbgLd2YP54LtaGscx8IU8Ig8i/vByV+Qd7d0ti0gugLPVWJA7O/1OSsQffBcDYImjdN51LA422YB7XRoc6XulIkdivI6eIM7YkPLE9IAYsKZZ79MlgMM1EtQyfRm/VmPyU6go/mL4W0KgvqLLGc9GQ4pj4mam4FDQ3ukf+AH4c1zytD2qhNe+TKGDLONIv0gxtHMrefjB+VvHDd2J/AQGRHCKplxFny6OP+XcCcXz/js2WAfIVRnR9RVtUYjaMSq6Crxl9aCrxTHytG7NvksFbD1TwmQ==
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=ly/HvQtMzaGJpKqp/0q88MUxss81bD90jFjZOBCgXc0=; b=oVUyYuZw8RlIjmIOUaaTyvZG4GKiZmMyftEVWstPguvcs1VdblTSVzAbmKLZGNnEYUYhHdJclUzmmMFVxSShe8i9ob6Pz4li3Uc558NtzLG+xL0FKhnmEh55iuIh2OwunPrV20AdZAUNSNxLxoE+DxJxhxw6vBV4luENuzTCepJFiGs9+/nC0GxELZgYwXzmtyjMi0/vj95jnxRLBC6mES1RF07IaaD64jtFu7RKzs8IpuNjt7cKbreqIpfqOLYNbXxMHSZsx5hTaduaifg4HBGHqol0+wQhAguzj6wBz8+Hzt3F5Nu0UPzf9VrZTqthtpLEMEMeZq8NrPSFrsK5Pw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ly/HvQtMzaGJpKqp/0q88MUxss81bD90jFjZOBCgXc0=; b=XR/cvNowDnoRhH480I+zplIK9HYAL59Gh/EeXhGPNJXU4WAeVam2wxeS8jiDX9ddPg2Y94V6rRjc5i6H2zIYSmeHnAJdcyGOnzAzhlJEeaPeJzDZ3DjBvEVlEGu5OWmnmmb/xVJIgjwFWeHPcGhw1AEybqIoqcsXUt01esJybdw=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3789.namprd11.prod.outlook.com (20.178.252.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.19; Wed, 21 Aug 2019 09:18:11 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::6db3:f4c:467b:30f6]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::6db3:f4c:467b:30f6%7]) with mapi id 15.20.2178.020; Wed, 21 Aug 2019 09:18:11 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Qin Wu <bill.wu@huawei.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: AdVX/j2iSmACvf5sQbGbTbakgZnlIAAAqUYg
Date: Wed, 21 Aug 2019 09:18:11 +0000
Message-ID: <MN2PR11MB436662062656950A03C89609B5AA0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA92AAC97@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA92AAC97@dggeml511-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.59]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e2ae54c9-2a1f-4bb7-edfb-08d726187d02
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3789;
x-ms-traffictypediagnostic: MN2PR11MB3789:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <MN2PR11MB37896C428D19224F387D1C9BB5AA0@MN2PR11MB3789.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0136C1DDA4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(346002)(136003)(396003)(189003)(13464003)(51444003)(199004)(76176011)(186003)(476003)(446003)(11346002)(8676002)(14454004)(81156014)(7696005)(81166006)(486006)(74316002)(53936002)(66574012)(66946007)(66476007)(66556008)(64756008)(66446008)(76116006)(66066001)(6506007)(53546011)(102836004)(7736002)(26005)(33656002)(229853002)(305945005)(6246003)(55016002)(6306002)(256004)(14444005)(2906002)(25786009)(86362001)(9686003)(3846002)(6116002)(52536014)(110136005)(5660300002)(966005)(8936002)(6436002)(478600001)(99286004)(2501003)(71200400001)(71190400001)(316002)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3789; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 0i0vEpkT58jZeaK17ycD5LrMMYseEcSeIA1T1xydTo5yRataUhgq7FQ64oyiErkoYRI8IHvruzdvnZmCivvL0lWlb/mn6SJK/srQCRi12AHiM/MOuy9I8JfgVzfint8n096yeKWbixVisq3ODQXdSzcmSFpZy3FJcPa811/08nYiNALw1VvyZVSmwX2QJXLUdzmlXdLOs5ZVy+Wi693sQZX9kb9iIDy5/W0xT1zKbXAUg5MXFBJMCZJm+VI0fpbD46rbehwgM4+BAUoQnaWHefQOrkf5PZalliZ/gCfbd/FUSoRzEJIyQuMSuncTGnmUx0ASiJ4KoD3G8b1602x5JTm1BwT/1duRzPXwXXPRV9VYdC6/O3QtaAxDKHdbHk61VVxV7FB0jxG0z9ZuMkoxBYMjrJlZbL20DTmEXyg1MP4=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e2ae54c9-2a1f-4bb7-edfb-08d726187d02
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2019 09:18:11.3179 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: T3oVfH1l3wtEjim5TAEs632baDQucPwvHkJjJrApdyPbvL4fDrJBWl6bnNiZybAFFLxGguPzCpmUCVcEzMXvUg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3789
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/lgZE_EFtMqu1VOATf3FR3M8IUC0>
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 09:18:17 -0000

Hi Qin,

I think that you should use ieee802-dot1q-types.yang.

Similarly, if required, I would expect IEEE to use an IP address type defined by an IETF YANG types module rather than define their own version ...

Thanks,
Rob


-----Original Message-----
From: i2rs <i2rs-bounces@ietf.org> On Behalf Of Qin Wu
Sent: 21 August 2019 10:02
To: tom petch <ietfc@btconnect.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

Hi, Tom:
Yes, I am also not sure whether I should reference ieee802-dot1q-types for vlan type definition.
If you see this as an issue, I am fine with falling back to the previous version and remove reference to ieee802-dot1q-types And define vlan type in ietf-l2-topology.yang as follows:
"
    typedef vlan {
      type uint16 {
        range "1..4094";
      }
      description "Virual LAN using 802.1Q";
    }
"

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

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>om>; "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
>

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs