[i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology

Stephen Cheng <Stephen.Cheng@Aviatnet.com> Thu, 09 July 2020 04:53 UTC

Return-Path: <Stephen.Cheng@Aviatnet.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 6309E3A0F2E; Wed, 8 Jul 2020 21:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aviatus.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 hC1DJ3bpxzoe; Wed, 8 Jul 2020 21:53:21 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2089.outbound.protection.outlook.com [40.107.243.89]) (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 55CD43A0F2D; Wed, 8 Jul 2020 21:53:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CSFmwhXmgRePUh8ofqoBVGv0maLLMymfobKJxHmfzCrs7EGHxubjLkA1cx3bnPMfTzI1pTNBqVaaDxfHteRqOW4zz9xTvUg+fjO4vEkyf1Bg1EHffrvTw3FsneTkuV+P4kPrN9q4r5U8oHoRC61AD1mfhvSGVSQKtNehnV/Jr2MnXUZgxr36SM24hEvMqXaqV4LYCCcyv4mRvaaB9TgiFeauKQ0ya9Jhc17PjFF/qDPHZmMKhyR8RvZzx8IB619DdbP4LdBjaGqH86mXsp3OeA4Pj6yUs4GTr/Fi2qSVjS8FGv8mLYN9+NpcvkHdlh3yxVUz313YwJWtAESfptxh7A==
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=nYIrn8kuMph6/xKU4d0mbecqYwBY+3zEL5Mg6L0+Mzc=; b=O5IZFLxrR0AXPMG89pYaAgo63UQSbSVPuYauSaYXfxyBKw8FxGXhI94eOkHni6Uc49AzjwFm24IH6RoSu7/pr39jkxnFWiJDqiMBYDAyJebcHDl3X8l6jd7tXOHX7QiV3kUOcvR3RqsYUnC9+QIcWCydE5P6i6GFckgMj5v2nSsAAC2ZgIWK7NgeKgUNVQgOAYObMl5VBAA0SJSzEn2kZewWFL2BZ2tyjqbO6SIINtgoqBAySwKCCWEtMQAUTQ+LXiVJPhh1R/UT9wlwXi0DA7P84hjtXq6Ql51oKMYFpF3i6LRHJ3QB3VKrp5w2kEe1kvm1J3DczX0Q+JmWUShTGg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=aviatnet.com; dmarc=pass action=none header.from=aviatnet.com; dkim=pass header.d=aviatnet.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aviatus.onmicrosoft.com; s=selector1-aviatus-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nYIrn8kuMph6/xKU4d0mbecqYwBY+3zEL5Mg6L0+Mzc=; b=j/Ek/KDofhRG1/PBPH4rzHOxO+y4gn5PVpP6I96YT/uRfMYgGqpg+c1ruFt78079iTrBhOsJngWefe6lM8J7wCBEDmqM3s+ZB+IevBnNAMce0PQv4bTt4zE0BmwCh7Z/KIDzoC1rsZGySq3K1nWfpDpObsTHJyzSmFbKAcEaZwk=
Received: from CY4PR2201MB1239.namprd22.prod.outlook.com (2603:10b6:910:66::15) by CY4PR2201MB1383.namprd22.prod.outlook.com (2603:10b6:910:6c::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.28; Thu, 9 Jul 2020 04:53:19 +0000
Received: from CY4PR2201MB1239.namprd22.prod.outlook.com ([fe80::351b:4d5b:7181:543c]) by CY4PR2201MB1239.namprd22.prod.outlook.com ([fe80::351b:4d5b:7181:543c%4]) with mapi id 15.20.3174.022; Thu, 9 Jul 2020 04:53:18 +0000
From: Stephen Cheng <Stephen.Cheng@Aviatnet.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>, "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology@ietf.org>
Thread-Topic: Mail regarding draft-ietf-i2rs-yang-l2-network-topology
Thread-Index: AdZVpANd0Kl70/UjS6GkTyoiV4KzCQ==
Date: Thu, 9 Jul 2020 04:53:18 +0000
Message-ID: <CY4PR2201MB1239E0511B0B27CDCC98E83E99640@CY4PR2201MB1239.namprd22.prod.outlook.com>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=Aviatnet.com;
x-originating-ip: [202.27.34.26]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2a7a79de-c6fb-464c-2740-08d823c3ffa4
x-ms-traffictypediagnostic: CY4PR2201MB1383:
x-microsoft-antispam-prvs: <CY4PR2201MB138325B20C471BC2E61A9AA499640@CY4PR2201MB1383.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04599F3534
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CmPcdbsfaWznPXETVgYPNkYSfRuIuUC43CzRki3MBZGm1DbtMzp1/wptBTbI7CArGIIfkv+xF1XEEnoIsJ982wGxLlmkJtaa5/SFog6TMqDAoW4sC1C91uczLbvWMGArghkREs4g0Oj9ZpcajoJMGvG1Ash1R8flIOAA6h2qRdvhxiJgcyaGA9oWoan+bvlOgsqwFP+/J4mfKzrFiOPT8qlrqCgDW/Rd3Txst40Co25gV6oBvJrXKvFdYKHzNc7bEvwe3kwPJsxHXV/1QotCBTPuHocrK7xNRtcPfHwX4PR2ELcQS6Px6I+ByDeoYqBIepo/0WAr0/Rret8Gcx/6SUq+yh92C/cqLUV7JLpoe0hmdZ3Wwwd/QYb2V8R3dTxiYJiezD/8v90bezZJ2atGrw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CY4PR2201MB1239.namprd22.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(376002)(346002)(39850400004)(396003)(366004)(316002)(9686003)(66946007)(186003)(26005)(2906002)(110136005)(86362001)(76116006)(450100002)(33656002)(166002)(6506007)(8936002)(7696005)(83380400001)(5660300002)(8676002)(71200400001)(55016002)(66476007)(52536014)(66556008)(64756008)(478600001)(66446008); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 0HgsuQI2e3vYt2skQbSPvgHxtDSbx5RKZi7oeSrP4skvqJOgZ1iT+HH4HW1BmGAugkF8N9TcRkRo/Egh2e84erFNNJVJPD4+KmxwCP+mFHCO1M0bPbWofhvUGFRm3550Bo5MA0/kv6Xo+0A+2gvsLWUttp7RjGW2YUkdkfWio87IAbFKc6F4iopGGkytUgKaDdAf75b3qqD3ADCMsNO1PfhPCvIwbLDCc4mR3BKwcGjei86lkqeLMSujtp+vhcEJmsjEwuvFaDb1OdaGUt04/X41g5xaTTztI/qFGxkHyx7ihHlNI27NM4cuA8qBnuJBzd6sEgO6qbFdr+k957Q+QhGqFhdjKc+OMuQpwOlVQGUcOejZFaKOIT9Wj9jx/+frJZEvIFYRLBUbZ7AD4HbFJahbtfl0LEcuP80wNiXmaR0Vy+s52ng3edWIVH6WDSP3GZKjgr7VjUytjRdBdJa6en43YonozZxdzEKGTi0yW9g=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR2201MB1239E0511B0B27CDCC98E83E99640CY4PR2201MB1239_"
MIME-Version: 1.0
X-OriginatorOrg: aviatnet.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR2201MB1239.namprd22.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2a7a79de-c6fb-464c-2740-08d823c3ffa4
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2020 04:53:18.4559 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8d7d22b9-3890-4eef-95a6-a226e64151be
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ZKXH/91/2pk7jo/F+e3uMnKF45BqT13Lgby6Jx7/K1z5Y91zywcT6E39XNW0Aqocm1cD5m4ppJLFF5/h6/UoJV1JvPNVEus3WFMGghZcNoA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR2201MB1383
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/sm5EoXj2cQxv3zZYooGoluRx3yg>
Subject: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology
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: Thu, 09 Jul 2020 04:53:25 -0000

Dear authors,

I have a number of questions regarding this L2 topology YANG.


  1.  Does draft-ietf-i2rs-yang-l2-network-topology support the modelling of a termination point that maps to a VLAN sub-interface?
This capability would facilitate the creation of a topology stack for the following use cases:

     *   Mapping a ietf-l3-topology TP over a vlan sub-interface
In this case a TP in ietf-l3-topology instance would be supported by a VLAN sub-interface TP in the l2-topology
     *   Mapping different VLAN IDs in a L2 ports to different services

                                                               i.      For example, on a particular L2 port, VLAN 23 might be an attachment circuit for VPLS #78, where as VLAN 99 might be an attachment circuit for L3VPN #999

If draft-ietf-i2rs-yang-l2-network-topology does not have the capability to model VLAN sub-interface as a TP, is there a different way for draft-ietf-i2rs-yang-l2-network-topology to support the above use cases?



  1.  The VLAN sub-interface YANG (https://tools.ietf.org/pdf/draft-ietf-netmod-sub-intf-vlan-model-06.pdf) being developed has some overlap with draft-ietf-i2rs-yang-l2-network-topology. It would be good if there would be better alignment between the two:
     *   Use similar definition/fields where possible; even better use shared grouping definition

                                                               i.      For example outer-tag and inner-tag

     *   VLAN sub-interface YANG (https://tools.ietf.org/pdf/draft-ietf-netmod-sub-intf-vlan-model-06.pdf) flexible encapsulation supports symmetric and asymmetric rewrites, which does not appear to be supported by draft-ietf-i2rs-yang-l2-network-topology.


  1.  Consider the scenario where a domain controller implementing draft-ietf-i2rs-yang-l2-network-topology is also implementing schema mounted ietf-interface to model the interface stacks of the managed devices:

  *   Is there a mechanism in draft-ietf-i2rs-yang-l2-network-topology to associate a L2 TP with the corresponding interface entry in the schema mounted ietf-interface?


  1.  For a LAG link, would the LAG TP be expected to be also represented by /nw:networks/nw:network/nw:node:termination-point/tp-id/supporting-termination-point to its membership TPs?
It would be useful to clarify for uniform implementation across different vendors.

Thank you.

Warm regards,
Stephen Cheng
Aviat Networks