RE: IANA considerations update for NETCONF protocol draft

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

Thanks Bert, comments and updated sections below.

> for an informational or experimental.
> So that is why I think I prefer "Standards Action".

"Standards Action" is fine with me too.
 
> >    The initial content of the registry will be the capability URNs
> >    defined in Section 8.  Once further experience is gained with
> >    NETCONF, this sub-namespace may be used for additional purposes.
> > 
> I think last sentence can go away, because defining the registry and
> requiring Standards Action (or IETF consensus if that is what the WG
> wants) basically allow for that Netconf impact anyway.

Ok.

> > 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.
> > 
> 
> Mmm the template in appendix C looks (to me anyway) a template to
> register new entries in the "standards" space, not in the vendor 
> or enterprise space. Or am I missing something?

We can replace the "standard" NETCONF URN prefix in Appendix C with
an {insert your capability URI here} wildcard and the
single Appendix C should be ok.

Here are the 2 updated sections from IANA considerations.

10.3.  NETCONF Capability URNs

   This document requests that IANA create a registry for allocating
   NETCONF capability identifiers.  Allocation from the registry
   requires IETF Standards Action.

   The initial content of the registry will be the capability URNs
   defined in Section 8.

   Following the guidelines in RFC 3553 [7], IANA is requested to assign
   a NETCONF sub-namespace as follows:

   Registry name: netconf

   Specification: Section 8 of this document.

   Repository: The following table.

   +--------------------+----------------------------------------------+
   | Index              | Capability Identifier                        |
   +--------------------+----------------------------------------------+
   | :writable-running  | urn:ietf:params:netconf:capability:writable- |
   |                    | running:1.0                                  |
   | :candidate         | urn:ietf:params:netconf:capability:candidate |
   |                    | :1.0                                         |
   | :confirmed-commit  | urn:ietf:params:netconf:capability:confirmed |
   |                    | -commit:1.0                                  |
   | :rollback-on-error | urn:ietf:params:netconf:capability:rollback- |
   |                    | on-error:1.0                                 |
   | :validate          | urn:ietf:params:netconf:capability:validate: |
   |                    | 1.0                                          |
   | :startup           | urn:ietf:params:netconf:capability:startup:1 |
   |                    | .0                                           |
   | :url               | urn:ietf:params:netconf:capability:url:1.0   |
   | :xpath             | urn:ietf:params:netconf:capability:xpath:1.0 |
   +--------------------+----------------------------------------------+

   Index value: The capability name.

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.

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