Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations

Lou Berger <lberger@labn.net> Mon, 11 November 2019 16:33 UTC

Return-Path: <lberger@labn.net>
X-Original-To: netmod-ver-dt@ietfa.amsl.com
Delivered-To: netmod-ver-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75108120909 for <netmod-ver-dt@ietfa.amsl.com>; Mon, 11 Nov 2019 08:33:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 gb2ifUBHrLJL for <netmod-ver-dt@ietfa.amsl.com>; Mon, 11 Nov 2019 08:33:15 -0800 (PST)
Received: from gproxy5-pub.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C23F120958 for <netmod-ver-dt@ietf.org>; Mon, 11 Nov 2019 08:33:15 -0800 (PST)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy5.mail.unifiedlayer.com (Postfix) with ESMTP id 9FC91140620 for <netmod-ver-dt@ietf.org>; Mon, 11 Nov 2019 09:33:14 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id UCcsiJizzlpxgUCcsiqcvG; Mon, 11 Nov 2019 09:33:14 -0700
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=DP+hHRFb c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=xqWC_Br6kY4A:10:nop_ipv6 a=IkcTkHD0fZMA:10:nop_charset_1 a=MeAgGD-zjQ4A:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=wU2YTnxGAAAA:8 a=AUd_NHdVAAAA:8 a=48vgC7mUAAAA:8 a=dtCEmiGbqKpSq9AEsgcA:9 a=7Zwj6sZBwVKJAoWSPKxL6X1jA+E=:19 a=QEXdDO2ut3YA:10:nop_charset_2 a=-RoEEKskQ1sA:10:nop_election2020_name_body a=Yz9wTY_ffGCQnEDHKrcv:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=4a66B3zo2bJlOxBx8EZdEPUEy6aPuGg469sAL1siNCI=; b=pZExWFNbpTJddUzF436BYCfnOA F88ifZ9N/B1iKurcLAWna3hK+A8nXpx7AKqGbVIx0VJAg99Lcm7gYJzgm2bvV1m7GPp5Qbj5x27f3 dRHzwjumMh0NPjU+5zSXpdw/N;
Received: from [127.0.0.1] (port=34505 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <lberger@labn.net>) id 1iUCcs-004DWg-8X; Mon, 11 Nov 2019 09:33:14 -0700
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, NetMod WG Chairs <netmod-chairs@ietf.org>
Cc: "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
References: <0100016df4023541-879644c6-353f-4b32-9ccd-96dcd3d5e113-000000@email.amazonses.com> <0100016df49997cc-581feda8-01ed-4980-b8bb-2ffd5d648df9-000000@email.amazonses.com> <619859ba-f5b7-b08d-d928-0d70ad3cffaf@labn.net> <MN2PR11MB4366A6DF5DF4C29F1D97BECAB57F0@MN2PR11MB4366.namprd11.prod.outlook.com> <0a2825d0-a871-f0c3-aca9-4b9c61ee2f07@labn.net> <MN2PR11MB43662722E0F1B65442BAD5E3B57E0@MN2PR11MB4366.namprd11.prod.outlook.com> <bc3b6674-ebaf-e056-1dbe-08a52fb8cc58@labn.net> <MN2PR11MB436655746DE65AF6B9DFDF23B57E0@MN2PR11MB4366.namprd11.prod.outlook.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9d0a54b7-a6fb-2bbe-9cb6-4915e2d497ef@labn.net>
Date: Mon, 11 Nov 2019 11:33:09 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB436655746DE65AF6B9DFDF23B57E0@MN2PR11MB4366.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Source-L: Yes
X-Exim-ID: 1iUCcs-004DWg-8X
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([IPv6:::1]) [127.0.0.1]:34505
X-Source-Auth: lberger@labn.net
X-Email-Count: 3
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/CmroXeyciiMnqKdw29_9UY9FIEg>
Subject: Re: [Netmod-ver-dt] [netmod] NETMOD 106 Schedule and Call for Presentations
X-BeenThere: netmod-ver-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NetMod WG YANG Model Versioning Design Team <netmod-ver-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod-ver-dt/>
List-Post: <mailto:netmod-ver-dt@ietf.org>
List-Help: <mailto:netmod-ver-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2019 16:33:17 -0000

Hi,

We discussed this today.  Our preference would be for a thin/minimal 
draft covering the tooling and the output showing the intended direction 
for the work and for this to be included in the set adoption call.  It 
really doesn't have to be complete /much -- just enough to show intended 
direction.  Hopefully this is minimal enough effort for it to be 
submitted quite rapidly.

