Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sat, 21 July 2018 10:12 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74670130EA9 for <netmod@ietfa.amsl.com>; Sat, 21 Jul 2018 03:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 tlo44G-a50Ga for <netmod@ietfa.amsl.com>; Sat, 21 Jul 2018 03:12:25 -0700 (PDT)
Received: from anna.localdomain (firewallix.jacobs-university.de [212.201.44.247]) by ietfa.amsl.com (Postfix) with ESMTP id 54B25130DDF for <netmod@ietf.org>; Sat, 21 Jul 2018 03:12:25 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 7C5D42362EB9; Sat, 21 Jul 2018 12:12:24 +0200 (CEST)
Date: Sat, 21 Jul 2018 12:12:23 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Cc: NetMod WG <netmod@ietf.org>
Message-ID: <20180721101223.vg2hipa6ocfhmemy@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, NetMod WG <netmod@ietf.org>
References: <CABCOCHQ47ztJTPaZMZK7FWHsRPk1jN6SuuAWtg08rmtVgUPEWw@mail.gmail.com> <20180721054935.cgsgpxvnkmnpro6n@anna.jacobs.jacobs-university.de> <CABCOCHRFJNsFYF2yiR_+JXA-McD1XMB-iHEaMiA6LrQg0cSw5g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABCOCHRFJNsFYF2yiR_+JXA-McD1XMB-iHEaMiA6LrQg0cSw5g@mail.gmail.com>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OfZxZbsaR3Al2e7ofNXotvFCMGg>
Subject: Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.27
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 21 Jul 2018 10:12:28 -0000
On Sat, Jul 21, 2018 at 01:48:37AM -0700, Andy Bierman wrote: > > But you can tell the 2 subtrees apart this way. > If I change /foo from a container to a list, then how do you support both > implementations > of container /foo and list /foo at the same time? > Well, all of this is the consequence of moving from the current naming system (module, path) to (module,path,version). Once we allow non-backwards compatible changes, then we may have to find ways to support different versions of a module (i.e, during session establishment the client selects a version context to work with). To be clear about my involvement in the versioning design team: I am personally not convinced that a different versioning scheme is going to be simpler; certain things that are simple and robust today will become more complex and fragile. I decided to get involved in order to point out that moving to a (module,path,version) naming scheme has many implications since everywhere where we currently use (module,path) we need to think about now required version context is coming from. This goes far beyond YANG imports, this impacts likely protocols, the proposed instance document storage format, NACM rules may need to be interpreted in a version context etc. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
- [netmod] backward compatibility requirements in d… Andy Bierman
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Christian Hopps
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Christian Hopps
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Kent Watsen
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Andy Bierman
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Juergen Schoenwaelder
- Re: [netmod] backward compatibility requirements … Robert Wilton
- Re: [netmod] backward compatibility requirements … Christian Hopps
- Re: [netmod] backward compatibility requirements … Kent Watsen