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

Stephen Cheng <Stephen.Cheng@Aviatnet.com> Tue, 05 November 2019 02:30 UTC

Return-Path: <Stephen.Cheng@Aviatnet.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 7C72F120033 for <netmod@ietfa.amsl.com>; Mon, 4 Nov 2019 18:30:20 -0800 (PST)
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_DNSWL_NONE=-0.0001, SPF_PASS=-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 RbrZoqazbm_1 for <netmod@ietfa.amsl.com>; Mon, 4 Nov 2019 18:30:17 -0800 (PST)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0624.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe41::624]) (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 544E412000F for <netmod@ietf.org>; Mon, 4 Nov 2019 18:30:17 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jaUiY4V/ZTqOscg6bf+wTjOWcHUT7gUXUn6p9h+gIHBKgSW6TTT8ycbnHyAfmL2ZoPFWxOQOV21sClCeE4zmdMXPp8gi7Kqq9Tyn4/XDWPuoTDZtM1lWo8im5zhHfaOoT+rLnpKuzerbUWAWGBEsn5Y0FUSqqawIOIB7bZ45Vn7nu/cXyZvXh5F005gOWC+nfx53tRKOHhOovW99y5FRIXMz8U1t6q4QUZCpSpRKykP5xco9XUTyO70T7ynmt7ctbKYNccP7WnX6byAv/KaLAzEuNz9gz/TS+QL5mwDyFlMRuvmq+bVkIkZqkAqeXXCLwaKaClCAtqDvQLYXw7TKLQ==
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=oEfVmimayN3kewoXuLrYZav8ObwrlzHERnQfV8Ef57Q=; b=AaihXsd9Y4n5bR/OLmPVhV6rBKx51Jf5qXyp89W1m0UXD8vFlOYdIR28prVN0TEMbEGQ0tWmwxreHBk/P0ecpq0waLQiBNTN/KaAS6BY6fAVzGVaNyt6I5MbeZqnc0HHWuxOJ3+9T3S7hN0AZIY1Dd6FNze2fcGzyANn7YFlYAxvV2jgg0FKbWyyD58JtJA84mOJ1i7LE5zQ8WcNw7oMgKZqPeK5eT8B0EwzuAprhqbv8QE9EgvYx6tpkT3F1+2RTNDiAqW6SSAmeKNfb9HFQh2SeoTvaV40lcGa6hpRY4zT6HVTj390b8kUqi9X70zpoO+dNy8XBof+CtvbqjzL4A==
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=selector2-aviatus-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oEfVmimayN3kewoXuLrYZav8ObwrlzHERnQfV8Ef57Q=; b=XXTDgp89qj+Fa5ifd9k89hQ7hd2gribkhPnYYMFMrF/4cHtDX5ZQLZb0fse7YrPduwATgpFYe+NyC4yCDevopLUt/MH6jsGvwJa3DOGI1Ap2p/thWKLY65yppgTsrr2kryhrkU/JDI8sxE/KXlsvLsW5e9FbHQXYDmw7ZAJlw+M=
Received: from MWHPR2201MB1215.namprd22.prod.outlook.com (10.172.63.138) by MWHPR2201MB1709.namprd22.prod.outlook.com (10.164.206.151) 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 02:30:02 +0000
Received: from MWHPR2201MB1215.namprd22.prod.outlook.com ([fe80::ed5b:20ef:f55:86d9]) by MWHPR2201MB1215.namprd22.prod.outlook.com ([fe80::ed5b:20ef:f55:86d9%11]) with mapi id 15.20.2408.024; Tue, 5 Nov 2019 02:30:02 +0000
From: Stephen Cheng <Stephen.Cheng@Aviatnet.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Mail regarding draft-ietf-netmod-sub-intf-vlan-model
Thread-Index: AdWSyl7cbaWiqA3FQnS6BKC6PM73AwAtkXJA
Date: Tue, 5 Nov 2019 02:30:02 +0000
Message-ID: <MWHPR2201MB1215B39679CE1878DE333614997E0@MWHPR2201MB1215.namprd22.prod.outlook.com>
References: <MWHPR2201MB1215C70D16303009DAC11294997F0@MWHPR2201MB1215.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR2201MB1215C70D16303009DAC11294997F0@MWHPR2201MB1215.namprd22.prod.outlook.com>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Stephen.Cheng@Aviatnet.com;
x-originating-ip: [202.27.34.26]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 22829e91-364b-4ed6-57e7-08d761980feb
x-ms-traffictypediagnostic: MWHPR2201MB1709:
x-microsoft-antispam-prvs: <MWHPR2201MB170957CCCF71C299BE6A276C997E0@MWHPR2201MB1709.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(39850400004)(136003)(376002)(396003)(346002)(189003)(199004)(186003)(9686003)(66446008)(14454004)(790700001)(81156014)(81166006)(8676002)(1730700003)(76176011)(2351001)(2501003)(476003)(14444005)(66066001)(256004)(7696005)(6116002)(3846002)(25786009)(74316002)(5660300002)(236005)(8936002)(11346002)(316002)(102836004)(66946007)(6916009)(446003)(66556008)(86362001)(6306002)(54896002)(66476007)(64756008)(52536014)(99286004)(26005)(5640700003)(7736002)(76116006)(33656002)(2906002)(55016002)(71200400001)(71190400001)(486006)(478600001)(6436002)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR2201MB1709; H:MWHPR2201MB1215.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:3; A:1;
received-spf: None (protection.outlook.com: Aviatnet.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: s9tNBCKbLmHmWmjS72+3poghXF/k72/O4sHz7C0esp0WIHTuoyLEwzKlG6TWXAUbt0VzpwOD8TihMVCeFPVj3n6TSYKlIR+gxBFWj2XtG2l2f7H6dTks+tTQny6TgsPIR+dwYcGCZdMCS1rkphcCQzamRTExBI5MQyLsIg5yUk+XLQ4SxhTmTFxyQDBY1q/hBvLWKOkaThoR7pYKvbfKvmlZYfqDj02KTvqvo5OodwPvJI7HeER7w8DtxJ0G2joblxrRbztwkSDEAtbexfalU/AOoQk07ZCkRaam1cE7fU2EDGpxH1GdaE5xG2N8JnbmW8Fh0SD5qRpyd/iXNYx+JkH0DwO/ohwaWDWbnFApZ/fNBsRFhVtcbWHlnSBX0562AxuLjsi3Kyy+jeTuaAQpy8YZ+lPOgBCRfHvR3wP4z31WZEndqkNp4awsKlao7gkq
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR2201MB1215B39679CE1878DE333614997E0MWHPR2201MB1215_"
MIME-Version: 1.0
X-OriginatorOrg: aviatnet.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 22829e91-364b-4ed6-57e7-08d761980feb
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 02:30:02.5039 (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: aDqlj4O7y8Yn2Q+8CrfU/7P9E9c+iplmZ06kn7fD0l0tqUI9YJSdUZnIPJ9rHLwHMPkk/2Ecd7sNI5NomTFTQ0gFJutRzGd4osrCNqXY7k4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR2201MB1709
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ekXeMJm1lC91iEUh8OVzSmRFW38>
Subject: [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 02:30:21 -0000

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