Re: [netmod] 6087bis namespace recommendations

Ladislav Lhotka <lhotka@nic.cz> Fri, 15 January 2016 15:20 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 $3112$)
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <CABCOCHQtEFH44gLqc4hRfpxv6kaaoW99qM04JKngNMSeRqkkzA@mail.gmail.com>
Date: Fri, 15 Jan 2016 16:20:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9D2D332-33CD-41B6-BAE6-DD6A8B59AD9B@nic.cz>
References: <20160111.101526.1720014765007751699.mbj@tail-f.com> <20160111092831.GA41568@elstar.local> <20160111.112143.1731089672764861015.mbj@tail-f.com> <20160111104855.GA41658@elstar.local> <01d301d14ef1$814dcee0$4001a8c0@gateway.2wire.net> <CABCOCHTXa-XTkY73QhM3gzFbx0zQ_a24hijCz2HOaOQ9odL9DA@mail.gmail.com> <m2oacnnkbf.fsf@birdie.labs.nic.cz> <20160115114924.GA12322@elstar.local> <301372A9-0333-4D56-B501-207C405C79F3@nic.cz> <CABCOCHRrBSn7VX3dK54TZ_GES86ANn9xzzFQFue5sJF_d17EuQ@mail.gmail.com> <9DA7DD58-6890-4BC2-A7BE-6D6F15F1B08D@nic.cz> <CABCOCHQtEFH44gLqc4hRfpxv6kaaoW99qM04JKngNMSeRqkkzA@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/bKQpHhQBSwcf0Aty7fumr6Cx7BQ>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] 6087bis namespace recommendations
Precedence: list

> On 15 Jan 2016, at 15:49, Andy Bierman <andy@yumaworks.com> wrote:
> 
> 
> 
> On Fri, Jan 15, 2016 at 6:19 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> 
> > On 15 Jan 2016, at 15:10, Andy Bierman <andy@yumaworks.com> wrote:
> >
> >
> >
> > On Fri, Jan 15, 2016 at 3:55 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> >
> > > On 15 Jan 2016, at 12:49, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > >
> > > On Fri, Jan 15, 2016 at 12:39:16PM +0100, Ladislav Lhotka wrote:
> > >>
> > >> Does this solve any practical problem? Modules are imported based on
> > >> the module name and revision. On the other hand, it does create new problems:
> > >> namespace URIs and their mappings to prefixes may be spread in many
> > >> places in the code, and these would have to be manually edited after an
> > >> I-D -> RFC transition.
> > >>
> > >> It would IMO be much better to use revision numbers rather than dates,
> > >> and adopt a convention, e.g., that modules in the I-D stage have
> > >> revisions 0.x that get bumped with each new revision of the I-D.
> > >>
> > >
> > > Lada, this is not how our current YANG 1.0 versioning and revision
> > > rules work and we are not going to change them in YANG 1.1 either.
> > > The rules we have do make a distinction between published modules and
> > > modules that are unpublished.
> >
> > I am not proposing it. The problem I'd like to get solved is proper module revisioning already at the I-D stage so that implementations be able to distinguish one revision from another. Appending DRAFT to the namespace URI doesn't help anything.
> >
> >
> >
> > Changing the module name constantly does not help.
> > It would be better to just keep using revision dates.
> 
> Some I-Ds don't do even that, for example acl-model uses the same revision date in subsequent I-D revisions. I checked that this actually violates a MUST in RFC 6087.
> 
> 
> 
> If the YANG module does not change from one I-D to the next,
> then the revision date does not need to change.

6087(bis) says:

   It is acceptable to reuse the same revision statement within
   unpublished versions (i.e., Internet-Drafts), but the revision date
   MUST be updated to a higher value each time the Internet-Draft is re-
   posted.

I think it is a good idea.

Lada

> 
>  
> Lada
> 
> 
> Andy
>  
> >
> >
> > Lada
> >
> >
> >
> > Andy
> >
> > >
> > > /js
> > >
> > > --
> > > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > > Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> > > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> >
> > --
> > Ladislav Lhotka, CZ.NIC Labs
> > PGP Key ID: E74E8C0C
> 
> --
> Ladislav Lhotka, CZ.NIC Labs
> PGP Key ID: E74E8C0C

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

[netmod] 6087bis namespace recommendations Martin Bjorklund
Re: [netmod] 6087bis namespace recommendations Juergen Schoenwaelder
Re: [netmod] 6087bis namespace recommendations Martin Bjorklund
Re: [netmod] 6087bis namespace recommendations Juergen Schoenwaelder
Re: [netmod] 6087bis namespace recommendations Mahesh Jethanandani
Re: [netmod] 6087bis namespace recommendations t.petch
Re: [netmod] 6087bis namespace recommendations Andy Bierman
Re: [netmod] 6087bis namespace recommendations Ladislav Lhotka
Re: [netmod] 6087bis namespace recommendations Juergen Schoenwaelder
Re: [netmod] 6087bis namespace recommendations Ladislav Lhotka
Re: [netmod] 6087bis namespace recommendations Andy Bierman
Re: [netmod] 6087bis namespace recommendations Andy Bierman
Re: [netmod] 6087bis namespace recommendations Ladislav Lhotka
Re: [netmod] 6087bis namespace recommendations Ladislav Lhotka
Re: [netmod] 6087bis namespace recommendations Andy Bierman
Re: [netmod] 6087bis namespace recommendations Ladislav Lhotka
Re: [netmod] 6087bis namespace recommendations Robert Wilton
Re: [netmod] 6087bis namespace recommendations Andy Bierman
Re: [netmod] 6087bis namespace recommendations Juergen Schoenwaelder
Re: [netmod] 6087bis namespace recommendations Robert Wilton
Re: [netmod] 6087bis namespace recommendations t.petch