> -----Original Message----- > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs- > university.de] > Sent: Thursday, April 28, 2016 5:39 AM > To: Ing-Wher (Helen) Chen <[email protected]> > Cc: Martin Bjorklund <[email protected]>; [email protected] > Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models > > On Wed, Apr 20, 2016 at 03:24:25PM +0000, Ing-Wher (Helen) Chen wrote: > > > > The technical problem of generalizing is the difficulty in creating a > > URN based on domain names that is also persistent. Limiting the scope > > of the "rdns" URN namespace to only YANG modules means that there is a > > smaller persistency problem to solve and that it can be solved by > > taking advantage of properties specific to YANG modules. > > > > Can you detail which properties specific to YANG modules make the smaller > persistency problem solvable?
It's both what YANG module namespaces don't need to have and the limited case where a non-persistent namespace results in a collision. The property that YANG module namespaces don 't need to have is that YANG module namespaces are not used to provide global resolution, where the persistence of a namespace is particularly important. (Please see RFC 3406 top of page 13 <https://tools.ietf.org/html/rfc3406#page-13> for the Identifier persistence discussion.) The potential collision of a non-persistent namespace is described In the example in <http://www.ietf.org/mail-archive/web/netmod/current/msg15818.html> . When a namespace collision does occur, the problem is limited to a device that has an administrator and the solution is simple. This is also stated in draft-chen-rdns-urn , in the "Identifier Persistence Considerations" section at the bottom of page 5 <https://tools.ietf.org/html/draft-chen-rdns-urn-06#page-5> . Thanks, Helen _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
