[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NETCONF protocol IANA considerations & capability URNs

Rob Enns wrote:

I would like to go with the new format if nobody objects.

Essentially, we are removing the "xml:ns" from this formatted string,
since it doesn't add any information and it is inconsistent with
other URN definitions.

Andy

Here is a proposed IANA considerations section for the NETCONF
protocol draft. Also, while working through the various RFCs
3553 and 3688 I realized that the capability URNs shown in the
NETCONF protocol draft are incorrect. 

The URNs currently have the form:

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

This says that the capability is an XML namespace as defined
by RFC 3688. Strictly speaking, that is incorrect.

The capability URNs should really be a NETCONF protocol parameter a la RFC 3553. Something like:

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

If the WG approves, I will make this change to the protocol draft.

Here is a proposed IANA considerations section assuming the
capabilities are expressed as shown above. Please comment.

----

10.  IANA Considerations

10.1.  NETCONF XML Namespace

  This document requests that IANA assign a URI for the NETCONF XML
  namespace in the IETF XML registry [8].

  Following the format in RFC 3688, the following registration is
  requested.

  URI: Please assign the URI "urn:ietf:params:xml:ns:netconf" for use
  by the NETCONF protocol.

  Registrant Contact: The IESG.

  XML: This document.

10.2.  NETCONF XML Schema

  This document requests that IANA assign a URI for the NETCONF XML
  namespace in the IETF XML registry [8].

  Following the format in RFC 3688, the following registration is
  requested.

  URI: Please assign the URI "urn:ietf:params:xml:schema:netconf" for
  use by the NETCONF protocol.

  Registrant Contact: The IESG.

  XML: Appendix B of this document.

10.3.  NETCONF Capability URNs

  This document requests that IANA create a registry for allocating
  NETCONF capability identifiers.  Allocation from the registry is on a
  First Come First Served Basis, but a specification is required.

  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.

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

  Registry name: netconf

  Specification: This document.

  Repository: This document.

  Index value: The NETCONF 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/>






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