> On Jan 11, 2016, at 1:15 AM, Martin Bjorklund <m...@tail-f.com> wrote: > > Hi, > > Currently, 6087bis says that standards-track, published and > unpublished modules SHOULD use the URN prefix > "urn:ietf:params:xml:ns:yang:". > > There are two issues with this: > > 1. We already publish experimental modules w/ this prefix. > (ietf-netconf-time and ietf-complex-types).
True. > > So 6087bis should remove "standards track" from this > recommendation. Yes. > > 2. There was some discussion about recommending a different URN > prefix for unpublished modules (i.e., modules in Internet > Drafts). > > Should 6087bis recommend some special urn prefix for drafts, > with a note to the RFC editor to change the namespace once it > has been registered with IANA? I am inclined to let the urn prefixes be what they will be once the document gets adopted as an RFC. There are plenty of tools and work today that extracts the module and uses it as is on an experimental basis. Having to change them every time the drafts changes or modify existing code once the module it uses becomes RFC is painful. Besides, the chances of conflict are low with the URN namespaces, so why make the process onerous. > > And another issue. 6087bis also has this: > > OLD: > > The following examples are for non-Standards-Track modules. > The domain "example.com" SHOULD be used in all namespace URIs > for example modules. > > http://example.com/ns/example-interfaces > > http://example.com/ns/example-system > > > First of all, the sentence about non-Standards-Track modules is > confusing. Second, since the publication of RFC 6087, RFC 6963 has > been published, which defines a URN for examples. I suggest we update > 6087bis like this: > > NEW: > > Example modules in all types of documents SHOULD use a namespace > with either the example URN [RFC 6963] or the domain "example.com". > For example: > > urn:example:interfaces > > http://example.com/ns/example-system > <http://example.com/ns/example-system> Agree. > > > > /martin > > > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod Mahesh Jethanandani mjethanand...@gmail.com
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
