Re: Netconf Notifications WC LC: Issues & Proposed Resolutions - Part 1

["tom.petch" <cfinss@dial.pipex.com>]

By analogy with RFC4741, I think that the IANA consideration for
capability:notification should specify

index       :notification
capability identifier   urn:ietf:params:netconf:capability:notification:1.0
Specification 3.1 of this document
[not sure about this is; is the expectation that
everyone will implement everything eg subtree and XPath filtering or is
'notification' too big to be just one capability or should it be subdivided (as
you  might guess, I am thinking of different conformance clauses in various
other standards)?]

Tom Petch


----- Original Message -----
From: "Sharon Chisholm" <schishol@nortel.com>
To: "Netconf (E-mail)" <netconf@ops.ietf.org>
Sent: Wednesday, April 11, 2007 9:45 PM
Subject: Netconf Notifications WC LC: Issues & Proposed Resolutions - Part 1


hi

<snip>

9. ToC: No entry for IANA Considerations (no section either) (Source
Andy)

Proposed Resolution: Add an 'IANA Considerations' section to request
allocation of namespaces for the Schemas.

"This document registers two URIs for the NETCONF XML namespace in the
   IETF XML registry [7].

   Following the format in RFC 3688, IANA has made the following
   registration.

   URI: urn:ietf:params:netconf:capability:notification:1.0

   URI: urn:ietf:params:xml:ns:netmod:notification

   Registrant Contact: The IESG.

   XML: N/A, the requested URI is an XML namespace."

Update various references to content namespace to use this tag.

<snip>


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