Re: [netmod] Adoption of versioning design team docs

Susan Hares <> Tue, 10 March 2020 09:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 80BC23A0EA7; Tue, 10 Mar 2020 02:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.233
X-Spam-Level: *
X-Spam-Status: No, score=1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JsiHLiKlwPRG; Tue, 10 Mar 2020 02:15:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0678D3A0EC8; Tue, 10 Mar 2020 02:15:18 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <>
To: "'Lou Berger'" <>, "'NETMOD Group'" <>
Cc: <>
References: <> =?utf-8?q?=3CDM5?= =?utf-8?q?PR08MB2633011491B1A7880806E54F9BFE0=40DM5PR08MB2633=2Enamprd08=2E?= =?utf-8?q?prod=2Eoutlook=2Ecom=3E?=
In-Reply-To: =?utf-8?q?=3CDM5PR08MB2633011491B1A7880806E54F9BFE0=40DM5PR08MB?= =?utf-8?q?2633=2Enamprd08=2Eprod=2Eoutlook=2Ecom=3E?=
Date: Tue, 10 Mar 2020 05:15:14 -0400
Message-ID: <00bd01d5f6bc$68e0dfb0$3aa29f10$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BE_01D5F69A.E1D66BA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGS1Z8kktj4fnDV2SiOa4whQ8pHBQKg0HumqLLGxyA=
Content-Language: en-us
X-Antivirus: AVG (VPS 200309-0, 03/09/2020), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: <>
Subject: Re: [netmod] Adoption of versioning design team docs
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Mar 2020 09:15:20 -0000

Lou and WG –


I not aware of any IPR relating to these drafts. 


Susan Hares 


From: netmod <> On Behalf Of Lou Berger
Sent: Monday, March 2, 2020 5:30 PM
To: NETMOD Group <>
Subject: [netmod] Adoption of versioning design team docs


We'd like to start a two week adoption call for the set of documents described below by Rob.  To be specific, this includes
1) draft-verdt-netmod-yang-solutions-03
2) draft-verdt-netmod-yang-module-versioning-01
3) draft-verdt-netmod-yang-semver-01
4) draft-rwilton-netmod-yang-packages-03
5) draft-wilton-netmod-yang-ver-selection-02
6) draft-verdt-netmod-yang-schema-comparison-00
The adoption call ends in two weeks, on March 16.  
Please voice your support or objections on list.  While we prefer to adopt as a set, objections on specific documents are acceptable.
Netmod Chairs
On 2/29/2020 2:21 AM, Rob Wilton (rwilton) wrote:

Netmod chairs,
The version selection draft draft-wilton-netmod-yang-ver-selection-02 is now posted.  With that, the YANG versioning design team would like to please request you make an WG adoption call for these documents.
The updated full list is:
1) draft-verdt-netmod-yang-solutions-03
  - Solution overview, updated since 106 to cover updates to version selection and schema comparison drafts.
2) draft-verdt-netmod-yang-module-versioning-01
  - Base module versioning solution, unchanged from the version presented at 106.
3) draft-verdt-netmod-yang-semver-01
  - YANG Semantic version numbers, unchanged from the version presented at 106.
4) draft-rwilton-netmod-yang-packages-03
  - YANG packages draft, updated since 106
5) draft-wilton-netmod-yang-ver-selection-02
  - Version selection, updated since 106, as per notes below
6) draft-verdt-netmod-yang-schema-comparison-00
  - Schema comparison tooling, unchanged from the version presented at 106.
The main changes to the version selection draft are:
  - We have tried to simplify the model, but at the same time give servers more flexibility about how they implement version selection and what it can be used for.  E.g. if the server wants to allow a client to choose between different schema versions, but require that all clients use the same schema version, that is now possible
  - The draft explicitly disallows schema-selection happening mid-session
  - The solution allows the server to require clients to configure schema-sets before they are used
  - The solution provides more information about which schema-sets are compatible with each other