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

"BRUNGARD, DEBORAH A" <db3546@att.com> Fri, 24 October 2014 14:34 UTC

Return-Path: <db3546@att.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 52BDA1A0070 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 24 Oct 2014 07:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 5D3CcCftUoL1 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 24 Oct 2014 07:34:32 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10ED81A0084 for <rtg-yang-coord@ietf.org>; Fri, 24 Oct 2014 07:34:32 -0700 (PDT)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.2-0) with ESMTP id 8736a445.2b0e9ea30940.945840.00-2478.2662441.nbfkord-smmo07.seg.att.com (envelope-from <db3546@att.com>); Fri, 24 Oct 2014 14:34:32 +0000 (UTC)
X-MXL-Hash: 544a637819f5f8e8-647a71bcc287fffcaf2562c41e413a3d3d0b5446
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.2-0) over TLS secured channel with ESMTP id e636a445.0.945727.00-2270.2662126.nbfkord-smmo07.seg.att.com (envelope-from <db3546@att.com>); Fri, 24 Oct 2014 14:34:22 +0000 (UTC)
X-MXL-Hash: 544a636e601603f3-c32ea2ede62e9f789dc7830b3c53b3ec87fc281d
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s9OEYLAb011004; Fri, 24 Oct 2014 10:34:21 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s9OEYF7G010930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 24 Oct 2014 10:34:18 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Fri, 24 Oct 2014 14:33:59 GMT
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.237]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 10:33:58 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: Alia Atlas <akatlas@gmail.com>, "Matt Hartley (mhartley)" <mhartley@cisco.com>
Thread-Topic: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed
Thread-Index: AQHP7zSFPTXoTJZzSEagn3nvG9jyxZw/UFjw
Date: Fri, 24 Oct 2014 14:33:58 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C8166D4A71@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <CAG4d1rfj90_O7Y2iuszVdqeHa_wgBuTEdgY5DRFBqKCJxcnzMg@mail.gmail.com> <9D50FCE7413E3D4EA5E42331115FB5BC14AE9DE4@xmb-rcd-x03.cisco.com> <CAG4d1rek-aYrNvuJc2q=tKVk-nRndV_8McYuOOuBWni5EfXBgg@mail.gmail.com>
In-Reply-To: <CAG4d1rek-aYrNvuJc2q=tKVk-nRndV_8McYuOOuBWni5EfXBgg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.16.234.240]
Content-Type: multipart/alternative; boundary="_000_F64C10EAA68C8044B33656FA214632C8166D4A71MISOUT7MSGUSRDE_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=be/cppzB c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=3T6DJ_suu6wA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqp]
X-AnalysisOut: [o32RAAAA:8 a=48vgC7mUAAAA:8 a=AUd_NHdVAAAA:8 a=2tgTY_QcJpf]
X-AnalysisOut: [UlIW0GP0A:9 a=QEXdDO2ut3YA:10 a=Q-S3ZxpXFpjEAviB:21 a=_FI7]
X-AnalysisOut: [An3DvAnLPbUE:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=aLe8J9]
X-AnalysisOut: [aEQQ9dHCYAGWkA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZ]
X-AnalysisOut: [eC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=iPL4quwxriOfyfSA:21 a=Zq3]
X-AnalysisOut: [cZ1C6JCil0Jki:21 a=-gzsJ7ezRXVs5mCJ:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <db3546@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/itCggNevaouBuls_kf0aaxI-xfU
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "Benoit Claise (bclaise)" <bclaise@cisco.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: Fri, 24 Oct 2014 14:34:35 -0000

Thanks Matt-
Yes, this should fall under ccamp-

Deborah
(Co-chair CCAMP)


From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Thursday, October 23, 2014 10:45 PM
To: Matt Hartley (mhartley)
Cc: Rtg-yang-coord@ietf.org; Benoit Claise (bclaise)
Subject: Re: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed

Hi Matt,

Thanks.  I guess that might fall under CCAMP.   Not closely following CCAMP, I wasn't sure if it was well connected.

Alia

On Thu, Oct 23, 2014 at 10:04 PM, Matt Hartley (mhartley) <mhartley@cisco.com<mailto:mhartley@cisco.com>> wrote:
Alia,

draft-dharini-netmod-g-698-2-yang-00 should probably go on the list.

Cheers

Matt


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