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

Lou Berger <lberger@labn.net> Mon, 28 November 2016 13:25 UTC

Return-Path: <lberger@labn.net>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 923FD129F11 for <teas@ietfa.amsl.com>; Mon, 28 Nov 2016 05:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMODJSUNrkki for <teas@ietfa.amsl.com>; Mon, 28 Nov 2016 05:25:04 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 3CC56129F06 for <teas@ietf.org>; Mon, 28 Nov 2016 05:25:04 -0800 (PST)
Received: (qmail 6476 invoked by uid 0); 28 Nov 2016 13:25:04 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy6.mail.unifiedlayer.com with SMTP; 28 Nov 2016 13:25:04 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with id DRQy1u00v2SSUrH01RR1ak; Mon, 28 Nov 2016 06:25:02 -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=wU2YTnxGAAAA:8 a=48vgC7mUAAAA:8 a=z5nbsJZ9MsWi_9_UTQQA:9 a=7QmClhpfjcUDqHVD:21 a=LZffTU3c9aEftv2D:21 a=pILNOxqGKmIA:10 a=Yz9wTY_ffGCQnEDHKrcv:22 a=w1C3t2QeGrPiZgrLijVG:22
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:From:To:References:Subject; bh=SC1CkmpMN+QswidimJpMQRq2DSXNGaC4s8yYFYjQBx4=; b=0QpyB3pg2mRwWTRZEHtzLvzysW meGrgnJSna3CenAWc4t3aYvSTnNz0WMKufQyS1rL6mdEsVA+uS115YEEXIkTn8dmtvY0h84PS6269 w5Eo9ZYfYQvTawGaAjgQQDGdE;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:35969 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 1cBLvY-0005c3-4y for teas@ietf.org; Mon, 28 Nov 2016 06:25:00 -0700
References: <7a7c1896-b203-196d-6a6e-fb8afd3c3846@labn.net>
To: TEAS WG <teas@ietf.org>
From: Lou Berger <lberger@labn.net>
X-Forwarded-Message-Id: <7a7c1896-b203-196d-6a6e-fb8afd3c3846@labn.net>
Message-ID: <fa66f270-0cc9-4641-a534-eb27f4240fbc@labn.net>
Date: Mon, 28 Nov 2016 08:24:57 -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: <7a7c1896-b203-196d-6a6e-fb8afd3c3846@labn.net>
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-Source-IP: 100.15.85.191
X-Exim-ID: 1cBLvY-0005c3-4y
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) [100.15.85.191]:35969
X-Source-Auth: lberger@labn.net
X-Email-Count: 1
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FSBvJ-qTOSRZ21cQ9Cw5PoT9Pq4>
Subject: [Teas] Fwd: [Rtg-yang-coord] Aligning models across the Routing Area
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Nov 2016 13:25:06 -0000

YANG draft authors please take note and discuss proposed changes with
the WG.

Lou

-------- Forwarded Message --------
Subject: 	[Rtg-yang-coord] Aligning models across the Routing Area
Date: 	Wed, 23 Nov 2016 10:49:38 -0500
From: 	Lou Berger <lberger@labn.net>
To: 	Routing Chairs <rtg-chairs@ietf.org>, Routing YANG Coordination
<rtg-yang-coord@ietf.org>
CC: 	Routing Area YANG Architecture DT <rtg-dt-yang-arch@ietf.org>



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
   draft-rtgyangdt-rtgwg-routing-types)

   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



_______________________________________________
Rtg-yang-coord mailing list
Rtg-yang-coord@ietf.org
https://www.ietf.org/mailman/listinfo/rtg-yang-coord