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

Re: Notification Issue List -- DRAFT



Hello,
About my comments:
I16) too many namespaces: open
I17) closed
I18) closed?
I19) closed
I20) closed
I21) closed
I22) closed
I26) open, not so important
I27)  Open not so important
I28) open
I29) open
I30) Open
I31) Open, for me this is important
I32) open
I33) open
I34) open
I35) open

other comments:
- if starttime is in future, it should have no effect, same as if it would be missing

- all times should be converted to UTC for internal use, that solves time-zone and time leap problems

- I like the warning for the case when we asked for a too early start-time. Page 27 sec 6.1 para 3

- I prefer to keep named profiles, but can live without them.

- Timestamps SHOULD be generation time. The term SHOULD allows
the implementations to deviate from this, but states our wish.

- it should be allowed to add new error codes.
I think having more specific error codes is a very much needed and good idea.
One of our difficulties with SNMP was just this, that
the error codes provided by SNMP was limited.
I understand that this is problematic with the XML
 so the error codes shall go into some place like the error-app-tag.

Balazs
PS: Sorry and  I hope it is not to late, but at the moment I am occupied with  my new baby.

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