Re: [netmod] Adoption of versioning design team docs

[Martin Björklund <[e-mail]>]

[second attempt, sorry for duplicates]

Hi,

By document:

draft-verdt-netmod-yang-module-versioning-01

  This is a great contribution to the YANG ecosystem.  It is very well
  written, and I would like to see this document proceed quickly.  The
  solutions it proposed are really needed.  I have one objection
  though; in 7.1 the text says:

    All IETF YANG modules MUST include revision-label statements for all
    newly published YANG modules, and all newly published revisions of
    existing YANG modules.  The revision-label MUST take the form of a
    YANG semantic version number [I-D.verdt-netmod-yang-semver].

  I strongly disagree with this new rule.  IETF modules use a linear
  history, so there are no reasons to use "modified semver".

  I support the adoption of this document.

  (I will send a review of this document in a separate mail)


draft-verdt-netmod-yang-semver-01

  This draft proposes a way to express how a given revision is
  backwards compatible in a very short format.  With the new extension
  statements in draft-verdt-netmod-yang-module-versioning, this
  information is already present in the revision history of a module.
  (One possible exception is editorial changes, but that can easily be
  fixed by adding an "editorial" extension to "ietf-yang-revisions").

  I don't think this document should be adopted.


draft-rwilton-netmod-yang-packages-03

  I support the adoption of this document.


draft-wilton-netmod-yang-ver-selection-02

  I think the solutions proposed in this draft are overly complex and
  some of them are probably impossible to implement correctly in real
  world use cases.

  I don't think this document should be adopted.


draft-verdt-netmod-yang-schema-comparison-00

  I support the adoption of this document.



/martin


Lou Berger <[e-mail]> wrote:
> Hi,
> 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
> >
> > Regards,
> > Rob
> >
> >