Does that work for you?

Thanks,

Lou (Joel and Kent)

On 11/5/2019 11:43 AM, Rob Wilton (rwilton) wrote:
> Ack.  Thanks.
>
>
>
>> -----Original Message-----
>> From: Lou Berger <lberger@labn.net>
>> Sent: 05 November 2019 16:35
>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs <netmod-
>> chairs@ietf.org>
>> Cc: netmod-ver-dt@ietf.org
>> Subject: Re: [netmod] NETMOD 106 Schedule and Call for Presentations
>>
>> I'll discuss with my co-chairs. I think this is also fair to raise at the
>> meeting...
>>
>> On 11/5/2019 10:49 AM, Rob Wilton (rwilton) wrote:
>>> We might like to ask you (the chairs) to reconsider the discussion as to
>> whether we can do a call for adoption on some of these drafts?
>>> I know that the chairs have previously wanted to adopt the drafts as an
>> entire set to cover the whole solution.  And we are obviously still
>> missing the draft of schema comparison tooling.  Arguably this draft isn't
>> required for the solution, only strongly desirable to have because it is
>> only intending to address requirement 2.2 (which has always been a SHOULD
>> rather than a MUST):
>>>          2.2  A mechanism SHOULD be defined to determine whether data
>>>               nodes between two arbitrary YANG module revisions have (i)
>>>               not changed, (ii) changed in a backwards-compatible way,
>>>               (iii) changed in a non-backwards-compatible way.
>>>
>>> Note, there is no intention of dropping this last draft, and we already
>> have some pyang tooling/scripts that perform this task, but I think that
>> it could also realistically follow on a bit after the other drafts.
>>>
>>> All the "MUST" requirements are intended to be addressed by the set of
>> drafts below.
>>>
>>> Personally, I think that these 4 drafts are all in good enough shape
>> that they could be considered for an WG adoption call:
>>>     draft-verdt-netmod-yang-solutions-02
>>>     draft-verdt-netmod-yang-module-versioning-01
>>>     draft-verdt-netmod-yang-semver-01
>>>     draft-rwilton-netmod-yang-packages-02
>>>
>>> I think that this draft is also well on its way to be ready for WG
>> adoption:
>>>     draft-wilton-netmod-yang-ver-selection-01
>>>
>>>     - IMO, the key bit that we still need to figure out for this draft is
>> exactly how packages are sensibly put together (e.g. for optional feature
>> sets and bugfixes) in a way that doesn't defeat one of the main benefits
>> of packages for clients (i.e. being able to know the exact device schema
>> offline without having to download/check the entirely of YANG library on
>> connection).  But equally I see no reason why that couldn't be figured out
>> after the document as been adopted as a WG item.
>>>
>>> Finally, doing an adoption call on these drafts may act as a forcing
>> function to get the WG to discuss/agree whether this solution is on the
>> right path.
>>> Of course, it is your decision.
>>>
>>> Thanks,
>>> Rob
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Lou Berger <lberger@labn.net>
>>>> Sent: 05 November 2019 15:11
>>>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; NetMod WG Chairs
>>>> <netmod- chairs@ietf.org>
>>>> Cc: netmod-ver-dt@ietf.org
>>>> Subject: Re: [netmod] NETMOD 106 Schedule and Call for Presentations
>>>>
>>>> You're the headliner -- so should have the time ;-)
>>>>
>>>> On 11/4/2019 4:49 AM, Rob Wilton (rwilton) wrote:
>>>>> 1) DT Update overview & status update (10 mins, Rob?):
>>>>> YANG Module Versioning Requirements
>>>>> draft-ietf-netmod-yang-versioning-reqs-01
>>>>>
>>>>> YANG Versioning Solution Overview
>>>>> draft-verdt-netmod-yang-solutions-02
>>>>>
>>>>> 2) Updated YANG Module Revision Handling (10 mins, tbd?):
>>>>> draft-verdt-netmod-yang-module-versioning-01
>>>>>
>>>>> 3) YANG Semantic Versioning (10 mins, Joe?)
>>>>> draft-verdt-netmod-yang-semver-01
>>>>>
>>>>> 4) YANG Packages (25 mins, Rob)
>>>>> draft-rwilton-netmod-yang-packages-02
>>>>>
>>>>> 5) YANG Schema Version Selection (25 mins, tbd?)
>>>>> draft-wilton-netmod-yang-ver-selection-01
> _______________________________________________
> Netmod-ver-dt mailing list
> Netmod-ver-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod-ver-dt
>