RE: IANA considerations update for NETCONF protocol draft

["Rob Enns" <rpe@juniper.net>]

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Tom Petch
> Sent: Monday, December 05, 2005 1:10 AM
> To: Randy Presuhn; netconf
> Subject: Re: IANA considerations update for NETCONF protocol draft
> 
> From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> To: "netconf" <netconf@ops.ietf.org>
> Sent: Monday, December 05, 2005 2:42 AM
> Subject: Re: IANA considerations update for NETCONF protocol draft
> 
> 
> > Hi -
> >
> > > From: "McDonald, Ira" <imcdonald@sharplabs.com>
> > > To: "'Andy Bierman'" <ietf@andybierman.com>; "Rob Enns" 
> <rpe@juniper.net>
> > > Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; 
> <netconf@ops.ietf.org>
> > > Sent: Saturday, December 03, 2005 3:37 PM
> > > Subject: RE: IANA considerations update for NETCONF protocol draft
> > ...
> > > Instead, simply specify that Enterprise Capabilities MUST choose a
> > > _durable_ globally unique URI within one of the 
> registered DNS domains
> > > for that enterprise (i.e., using GUIDs based on MAC address is NOT
> > > allowed).
> > ...
> 
> > What happens when that domain name is recycled?  (E.g., the company
> > is swallowed by another, the domain registration is allowed 
> to lapse,
> > and some other orgnaization starts using it for thir own URIs.)
> >
> > Randy
> >
> 
> Then we should have used URN 'which are required to remain 
> globally unique
>    and persistent even when the resource ceases to exist or 
> becomes unavailable'
> [RFC3986]
> 
> Not sure that it is worth it though.


I'm not sure it's worth it either. My preference is to drop the IANA
allocated enterprise capability registry. Enterprises defining their
own capabilities can choose URIs that make sense to them. Much like
XML namespaces, common sense would dictate the choice of a URI that
won't clash with others. 

Rob

 
> Tom Petch

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>