RE: IANA considerations update for NETCONF protocol draft

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

> 10.4.  NETCONF Enterprise Capability URNs
> 
>    This document requests that IANA create a registry for allocating
>    NETCONF capability identifiers to enterprises.  Allocation from the
>    registry is on a First Come First Served basis, but a specification
>    is required in the form of Appendix C of this document.
> 
>    Following the guidelines in RFC 3553 [7], IANA is requested to assign
>    a NETCONF sub-namespace as follows:
> 
>    Registry name: netconf-enterprise
> 
>    Specification: To be provided by the registrant.  The specification
>    document must conform to Appendix C of this document.
> 

But appendix C now states:

   C.1.3.  Capability Identifier

   The {name} is identified by following capability string:

      urn:ietf:params:xml:ns:netconf:capability:{name}:1.0

Which to me seems to apply be in sync with sect 10.3
for sect 10.4, it probably should be:

      urn:ietf:params:xml:ns:netconf-enterprise:capability:{name}:1.0

But even then, how do you avoid conflicts between multiple enterprises,
and how do you you which capability is from which enterprise?

Bert

>    Repository: IANA is requested to store the submitted specifications
>    in a public location such as
>    http://www.iana.org/assignments/netconf/capabilities.html.
> 
>    Index value: The capability name.
> 

--
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/>