Re: [Rtg-yang-coord] Very active discussion and coordination of YANG models is needed
"Matt Hartley (mhartley)" <mhartley@cisco.com> Fri, 24 October 2014 02:04 UTC
Return-Path: <mhartley@cisco.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 6DA741AD8ED for <rtg-yang-coord@ietfa.amsl.com>; Thu, 23 Oct 2014 19:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 AuvzpT2BsuNq for <rtg-yang-coord@ietfa.amsl.com>; Thu, 23 Oct 2014 19:04:43 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E44F41AD845 for <Rtg-yang-coord@ietf.org>; Thu, 23 Oct 2014 19:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24690; q=dns/txt; s=iport; t=1414116283; x=1415325883; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iW397rSpj3Zl4/FveFt0trwqdztWhnDsFMMMrWtTCTI=; b=bVBP8q3BNu2qodY4ylLdJwoWrDkMGA/o8/bxxbTEmyn8xPW42ziGXwBw cnQQSQYX9Kbh3YvkS1TnWzrsssl3Dco3RoXGlcgH/IWaX4Z3p5AbPaEMX sWn4AnlOP2pByq1gKJUFe45BVja6xjk8txS3LTBN0BGXr4Fea/0dHsH2b E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApUFAHqySVStJA2E/2dsb2JhbABcgkhGVFyDAsoCh0sCG3MWAX2EAwEBBCMKQQsQAgEIDhQgAgICMCUCBAENDQyILQ21NZRuAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSPdhEBHy0EB4J3NoEeBZIFhEaIQ4NJkTKCNIFEgXs5gQMBAQE
X-IronPort-AV: E=Sophos;i="5.04,778,1406592000"; d="scan'208,217";a="366200521"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP; 24 Oct 2014 02:04:42 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s9O24fsB024120 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 02:04:41 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.227]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 21:04:41 -0500
From: "Matt Hartley (mhartley)" <mhartley@cisco.com>
To: Alia Atlas <akatlas@gmail.com>, "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: AQHP7w150sQXcmy0qUenAVfIbAJv3Jw+fqjw
Date: Fri, 24 Oct 2014 02:04:41 +0000
Message-ID: <9D50FCE7413E3D4EA5E42331115FB5BC14AE9DE4@xmb-rcd-x03.cisco.com>
References: <CAG4d1rfj90_O7Y2iuszVdqeHa_wgBuTEdgY5DRFBqKCJxcnzMg@mail.gmail.com>
In-Reply-To: <CAG4d1rfj90_O7Y2iuszVdqeHa_wgBuTEdgY5DRFBqKCJxcnzMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.251.185]
Content-Type: multipart/alternative; boundary="_000_9D50FCE7413E3D4EA5E42331115FB5BC14AE9DE4xmbrcdx03ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/Dgw87jFDBkTPO6uWEGyHO4rZD0o
Cc: "Benoit Claise (bclaise)" <bclaise@cisco.com>, "Matt Hartley (mhartley)" <mhartley@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 02:04:49 -0000
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
- [Rtg-yang-coord] Very active discussion and coord… Alia Atlas
- Re: [Rtg-yang-coord] Very active discussion and c… Robert Raszuk
- Re: [Rtg-yang-coord] Very active discussion and c… Alia Atlas
- Re: [Rtg-yang-coord] Very active discussion and c… Matt Hartley (mhartley)
- Re: [Rtg-yang-coord] Very active discussion and c… Alia Atlas
- Re: [Rtg-yang-coord] Very active discussion and c… BRUNGARD, DEBORAH A
- Re: [Rtg-yang-coord] Very active discussion and c… wangzitao
- Re: [Rtg-yang-coord] Very active discussion and c… Qin Wu