[ieee-ietf-coord] Fwd: IETF Sub-interface VLAN YANG Data Models - draft-ietf-netmod-sub-intf-vlan-model-04

Robert Wilton <rwilton@cisco.com> Mon, 05 November 2018 09:24 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E95341277BB; Mon, 5 Nov 2018 01:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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, 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
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MeFhpTtp4pah; Mon, 5 Nov 2018 01:24:51 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C717127133; Mon, 5 Nov 2018 01:24:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9741; q=dns/txt; s=iport; t=1541409890; x=1542619490; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=5kJ/22WRCUMN0Su24DpnGc9zZVoDHtG/eIEtVU98+20=; b=hOf63rT6iPhvEui5u3qr6btHo1N3wasyYnhZjnzsYosksMTJ3KLy+gIj TWMfv5Ukc1PR16/QV1ighiwUcYYzrzvh3gd2BKL25prYycONCv/MO1OK5 Ek65iXhRYTCFIZDMjdh7lVZM2VwUgWEw+2JxWGa40QeQQIMjIzoh33UM9 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ALAACFC+Bb/xjFo0hkGwEBAQEDAQEBB?= =?us-ascii?q?wMBAQGBUQYBAQELAYENgV1/KIN2iBhfjRgtkVmFVBSBZg0jhEkCg2s0DQ0BAwE?= =?us-ascii?q?BAgEBAm0cDIU6AQMDI2YcAwECKwICTQIIBgEMBgIBAYMdAYIBD6cqgS4fhBICA?= =?us-ascii?q?oEHhFUFilmBNIFBP4ERJ4IbIi6DGwEBA4EmBQESAT+CZIJXAo9pj0kJhm6KHQY?= =?us-ascii?q?YgVWFAIJ8hw+NCINrhlOBQzhkcTMaCBsVO4JsglCIS4VKMzCLZoI+AQE?=
X-IronPort-AV: E=Sophos; i="5.54,467,1534809600"; d="scan'208,217"; a="95785888"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([]) by bgl-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Nov 2018 09:24:44 +0000
Received: from [] (hkidc-vpn-client-233-89.cisco.com []) by bgl-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id wA59Of3S013612; Mon, 5 Nov 2018 09:24:43 GMT
References: <14a5c6fd-b24a-9669-7701-75dd822f95e2@cisco.com>
To: Glenn Parsons <glenn.parsons@ERICSSON.COM>, John Messenger <jmessenger@ADVAOPTICAL.COM>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
From: Robert Wilton <rwilton@cisco.com>
X-Forwarded-Message-Id: <14a5c6fd-b24a-9669-7701-75dd822f95e2@cisco.com>
Message-ID: <93f3c16b-1be8-814b-a04c-1ad1b1cbba06@cisco.com>
Date: Mon, 5 Nov 2018 16:24:41 +0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <14a5c6fd-b24a-9669-7701-75dd822f95e2@cisco.com>
Content-Type: multipart/alternative; boundary="------------9616AFB7F2D8C10924D153AA"
Content-Language: en-US
X-Outbound-SMTP-Client:, hkidc-vpn-client-233-89.cisco.com
X-Outbound-Node: bgl-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/WpK9yC9tYs5oPDTll5tddpyW1GA>
Subject: [ieee-ietf-coord] Fwd: IETF Sub-interface VLAN YANG Data Models - draft-ietf-netmod-sub-intf-vlan-model-04
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 09:24:54 -0000

FYI.  An informal review request email to 802.1 WG on the NETMOD 
sub-interface VLAN YANG model.


-------- Forwarded Message --------
Subject: 	IETF Sub-interface VLAN YANG Data Models - 
Date: 	Mon, 5 Nov 2018 16:16:00 +0700
From: 	Robert Wilton <rwilton@cisco.com>;

Dear esteemed 802.1 WG members,

A few years back, at the start of my IETF and IEEE standards journey I 
wrote a draft defining a sub-interface based VLAN termination YANG 
model.  After discussion and presentations in both IETF NETMOD WG and 
IEEE 802.1 WG, there was a general agreement that it would be acceptable 
for IETF to publish this YANG model as an informational RFC, with the 
acknowledgement that 802.1Q VLAN technology is owned by IEEE, and in 
future the IEEE 802.1 WG may choose to publish a VLAN termination model.

As part of that IETF NETMOD WG process, and after IEEE 802.1 WG had 
reviewed the model, I made a small change in structure of the YANG model 
with the sole aim of making the model simpler to use.  In particular, 
the older model required a slightly clunky indexed list of VLAN tags, 
and that is replaced with a simpler structure supporting two explicit 
named VLAN tags ('outer-tag' and 'second-tag').  A while back, Glenn 
requested that I pass these changes by the IEEE 802.1 WG to ensure that 
the changes are acceptable to the IEEE 802.1 WG, hence this email.

The change is perhaps best illustrated via the following change in the 
YANG tree output.

The*older format* of the YANG model (that members of the 802.1Q WG 
previously saw) was like this:

*if-cmn:encaps-type: +--:(vlan) +--rw vlan +--rw tags +--rw tag* [index] 
+--rw index uint8 +--rw dot1q-tag +--rw tag-type dot1q-tag-type +--rw 
vlan-id dot1q-vlan-id*

The *updated format *of YANG model in the current draft is like this:

           +--rw dot1q-vlan
              +--rw outer-tag!
              |  +--rw tag-type    dot1q-tag-type
              |  +--rw vlan-id     ieee:vlanid
              +--rw second-tag!
                 +--rw tag-type    dot1q-tag-type
                 +--rw vlan-id     ieee:vlanid

The same equivalent change has been made for L2 sub-interfaces as well.

The latest internet draft is 

In particular, it may also be useful to look at the instance data 
examples in chapter 7, that give a couple of examples of how the YANG 
model is expected to be used both for L3 termination, and also when used 
in conjunction with the IETF L2VPN YANG model to provision a 
point-to-point L2 service.

I hope to submit this draft to the NETMOD WG chairs for WG last call 
after the current IETF 103 meeting.  So if anyone has any concerns then 
please may I ask that you raise them.  ideally I would like to get them 
informally addressed before this document progresses.  Alternatively if 
you need more time to review this change, or need this as a formal 
liaison then please let me know, and I'll do my best.

Thank you for your time,
Rob Wilton