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

wangzitao <wangzitao@huawei.com> Mon, 27 October 2014 10:19 UTC

Return-Path: <wangzitao@huawei.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 574241A8BB6 for <rtg-yang-coord@ietfa.amsl.com>; Mon, 27 Oct 2014 03:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UeZf6Cz6gj42 for <rtg-yang-coord@ietfa.amsl.com>; Mon, 27 Oct 2014 03:19:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCE8E1A8AEB for <Rtg-yang-coord@ietf.org>; Mon, 27 Oct 2014 03:19:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOB89608; Mon, 27 Oct 2014 10:19:13 +0000 (GMT)
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Oct 2014 10:19:12 +0000
Received: from SZXEML501-MBX.china.huawei.com ([169.254.1.231]) by szxeml407-hub.china.huawei.com ([10.82.67.94]) with mapi id 14.03.0158.001; Mon, 27 Oct 2014 18:19:09 +0800
From: wangzitao <wangzitao@huawei.com>
To: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>
Thread-Topic: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed
Thread-Index: AQHP7w13vd0nkBrwhkWKpwwuyK9dD5xDvg+QgAAANpA=
Date: Mon, 27 Oct 2014 10:19:08 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EABA0E68@szxeml501-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.131]
Content-Type: multipart/mixed; boundary="_004_E6BC9BBCBCACC246846FC685F9FF41EABA0E68szxeml501mbxchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/5ZMAmb-hnI8jqe4FaXBGnUOXanA
Cc: "akatlas@gmail.com" <akatlas@gmail.com>
Subject: Re: [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: Mon, 27 Oct 2014 10:19:18 -0000

FYI.

Here is a new draft to discuss BFD YANG model.

https://datatracker.ietf.org/doc/draft-wang-yang-bfd-oam/

-Michael
发件人: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] 代表 Alia Atlas
发送时间: 2014年10月24日 6:05
收件人: Rtg-yang-coord@ietf.org<mailto:Rtg-yang-coord@ietf.org>
抄送: Benoit Claise
主题: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed

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