Re: [yang-doctors] Do we need a YANG doctor lunch meeting at the IETF meeting?
Benoit Claise <bclaise@cisco.com> Thu, 22 June 2017 09:53 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E774B127342 for <yang-doctors@ietfa.amsl.com>; Thu, 22 Jun 2017 02:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 CZ9skzvO1hyN for <yang-doctors@ietfa.amsl.com>; Thu, 22 Jun 2017 02:53:07 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0B6E1292C5 for <yang-doctors@ietf.org>; Thu, 22 Jun 2017 02:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14185; q=dns/txt; s=iport; t=1498125186; x=1499334786; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=4ukKH+Rfob2S3ty/hZNNeFDGu7Yv7DHFNQ53SbqMJ0U=; b=FDthnL/660IOqpl1ZfZNZIw5ZK6seLNwcndBx3q7KMtb8Y5yJcjNhQ6P 2FpjgOjAX6pHt7BqvFYqluEJRrpXMUAGK2HW18yef4EDT3bDkaRcwrUkc 3K4xgILSpFKehRbV8h8WOoCBmsr4p8Ff0DPGT4T1BWXV/Ju7uE/H/npPi E=;
X-IronPort-AV: E=Sophos;i="5.39,372,1493683200"; d="scan'208,217";a="653783386"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jun 2017 09:53:05 +0000
Received: from [10.55.221.38] (ams-bclaise-nitro5.cisco.com [10.55.221.38]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v5M9r436023839; Thu, 22 Jun 2017 09:53:04 GMT
To: Andy Bierman <andy@yumaworks.com>, Ladislav Lhotka <lhotka@nic.cz>
Cc: YANG Doctors <yang-doctors@ietf.org>, "Joe Clarke (jclarke)" <jclarke@cisco.com>
References: <90f1c2cb-8c53-f981-0430-94dc1fa21e56@cisco.com> <CABCOCHRCe7LwYL8_tuO0DUNfvqYSYjtzGqNZ5RF2_xbz2WCjKQ@mail.gmail.com> <m2mv91hddy.fsf@birdie.labs.office.nic.cz> <CABCOCHTQYQTFXp-TO9teaBfiMe2AF1fNtJ7JNoJLEodPV0FiEw@mail.gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <e4d12a2d-6ed6-3cf9-f99e-f4925cec5aac@cisco.com>
Date: Thu, 22 Jun 2017 11:53:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <CABCOCHTQYQTFXp-TO9teaBfiMe2AF1fNtJ7JNoJLEodPV0FiEw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D2EBAABAE8FF5C502FFA90B9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/lIkIQ25HooLXBS8SROTClYwATU0>
Subject: Re: [yang-doctors] Do we need a YANG doctor lunch meeting at the IETF meeting?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2017 09:53:18 -0000
Andy, > > > On Wed, Jun 21, 2017 at 2:57 AM, Ladislav Lhotka <lhotka@nic.cz > <mailto:lhotka@nic.cz>> wrote: > > Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>> writes: > > > Hi, > > > > I have a topic that is probably not workable but the issue is > very common. > > > > It would be nice if YANG library repositories were more > consistent and > > official. > > There is currently a ban against packaging YANG modules (e.g., > RPM or > > Debian) > > because of concerns the IETF Trust copyright will be violated > somehow. > > Maybe this could be changed somehow. > > > > The packages could correlate to the YANG catalog, e.g. an > > ietf-routing_1.0.deb package. > > I have been advocating YANG packages for a few years. IMO it is > hopelessly > > futile to > > attempt to manage a device as a random collection of individual > > modules. > > I would support this. I believe it is necessary to sort of > "emancipate" > YANG library, i.e. treat it as metadata that can exist on its own > rather > than plain state data provided by a server, or perhaps as a > module-level > data modelling language. > > Also, I believe it would be extremely helpful to step back and somehow > streamline and simplify all what we have, and in particular integrate > YANG library with datastores and the "use-schema" part of schema mount > into a coherent whole that is (relatively) easy to understand. Not > doing > so and just increasing complexity along several axes has IMO the > potential to kill the YANG business as such. > > > > I think the YANG catalog module attempts to provide off-box metadata. You will get a presentation of it during the OPS-AREA meeting. > The OpenEmbedded project is far superior to anything the IETF could do > on its own, but serves as an existence proof that building blocks can > be managed somehow (layers, feature-groups, packages for yocto). > > Networking equipment is still built with a monolithic mindset, so it > will be difficult for vendors to provide real modularity. The > first-level goal > is to let YANG designers and operators organize YANG APIs at a higher > level than individual YANG modules. > > I think the YANG catalog work is properly motivated and heading > in the right direction to define the packages. Yes. This is the notion of release bundle in draft-openconfig-netmod-model-catalog/ Note that they YANG module behind yangcatalog.org diverged from draft-openconfig-netmod-model-catalog, for good reasons. Joe and I are preparing an IETF draft to explain those. How many YANG doctors will we see in the hackathon ... Regards, Benoit > > > > I already made a concrete initial proposal in Chicago: > > https://www.ietf.org/mail-archive/web/netmod/current/msg18045.html > <https://www.ietf.org/mail-archive/web/netmod/current/msg18045.html> > > Lada > > > > Andy > > > > > > I have been working on Yocto/bitbake recently and the amount of > high-quality > > tools (see OpenEmbedded) is quite impressive. We could have > something like > > a bitbake recipe > > that describes the YANG requirements for some service or feature > package. > > Vendors could > > append the recipes to optimize for their platforms. Recipes > could point at > > open-source code > > or even vendor libraries that provides instrumentation for a > YANG package. > > We need distributed recipes, not a centralized catalog server, > although > > they could work together. > > > > > > > > > > Andy > > > > > > > > > > > > > > On Tue, Jun 20, 2017 at 9:26 AM, Benoit Claise > <bclaise@cisco.com <mailto:bclaise@cisco.com>> wrote: > > > >> Regards, Benoit > >> > >> _______________________________________________ > >> yang-doctors mailing list > >> yang-doctors@ietf.org <mailto:yang-doctors@ietf.org> > >> https://www.ietf.org/mailman/listinfo/yang-doctors > <https://www.ietf.org/mailman/listinfo/yang-doctors> > >> > > _______________________________________________ > > yang-doctors mailing list > > yang-doctors@ietf.org <mailto:yang-doctors@ietf.org> > > https://www.ietf.org/mailman/listinfo/yang-doctors > <https://www.ietf.org/mailman/listinfo/yang-doctors> > > -- > Ladislav Lhotka > Head, CZ.NIC Labs > PGP Key ID: 0xB8F92B08A9F76C67 > >
- [yang-doctors] Do we need a YANG doctor lunch mee… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Mahesh Jethanandani
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Juergen Schoenwaelder
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Juergen Schoenwaelder
- Re: [yang-doctors] Do we need a YANG doctor lunch… Andy Bierman
- Re: [yang-doctors] Do we need a YANG doctor lunch… Andy Bierman
- Re: [yang-doctors] Do we need a YANG doctor lunch… Ladislav Lhotka
- Re: [yang-doctors] Do we need a YANG doctor lunch… Kent Watsen
- Re: [yang-doctors] Do we need a YANG doctor lunch… Andy Bierman
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Ladislav Lhotka
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Kent Watsen
- Re: [yang-doctors] Do we need a YANG doctor lunch… Giles Heron (giheron)
- Re: [yang-doctors] Do we need a YANG doctor lunch… Radek Krejčí
- Re: [yang-doctors] Do we need a YANG doctor lunch… Ladislav Lhotka
- Re: [yang-doctors] Do we need a YANG doctor lunch… Mehmet Ersue
- Re: [yang-doctors] Do we need a YANG doctor lunch… Juergen Schoenwaelder
- Re: [yang-doctors] Do we need a YANG doctor lunch… Mahesh Jethanandani
- Re: [yang-doctors] Do we need a YANG doctor lunch… Andy Bierman
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Mehmet Ersue
- Re: [yang-doctors] Do we need a YANG doctor lunch… Mehmet Ersue
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise
- Re: [yang-doctors] Do we need a YANG doctor lunch… Andy Bierman
- Re: [yang-doctors] Do we need a YANG doctor lunch… Benoit Claise