Re: [netmod] IETF91 NETMOD agenda ?

Andy Bierman <andy@yumaworks.com> Wed, 05 November 2014 00:11 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E711A702B for <netmod@ietfa.amsl.com>; Tue, 4 Nov 2014 16:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, 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 ieQl_wQ7M-VP for <netmod@ietfa.amsl.com>; Tue, 4 Nov 2014 16:11:17 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D73B1A6FF6 for <netmod@ietf.org>; Tue, 4 Nov 2014 16:11:15 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id f12so10851615qad.10 for <netmod@ietf.org>; Tue, 04 Nov 2014 16:11:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6fkRlt+deAlAMgTMj1szkukGP5Y4YFSIdwxQ0T6X3qM=; b=kBbD2wHctIMAUsaaP0X3FJ2AJ2+JsfQHQ2IGSqNjzUHn5IiiGJBPrKFSCJZCbqbroX MAuEck+0uwLYhJdZm2tKm57sS5ThkhcKTpOEPfyr38FUUki4wz0/PmLO+r9D81s2afMe GAalQ4Tw3JbGx0SBRAGf6permehsHkQVAHLcVF6TbrSSLgalj8QB/p1yoCRTzkmbiRtk yEhPbJUvJ3ncPcz5eNiOGcrWnleVvNwkDlHulNEfU47qSdMSyIzHHcJTcrbHTcSmUNi8 zbwRD1i3tlPY7BEjMwIy/z06W5F7D6m5yTATVHhllcOjsfL7AsLVLsBqsYjnO8Cyj2v4 J17w==
X-Gm-Message-State: ALoCoQkT9cRE35poZt2HZ7WJGLI4a6r4QTh0Es3JsPMbkBqU0hs20b4WSooEYof9E8s2j5YQJwP2
MIME-Version: 1.0
X-Received: by 10.140.34.21 with SMTP id k21mr13491652qgk.21.1415146274411; Tue, 04 Nov 2014 16:11:14 -0800 (PST)
Received: by 10.140.37.52 with HTTP; Tue, 4 Nov 2014 16:11:14 -0800 (PST)
In-Reply-To: <545965FA.2050308@cisco.com>
References: <A125E53CE190A749957C19483DC79F9F5C977E5A@US70TWXCHMBA11.zam.alcatel-lucent.com> <D8D374DB-32C6-4725-AD1B-D4E1B23BC966@lucidvision.com> <CABCOCHSoDxZfzA0dnviB2yV8GbdqmUrGmJXsFxMy8_7MpG7W+w@mail.gmail.com> <79054E89-2D09-4461-8D35-8F6FA025B71F@nic.cz> <43060BE7-53EA-4B9D-B778-2FED58C0D60C@lucidvision.com> <52AE09CB-D4AB-4421-BBA4-1D9C45EA6957@gmail.com> <54590195.3010903@cisco.com> <CAAchPMtcvd3xb9xCGEBHqTZg8G-Fg76z8T2Wi1QLHoS=W_fiag@mail.gmail.com> <54595361.5000907@cisco.com> <CABCOCHSqWWPDyTWXMj3+DUJ89GGCiHD6mhK3W7bJf-+VgS_cRA@mail.gmail.com> <545965FA.2050308@cisco.com>
Date: Tue, 04 Nov 2014 16:11:14 -0800
Message-ID: <CABCOCHTCtrsLYTDtWSDAyPScD-dxLC0GDuzYDtgidHok_cT7-g@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/netmod/AV5z8CKZDGzLO9eobeLPCjY4818
Cc: "netmod@ietf.org" <netmod@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: Re: [netmod] IETF91 NETMOD agenda ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 00:11:23 -0000

