[Rtg-yang-coord] Very active discussion and coordination of YANG models is needed

Alia Atlas <akatlas@gmail.com> Thu, 23 October 2014 22:05 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7471A1A1C05 for <rtg-yang-coord@ietfa.amsl.com>; Thu, 23 Oct 2014 15:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 GGqdz6Nt1L9K for <rtg-yang-coord@ietfa.amsl.com>; Thu, 23 Oct 2014 15:05:17 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49D821A1C03 for <Rtg-yang-coord@ietf.org>; Thu, 23 Oct 2014 15:05:17 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id b13so1442637qcw.37 for <Rtg-yang-coord@ietf.org>; Thu, 23 Oct 2014 15:05:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=fh17FF88Z6FT4Jp7lsXXF86mhsm4LYPfqw1TayrfnLw=; b=N0S1z79beQXrT9nQuMUW2vsf5fM0XQcrROd3h7+O3J6P/49xMZzzJV0QFQHt/8oT1V 74IaNtrps1qvqB/jK/uAii7R5sV0N0ypyku+tdgZYZ2OG1Al6ntJnP5PrmD0Alx5QVqE 4cGchFssfDejPJQZ8oCNd1O0U/JAn9ja4zxCiIjWA6dHl+NUeureVIQ/jLxLuQbepg+M 7ztgvTtLtGDc4i1fb6Yx79eo9PKFYLOtQ+hkj1zotGKifRatD3YqDOi7uMVIRxMMCqD5 GZNwcBZuvIQ9g1793jlc4lrR0nxJLQDQb9qB2LmXAupwrjK4Pe/J6/ba/K3qal5J5weo EF6Q==
MIME-Version: 1.0
X-Received: by 10.170.202.196 with SMTP id t187mr386463yke.36.1414101916493; Thu, 23 Oct 2014 15:05:16 -0700 (PDT)
Received: by 10.170.113.132 with HTTP; Thu, 23 Oct 2014 15:05:16 -0700 (PDT)
Date: Thu, 23 Oct 2014 18:05:16 -0400
Message-ID: <CAG4d1rfj90_O7Y2iuszVdqeHa_wgBuTEdgY5DRFBqKCJxcnzMg@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Rtg-yang-coord@ietf.org
Content-Type: multipart/alternative; boundary="001a1139d06a68afbe05061e42f2"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/nZKGWNijNdwPvmO8CRCPnkErMvQ
Cc: Benoit Claise <bclaise@cisco.com>
Subject: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 23 Oct 2014 22:05:23 -0000

First, I am absolutely delighted to discover that this coordination list
has 139 subscribers!  I am quite encouraged that we will be able to use
this mailing list for meaningful discussion and coordination.  Welcome and
please start talking!

Towards that purpose...

With a few WG drafts and over 20 individual drafts that may overlap and
should share some common abstractions and groupings, we really need to
start coordinating.   This is a significant explosion of drafts and
interest in the last 9 months - and we are interacting, at least in part,
with a community that NEEDS standardization to happen much more quickly.

Adrian, Benoit, and I are planning on writing up a job description for a
secretary to help with this mailing list and the coordination and
communication necessary.  Needless to say, if you would already like to
volunteer, please email me with details.

To aid in finding the various YANG models that relate to routing in some
way, I've included a list below.  This list was generated by looking
through a search of drafts based on the keyword YANG plus a couple I2RS
drafts I was already familiar with.  I apologize if I missed any (and
encourage consistent naming ).

draft-ietf-netmod-routing-cfg-15
<https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/>
draft-ietf-isis-yang-isis-cfg-00
<https://datatracker.ietf.org/doc/draft-ietf-isis-yang-isis-cfg/>
draft-ietf-i2rs-rib-info-model-03
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/> (YANG
model coming very soon)

draft-bogdanovic-netmod-acl-model-02
<https://datatracker.ietf.org/doc/draft-bogdanovic-netmod-acl-model/> (more
general than routing, so currently progressing in NETMOD)
draft-chen-mpls-ldp-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-chen-mpls-ldp-yang-cfg/>
draft-chen-mpls-te-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-chen-mpls-te-yang-cfg/>
draft-clemm-i2rs-yang-network-topo-01
<https://datatracker.ietf.org/doc/draft-clemm-i2rs-yang-network-topo/>
draft-contreras-supa-yang-network-topo-00
<https://datatracker.ietf.org/doc/draft-contreras-supa-yang-network-topo/>
(targeted
at an unapproved BoF, overlap with I2RS)
draft-dong-i2rs-l2-network-topology-00
<https://datatracker.ietf.org/doc/draft-dong-i2rs-l2-network-topology/>
draft-gandhi-mpls-te-yang-model-00
<https://datatracker.ietf.org/doc/draft-gandhi-mpls-te-yang-model/>
draft-hao-trill-yang-01
<https://datatracker.ietf.org/doc/draft-hao-trill-yang/> (may be
interesting to consider from the ISIS overlap)
draft-hares-i2rs-bgp-dm-00
<https://datatracker.ietf.org/doc/draft-hares-i2rs-bgp-dm/>
draft-liu-netmod-yang-abstract-topo-00
<https://datatracker.ietf.org/doc/draft-liu-netmod-yang-abstract-topo/>
(another
topology model)
draft-liu-pim-igmp-mld-yang-00
<https://datatracker.ietf.org/doc/draft-liu-pim-igmp-mld-yang/>
draft-liu-pim-yang-00 <https://datatracker.ietf.org/doc/draft-liu-pim-yang/>
draft-penno-sfc-yang-08
<https://datatracker.ietf.org/doc/draft-penno-sfc-yang/>
draft-pkd-pce-pcep-yang-00
<https://datatracker.ietf.org/doc/draft-pkd-pce-pcep-yang/>
draft-tissa-nvo3-yang-oam-00
<https://datatracker.ietf.org/doc/draft-tissa-nvo3-yang-oam/>
draft-wang-i2rs-isis-dm-00
<https://datatracker.ietf.org/doc/draft-wang-i2rs-isis-dm/>
draft-wang-i2rs-ospf-dm-00
<https://datatracker.ietf.org/doc/draft-wang-i2rs-ospf-dm/>
draft-yang-trill-parent-seletion-03
<https://datatracker.ietf.org/doc/draft-yang-trill-parent-seletion/>
draft-yeung-netmod-ospf-02
<https://datatracker.ietf.org/doc/draft-yeung-netmod-ospf/>
draft-zhang-mpls-tp-yang-oam-00
<https://datatracker.ietf.org/doc/draft-zhang-mpls-tp-yang-oam/>
draft-zhang-nvo3-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-zhang-nvo3-yang-cfg/>
draft-zhdankin-netmod-bgp-cfg-01
<https://datatracker.ietf.org/doc/draft-zhdankin-netmod-bgp-cfg/>
draft-zhuang-l2vpn-evpn-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-zhuang-l2vpn-evpn-yang-cfg/>
draft-zhuang-l2vpn-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-zhuang-l2vpn-yang-cfg/>
draft-zhuang-l3vpn-yang-cfg-00
<https://datatracker.ietf.org/doc/draft-zhuang-l3vpn-yang-cfg/>

I hope that reading some of the above (at least
draft-ietf-netmod-routing-cfg-15
<https://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/>) will
start to inspire ideas and concrete discussion about what coordination
between models and drafts is needed.

Thanks,
Alia