[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Notification data model structure
In line.
Dan
> -----Original Message-----
> From: owner-netconf@ops.ietf.org
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Sharon Chisholm
> Sent: Wednesday, May 02, 2007 10:03 PM
> To: Netconf (E-mail)
> Subject: RE: Notification data model structure
>
> Hi
>
> I was getting ready to press send on the update ...
>
> I can easily enough add a <netconf> wrapper to the content
> schema in this draft. I guess then in theory we would then
> define the monitoring information in
> http://www.ietf.org/internet-drafts/draft-chisholm-netconf-mon
> itoring-00
> .txt to extend that object.
>
> I'm not sure what the procedure is for making these sort of
> changes post working group last call.
The document is still in the WG hands, so you are allowed to do any
change you want. The chairs should establish the process to make sure
the changes enjoy the consensus of the WG (another LC, fast track LC,
question the list, etc.)
>
> For the second issue, this seems more subjective. Do we
> expect people will use these complex types?
I would say yes (contributor opinion)
>
> Sharon
>
--
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/>