On Tue, Nov 4, 2014 at 3:49 PM, Benoit Claise <bclaise@cisco.com> wrote:
> On 05/11/2014 00:20, Andy Bierman wrote:
>
> On Tue, Nov 4, 2014 at 2:29 PM, Benoit Claise <bclaise@cisco.com> wrote:
>
> Mahesh,
>
> Benoit,
>
> I was going to give a quick update on the BFD YANG model, which is being
> presented/discussed in its own WG.
>
> I wonder which ideal outcome you want a presentation in the NETMOD WG?
>
> Here's the list of drafts that have normative or unclassified references to
> YANG:
>
> draft-vanderstok-core-comi-05                     2014-10-27  Active
> draft-shi-alto-yang-json-00                       2014-10-27  Active
> draft-shi-alto-yang-model-00                      2014-10-27  Active
> draft-netmod-clemm-datastore-push-00              2014-10-27  Active
> draft-wildes-netmod-syslog-model-05               2014-10-27  Active
> draft-zhang-nvo3-yang-active-active-cfg-00        2014-10-27  Active
> draft-zaalouk-supa-configuration-model-01         2014-10-27  Active
> draft-wang-lime-rpc-yang-oam-management-00        2014-10-27  Active
> draft-vergara-flexigrid-yang-00                   2014-10-27  Active
> draft-gandhi-mpls-te-yang-model-01                2014-10-27  Active
> draft-txh-opsawg-lime-gap-analysis-01             2014-10-27  Active
> draft-zheng-netmod-xmi-yang-translation-00        2014-10-27  Active
> draft-chen-i2rs-mpls-ldp-info-model-00            2014-10-27  Active
> draft-tripathy-cloud-sla-yang-model-00            2014-10-27  Active
> draft-clemm-i2rs-yang-l3-topo-00                  2014-10-27  Active
> draft-contreras-supa-yang-network-topo-01         2014-10-27  Active
> draft-wang-yang-bfd-oam-00                        2014-10-27  Active
> draft-ietf-netconf-server-model-04                2014-10-26  Active
> draft-ietf-isis-yang-isis-cfg-01                  2014-10-26  Active
> draft-shen-l2tpext-l2tpv3-yang-model-00           2014-10-26  Active
> draft-ietf-netmod-routing-cfg-16                  2014-10-26  Active
> draft-shaikh-idr-bgp-model-00                     2014-10-26  Active
> draft-ietf-netconf-restconf-03                    2014-10-25  Active
> draft-pkd-pce-pcep-yang-01                        2014-10-25  Active
> draft-sarikaya-dmm-for-wifi-01                    2014-10-24  Active
> draft-voit-netmod-peer-mount-requirements-01      2014-10-24  Active
> draft-shi-model-json-msg-yang-00                  2014-10-24  Active
> draft-liu-pim-igmp-mld-yang-00                    2014-10-23  Active
> draft-ietf-netmod-rfc6087bis-01                   2014-10-23  Active
> draft-liu-pim-yang-00                             2014-10-23  Active
> draft-asechoud-netmod-diffserv-model-00           2014-10-22  Active
> draft-dong-i2rs-l2-network-topology-00            2014-10-21  Active
> draft-bierman-netconf-efficiency-extensions-02    2014-10-21  Active
> draft-zhang-nvo3-yang-cfg-00                      2014-10-21  Active
> draft-sun-softwire-yang-00                        2014-10-20  Active
> draft-yeung-netmod-ospf-02                        2014-10-14  Active
> draft-ietf-netmod-yang-json-01                    2014-10-13  Active
> draft-clemm-i2rs-yang-network-topo-01             2014-10-10  Active
> draft-ietf-netconf-call-home-01                   2014-10-10  Active
> draft-bogdanovic-netmod-acl-model-02              2014-10-08  Active
> draft-clemm-netmod-mount-02                       2014-10-07  Active
> draft-zhdankin-netmod-bgp-cfg-01                  2014-10-02  Active
> draft-wang-i2rs-ospf-dm-00                        2014-09-26  Active
> draft-bhuvan-bmwg-of-controller-benchmarking-01   2014-09-25  Active
> draft-zhang-mpls-tp-yang-oam-00                   2014-09-25  Active
> draft-bierman-netmod-yang-conformance-04          2014-09-24  Active
> draft-ietf-netmod-snmp-cfg-08                     2014-09-18  In IESG
> processing - ID Tracker state <RFC Ed Queue>
> draft-frank-netconf-conformance-00                2014-09-16  Active
> draft-haas-i2rs-netmod-netconf-requirements-00    2014-09-12  Active
> draft-lhotka-netmod-yang-metadata-00              2014-09-11  Active
> draft-schoenw-lmap-yang-01                        2014-09-02  Active
> draft-zhuang-l2vpn-yang-cfg-00                    2014-08-24  Active
> draft-zhuang-l2vpn-evpn-yang-cfg-00               2014-08-16  Active
> draft-chen-mpls-ldp-yang-cfg-00                   2014-08-15  Active
> draft-chen-mpls-te-yang-cfg-00                    2014-08-15  Active
> draft-zhuang-l3vpn-yang-cfg-00                    2014-08-15  Active
> draft-scharf-alto-yang-00                         2014-07-04  Active
> draft-yang-netmod-location-00                     2014-07-04  Active
> draft-fang-l3vpn-virtual-pe-05                    2014-07-04  Active
> draft-mekking-dnsop-kasp-00                       2014-07-04  Active
> draft-xjz-opsawg-nfvmodel-00                      2014-07-04  Active
> draft-liu-netmod-yang-abstract-topo-00            2014-07-03  Active
> draft-ietf-netconf-yang-patch-01                  2014-07-03  Active
> draft-zheng-netmod-integrate-operations-00        2014-07-02  Active
> draft-liu-netconf-multi-instances-00              2014-07-02  Active
> draft-litkowski-isis-yang-isis-cfg-01             2014-06-27  Active
> draft-litkowski-netmod-isis-cfg-00                2014-06-17  Active
> draft-lonvick-private-tax-08                      2014-06-09  Active
> draft-tp-i2rs-yang-00                             2014-05-08  Active
>
> That could be a lot of updates...
> I believe we should focus on the YANG models that don't have an existing WG.
>
> I would prefer to spend all the meeting time
> trying to discuss open issues in chartered items.  I don't see why
> the NETMOD WG needs to spend time on status reports for
> any unchartered work.
>
> I don't agree that NETMOD WG should be the home of SYSLOG
> or any other protocol specific data models. IMO all those type of drafts
> should try to find a home in a protocol WG with the right experts.
>
> Sure, NIMY (Not In My Yard) is the easy answer.
> And where should we have syslog?
> https://datatracker.ietf.org/wg/syslog/charter/ is concluded
>

