Re: quick check of notification-11

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

A minor quirk - I see a missing solidus in 3.2.5.1
"<netconf xmlns="urn:ietf:params:xml:ns:netmod:notification">
           <streams/>
         <netconf>
"

and an uncertainty - the I-D does not register the XML Schema defined in
sections 4 and 3.4, just their targetNamespace; is this intentional?

Also in IANA considerations, it might be clearer if the registration of the
capability urn refers to the named registry created by RFC4741 s.10.3; obvious
to those up to their ears in netconf, perhaps less so to those with an IANA-wide
remit.

Tom Petch


----- Original Message -----
From: "Andy Bierman" <ietf@andybierman.com>
To: "Netconf (E-mail)" <netconf@ops.ietf.org>
Sent: Monday, November 12, 2007 9:15 PM
Subject: quick check of notification-11


> Hi,
>
> The new Notifications draft is out:
> http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-11.txt
>
> Could the people who made comments on -10 check that their bugs/issues
> were properly addressed?
>
> Unless there are no objections, the 1 hour NETCONF meeting in Vancouver
> dedicated to Notification issues will be canceled, because we are done. (!)
>
> Many thanks to Sharon and Hector for all their hard work,
> and to all the people who reviewed and improved it along the way.
>
>
> thanks,
> Andy
>
>
> --
> 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/>