Re: [netmod] Mail regarding draft-ietf-netmod-sub-intf-vlan-model

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 05 November 2019 09:50 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD5A120863 for <netmod@ietfa.amsl.com>; Tue, 5 Nov 2019 01:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=fFJvfGDo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=PUAMR3wO
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 QZnbL0T2I8j0 for <netmod@ietfa.amsl.com>; Tue, 5 Nov 2019 01:50:22 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E44DD120137 for <netmod@ietf.org>; Tue, 5 Nov 2019 01:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29367; q=dns/txt; s=iport; t=1572947421; x=1574157021; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=zxjY5B6CnMqyPbibVluWinmG3eS/nc8qcLMMpGl0nQE=; b=fFJvfGDotihSHXwcbCbUsEOOCTew1hB06MbPlDUaH3MYipUt+FUx2nbq 03fzOYKcGb4J7hpIzTkdnoSc0SpPnE5UQzBJgI/C8xB5YDNJ0wWyD6Tka HRxNlr0aNO+mZ7GunPSI7QxXE+LrE4eKPHToC69zNsjKSPoZUr32q+/Z2 Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3ASaowsR9eS6q+Cf9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVdSaCEnnK/jCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAABbRcFd/5RdJa1dCRkBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAREBAQEBAQEBAQEBAYFqAwEBAQEBCwGBGy9QBWxYIAQLKgq?= =?us-ascii?q?HZQOKe06CEJd+gS6BJANUCQEBAQwBAS0CAQGEQAKEDiQ1CA4CAwsBAQQBAQE?= =?us-ascii?q?CAQUEbYU3DIVRAQEBAQMSGxMBATgPAgEIEQQBASEBBgcyFAkIAQEEARIIGoM?= =?us-ascii?q?BgXlNAy4BAqRbAoE4iGCCJ4J+AQEFgTgDC0ODCBiCFwmBNgGMEhiBQD+BEUa?= =?us-ascii?q?CTD6EGwoBASA0gwyCLI0OiC0kgheWAgqCJIxmg2yFAYJrlnyOQ5lYAgQCBAU?= =?us-ascii?q?CDgEBBYFTATeBWHAVgydQERSDBoNzilN0gSiLFYEiAS9eAQE?=
X-IronPort-AV: E=Sophos;i="5.68,270,1569283200"; d="scan'208,217";a="435331337"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Nov 2019 09:50:17 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id xA59oHhK029184 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 5 Nov 2019 09:50:17 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 5 Nov 2019 03:50:16 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 5 Nov 2019 03:50:16 -0600
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 5 Nov 2019 04:50:16 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Sva8470WWb1C5weNm6nW2z37BJw2nrpudxr1duYiQQgTtKHG2jO2fvezzANog4xjSakCR5VExNbhmtiW7MGNu39/cM8fsJ68viIPWYxVdzafc01C969f5VxoxVw787wt+EGUHql1EPT3KV3dS0FqcQ1tVsPiAbYJe5FG4XsqsaHjG0KhaIjlo6QBvzgCMaShnELOF+MYXgCvxoplFFRenppZYJkjyeqX4V0KICKHZvjfVdP4GHcSKhaylaUQq89gH+HMet6vFOaUmDpJaEzbQxENkA9clVxHFLRo+8gOLtjZZ9u6I3gYFWkMr7F92UrIpV9sFbP/Td7Qeg11eojfLg==
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=YqFaES51y3LQtVAinp/BrUutRPR1Ec3d7eTBuRG0V6w=; b=Lt3xOtLkrq5EzIBX/f1V7Q3C9RAOOb/qeat+DWPd2hoTM3Q+NIUTlJjNm9as0Nrz8q8NWwUGYjCNBGta6RxsAQ3Hf3RreOv3du/n8Q4HwfqncE8ODm6xQmxyJ13Um9qeHHfuOLPHd1WzSawcwVsvI+NwQTUq3T/WL+kDsMy0tzRovMvqTPE9XT5YK0Yesw80ldszhe10oj8jzMo7H7LtDXIgoHUs63MDs/PP8mncLNxwfLFZsO10lHwUKySRSWwVPisugeor29yIM4CmQ9vmJTtEjBx0iXoCifgP+LqGFZMTHrdltHzLze4JR6smNiOHae96bid02RXK/FCT/475cQ==
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=YqFaES51y3LQtVAinp/BrUutRPR1Ec3d7eTBuRG0V6w=; b=PUAMR3wOcIkyOy2OB4mQtkYNtV8zEA625iCN8p2XoNA8ft+9L1N/p0pkh/CdEzOZPrzX3L2jUgp/0D8UXh68MAkIsVuhViZzUz2EYCRk2NNe40Wg+A7rf5WHAHWiOzHu8RmNN3IP3BzLxbnzQ+rJ+Rvz2q5N+02LLln7X99avEU=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB4126.namprd11.prod.outlook.com (20.179.149.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Tue, 5 Nov 2019 09:50:15 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::49b6:bc5c:bd3e:203c]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::49b6:bc5c:bd3e:203c%5]) with mapi id 15.20.2408.024; Tue, 5 Nov 2019 09:50:15 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Stephen Cheng <Stephen.Cheng@Aviatnet.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Mail regarding draft-ietf-netmod-sub-intf-vlan-model
Thread-Index: AdWSyl7cbaWiqA3FQnS6BKC6PM73AwAtkXJAAA9jFTA=
Date: Tue, 5 Nov 2019 09:50:14 +0000
Message-ID: <MN2PR11MB4366D22A90968E3B5975D496B57E0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <MWHPR2201MB1215C70D16303009DAC11294997F0@MWHPR2201MB1215.namprd22.prod.outlook.com> <MWHPR2201MB1215B39679CE1878DE333614997E0@MWHPR2201MB1215.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR2201MB1215B39679CE1878DE333614997E0@MWHPR2201MB1215.namprd22.prod.outlook.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.45]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ec8bdb14-0e74-40a5-5241-08d761d58efd
x-ms-traffictypediagnostic: MN2PR11MB4126:
x-microsoft-antispam-prvs: <MN2PR11MB41265281574017CC27340BE1B57E0@MN2PR11MB4126.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(346002)(136003)(396003)(366004)(189003)(199004)(2906002)(66066001)(478600001)(25786009)(7696005)(99286004)(55016002)(3846002)(790700001)(7736002)(236005)(229853002)(6306002)(54896002)(9686003)(74316002)(2501003)(256004)(5660300002)(6116002)(76116006)(86362001)(71190400001)(71200400001)(81166006)(446003)(11346002)(476003)(66556008)(66476007)(66446008)(64756008)(66946007)(8676002)(14444005)(6246003)(81156014)(14454004)(186003)(316002)(26005)(6436002)(76176011)(6506007)(53546011)(110136005)(9326002)(102836004)(33656002)(486006)(52536014)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4126; 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: BCL:0;
x-microsoft-antispam-message-info: kXxfvKhQF0BvTyuYMHZA8Pr4hkxQ9eftcVHjbuW2/QxFTdrZ0pGPuQZsWfGSUXVcZzS/klW6Qng4AEOCAf+cN3KhBEPNuo09GOIyZi/dhG+dXDGdw57gd1TzBJlzrj0zfoUXxkJ7AO5LmJWmz7PPpv9AHsBDgFPDSbs3oC0kk9IZaOwq5N+JMpSSZU6s/nhDOd0yFPG1uHBocZjmuCRvjBIazToLYG5IK79d0F+HHIIo+DxVKNXC2uC+QqzXmBpjEEY516RBP8d+P/b43MxyYC1iYWrvJpJpJa2LvGmIe+ygTiQfN2ZhCflM++S+NqlDYky6sM4Ib8J54psimszLXtX+ovDBUHcpbyBkJAi5a1+pY/xX4hy3XT5cp5KaIaUY38BZCXfFmrXPAKymLdOuO9Iao8NhjWtDdng4q29aw4qwYfe/5Iu2ZGctTrfEzaeV
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4366D22A90968E3B5975D496B57E0MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ec8bdb14-0e74-40a5-5241-08d761d58efd
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 09:50:14.9370 (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: +r6S+kAbgMV8oKSta4SSU0mSD+u+SDaiMV2gwQR7mTufspY/QuZmmjtgbvrla1IPDe4awTViMweL2uO7oITgKw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4126
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/vAqUc0Xu2uFKb668lLAxelfIMII>
Subject: Re: [netmod] Mail regarding draft-ietf-netmod-sub-intf-vlan-model
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 09:50:24 -0000

Hi Stephen,

I've just posted an updated version of this document.

The document is in WGLC, and I'm hoping that I can address any outstanding comments (including yours) over the next couple of weeks.

Kind regards,
Rob


From: netmod <netmod-bounces@ietf.org> On Behalf Of Stephen Cheng
Sent: 05 November 2019 02:30
To: netmod@ietf.org
Subject: [netmod] Mail regarding draft-ietf-netmod-sub-intf-vlan-model


Authors  of draft-ietf-netmod-sub-intf-vlan-model,

I noticed that the draft has expired, is there any intention to publish a new version in new future?

Secondly, I notice a possible problem in the examples in section 7.1/7.2.

In current (expired) draft, in section 7.1. we have in the example

       <interface>
         <name>eth0.1</name>
         <type>ianaift:l2vlan</type>
         <if-cmn:parent-interface>eth0</if-cmn:parent-interface>
         <if-cmn:encapsulation>
           <dot1q-vlan
            xmlns="urn:ietf:params:xml:ns:yang:ietf-if-l3-vlan">
             <outer-tag>
               <tag-type>dot1q-types:s-vlan</tag-type>
               <vlan-id>10</vlan-id>
             </outer-tag>

The type of of eth0.1 interface is defined as a l2vlan.

L2vlan is defined in RFC 7224 as follows, which means that l2vlan does not derive from ethernetCsmacd nor ieee8023adLag nor ethSubInterface:

identity l2vlan {

       base iana-interface-type;

       description

         "Layer 2 Virtual LAN using 802.1Q.";

     }


However in the current (expired) draft, ietf-if-l3-vlan@2019-03-05.yang<mailto:ietf-if-l3-vlan@2019-03-05.yang> says

     /*

      * Add support for the 802.1Q VLAN encapsulation syntax on layer 3

      * terminated VLAN sub-interfaces.

      */

     augment "/if:interfaces/if:interface/if-cmn:encapsulation/" +

             "if-cmn:encaps-type" {

       when

           "derived-from-or-self(../if:type,

                                 'ianaift:ethernetCsmacd') or

            derived-from-or-self(../if:type,

                                 'ianaift:ieee8023adLag') or

            derived-from-or-self(../if:type,

                                 'if-cmn:ethSubInterface')" {

         description

           "Applies only to Ethernet-like interfaces and

            sub-interfaces";

       }



       description

         "Augment the generic interface encapsulation with an

          basic 802.1Q VLAN encapsulation for sub-interfaces.";



       /*

        * Matches a single VLAN Id, or a pair of VLAN Ids to classify

        * traffic into an L3 service.

        */

       case dot1q-vlan {

         container dot1q-vlan {

           must

             'count(../../if-cmn:forwarding-mode) = 0 or ' +

             'derived-from-or-self(../../if-cmn:forwarding-mode,' +

                                   '"if-cmn:layer-3-forwarding")' {

               error-message

                 "If the interface forwarding-mode leaf is set then it

                  must be set to an identity that derives from

                  layer-3-forwarding";



               description

                 "The forwarding-mode leaf on an interface can

                  optionally be used to enforce consistency of

                  configuration";

             }





           description

             "Match VLAN tagged frames with specific VLAN Ids";

           container outer-tag {

             must

               'tag-type = "dot1q-types:s-vlan" or ' +

               'tag-type = "dot1q-types:c-vlan"' {



               error-message

                   "Only C-VLAN and S-VLAN tags can be matched";



               description

               "For IEEE 802.1Q interoperability, only C-VLAN and

                    S-VLAN tags can be matched";

             }



             description

               "Classifies traffic using the outermost VLAN tag on the

                frame.";



             uses dot1q-types:dot1q-tag-classifier-grouping;

           }


As such if the type of eth 0.1 is l2vlan should outer-tag etc be available to this interface, since l2vlan would not satisfy the "when" clause?

I believe there are similar issues for other interfaces too in section 7.1/7.2 examples.

Warm regards,
Stephen Cheng