It is not NIMBY. The YANG experts are not all SYSLOG experts.
Getting the right people in the room is important (you said that ;-)
Making a few SYSLOG experts sit through 140 minutes of
unrelated material may not be the best option for them either.

It is unfortunate that the SYSLOG WG has decided the protocol
is complete and no further work is needed.  I don't agree IETF
process should be a good reason to choose NETMOD WG.
This draft is already chartered and I am not trying to stop
the SYSLOG work.  I don't want it to start a trend though.


> Regards, Benoit
>
>


Andy

>
> Andy
>
>
>
> Reminder: A good avenue for any YANG models is
> http://www.ietf.org/meeting/91/tutorials/yang-session.html
>
> Regards, Benoit
>
>
>
>
> On Tue Nov 04 2014 at 8:40:55 AM Benoit Claise <bclaise@cisco.com> wrote:
>
> Mahesh,
>
> Not sure what exactly you want to present but let me draw your attention
> that the routing-related modules should be taken care of in their respective
> WG. See
> http://www.ietf.org/mail-archive/web/rtg-yang-coord/current/msg00094.html
>
> Regards, Benoit
>
> Tom,
>
> I am giving an update on the BFD YANG model in the BFD WG. I can give a
> quick update (~1-2min) in NETMOD if such an update is desired.
>
> Mahesh Jethanandani
> mjethanandani@gmail.com
>
> On Oct 23, 2014, at 1:43 PM, "Thomas D. Nadeau" <tnadeau@lucidvision.com>
> wrote:
>
>
>    We have plenty of runway in the agenda right now so I will put it down
> as two items. We reserved two slots because I feel its important to
> encourage discussion during the face2face meetings so insofar as I can, I
> want to give you enough runway to discuss this in detail.
>
>    --Tom
>
>
> On Oct 23, 2014:12:13 PM, at 12:13 PM, Ladislav Lhotka <lhotka@nic.cz>
> wrote:
>
>
> Hi,
>
>
> apart from the two WG items draft-ietf-netmod-routing-cfg-16 (to be
> submitted) and draft-ietf-netmod-yang-json-01, I’d like to discuss the draft
> and draft-lhotka-netmod-yang-metadata-00. I think 5 minutes would be enough
> for the latter, I could even do it together with yang-json.
>
>
> Thanks, Lada
>
>
> On 23 Oct 2014, at 18:02, Andy Bierman <andy@yumaworks.com> wrote:
>
>
>
>
> On Tue, Oct 21, 2014 at 2:34 PM, Thomas D. Nadeau
> <tnadeau@lucidvision.com> wrote:
>
>
>    Not yet. Please propose topics.
>
>
>
> I would like 15 min. to discuss YANG conformance issues, specified in this
> draft:
>
> http://www.ietf.org/id/draft-bierman-netmod-yang-conformance-04.txt
>
>
> These issues may get resolved in the NETCONF YANG 1.1 virtual interim
>
> meeting next week. If not, this topic should be discussed at the IETF
> meeting.
>
>
>
>    —Tom
>
>
> Andy
>
>
>
>
> On Oct 21, 2014:5:32 PM, at 5:32 PM, Sterne, Jason (Jason)
> <jason.sterne@alcatel-lucent.com> wrote:
>
>
> Hi all,
>
>
> Is there a preliminary agenda for the two NETMOD sessions at IETF91 ?
>
>
> Some thought about topics being split between the 1st (longer) and 2nd
> (shorter) sessions ?
>
>
> Thanks,
>
> Jason
>
>
> _______________________________________________
>
> netmod mailing list
>
> netmod@ietf.org
>
> https://www.ietf.org/mailman/listinfo/netmod
>
>
>
> _______________________________________________
>
> netmod mailing list
>
> netmod@ietf.org
>
> https://www.ietf.org/mailman/listinfo/netmod
>
>
>
> _______________________________________________
>
> netmod mailing list
>
> netmod@ietf.org
>
> https://www.ietf.org/mailman/listinfo/netmod
>
>
> --
>
> Ladislav Lhotka, CZ.NIC Labs
>
> PGP Key ID: E74E8C0C
>
>
>
>
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
> .
>
>