[Rtg-yang-coord] Aligning models across the Routing Area

Lou Berger <lberger@labn.net> Wed, 23 November 2016 15:49 UTC

Return-Path: <lberger@labn.net>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 19782129E2D for <rtg-yang-coord@ietfa.amsl.com>; Wed, 23 Nov 2016 07:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Status: No, score=-1.502 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id N97TdRO1Yt_8 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 23 Nov 2016 07:49:58 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com []) by ietfa.amsl.com (Postfix) with SMTP id 1DDDB129E34 for <rtg-yang-coord@ietf.org>; Wed, 23 Nov 2016 07:49:47 -0800 (PST)
Received: (qmail 6349 invoked by uid 0); 23 Nov 2016 15:49:43 -0000
Received: from unknown (HELO cmgw2) ( by gproxy6.mail.unifiedlayer.com with SMTP; 23 Nov 2016 15:49:43 -0000
Received: from box313.bluehost.com ([]) by cmgw2 with id BTpe1u00D2SSUrH01TphPF; Wed, 23 Nov 2016 08:49:42 -0700
X-Authority-Analysis: v=2.1 cv=YNIMl32x c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=L24OOQBejmoA:10 a=fWAjMxmLJTaWZCp2O-oA:9 a=TRnNIdgzN1TUaKuG:21 a=7sUkHCwyhxIOoIaZ:21 a=pILNOxqGKmIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:To:Cc:References:Subject:From; bh=ZbbQk9R2RdwwNnbOTXu+gfxJ2EyRhBL6B9VLYP2MPlE=; b=sHX0FPzB67jBPRxisMU5Y6xrko /aRBupegcxzMI66eakgNPpaJ90zR1Pu5Lsnv86PgmNSdq2NBblGoUNursjMFdrcSyQJSTmm4y1uRO c5KJXOMVQt3nAgjoaxQYe2+nd;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([]:55734 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from <lberger@labn.net>) id 1c9Znn-0001rs-U5; Wed, 23 Nov 2016 08:49:40 -0700
From: Lou Berger <lberger@labn.net>
References: <D45519FC.8A29A%acee@cisco.com> <x9aglvjyvns0jeeav2ruoxdm.1479525815799@email.android.com> <D4562787.8A2F5%acee@cisco.com> <BN3PR05MB2707B16E37B20354CC116F40B5B20@BN3PR05MB2707.namprd05.prod.outlook.com> <D4573FBB.8A343%acee@cisco.com> <BN3PR05MB270743E4645994907D8F203EB5B20@BN3PR05MB2707.namprd05.prod.outlook.com> <D457461C.8A35E%acee@cisco.com> <BN3PR05MB2707D273631D092EED629535B5B20@BN3PR05MB2707.namprd05.prod.outlook.com> <1588331fc68.2818.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <dnbuckhwhxbrjmxkteucj5bj.1479675848244@email.android.com>
To: Routing Chairs <rtg-chairs@ietf.org>, Routing YANG Coordination <rtg-yang-coord@ietf.org>
Message-ID: <7a7c1896-b203-196d-6a6e-fb8afd3c3846@labn.net>
Date: Wed, 23 Nov 2016 10:49:38 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <dnbuckhwhxbrjmxkteucj5bj.1479675848244@email.android.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Exim-ID: 1c9Znn-0001rs-U5
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) []:55734
X-Source-Auth: lberger@labn.net
X-Email-Count: 6
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-yang-coord/m0W32jaG9yyFHmA1TApEFLnZxzA>
Cc: Routing Area YANG Architecture DT <rtg-dt-yang-arch@ietf.org>
Subject: [Rtg-yang-coord] Aligning models across the Routing Area
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2016 15:49:59 -0000

Hi, (RTG Chairs and YANG aficionados),

    YANG continues to be a hot topic in many (of your) RTG area
groups.  Some of us in the DT thought it would be worth pointing out
some more recent publications/WG activities that may impact work in
area WGs -- and importantly, that aligning RTG Area WG's models with
these activities will help us all produce a more cohesive and
complementary body of work.

The key recent items are:

1) RFC 8022 has been published
   (A YANG Data Model for Routing Management)

   This really contains basic building blocks for our area

2) RFC6087bis has been submitted for publication
   (Guidelines for Authors and Reviewers of YANG Data Model Documents)

   Notably, Section  5.23 provides some guidance on how to handle
   OpState now, while waiting for the revised data store solution.

3) YANG Schema Mount, draft-ietf-netmod-schema-mount, is moving along
   in NetMod

   This is a key building block for VRFs/VSIs and Logical
   routers/switches/systems, and may provide value elsewhere too.

4) Logical Network Elements and Network Instance drafts are progressing
   in RTGWG (draft-ietf-rtgwg-lne-model, draft-ietf-rtgwg-ni-model)

   These are the models supporting VRFs/VSIs (NIs) and Logical
   routers/switches/systems (LNEs) *without* requiring explicit
   support in every model.

5) Finally, based on the past meeting, we should shortly have a base set
   of  "Routing Area Common YANG Data Types" defined in RTGWG (based on

   This defines several types that are commonly used in the rtg area,
   and use of such should help with consistency across models.

We are suggesting that aligning RTG WG's models to the above makes
sense at this time, and that each WG/set of authors review and update
their models as they see appropriate.  Of course, feedback on the
drafts mentioned above should be provided to their respective WGs.

Lou for the RTG Area YANG DT