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

Re: review of draft-ietf-netconf-notification-07.txt

David B Harrington wrote:

....
Note that "Note that ... Note that ... Note that ... Note that"  is
irritating!



yes -- this is my fault -- I will stop doing it, and this redundant
text should be removed from this draft is well.



Did we ever resolve the lowerCamel vs C-style naming? I see
"named-profile" and stopTime. Can we be consistent?



yes -- at the Prague meeting, and I think documented in the minutes.

Since we started using c-style-naming for our RPC method names
and their parameters, we decided to keep doing that.

To be more consistent with MIB object naming, the data model objects
are named with the lowerCamelNaming.

(It was a compromise to make both camps happy ;-)

IMO, it doesn't matter that much.  An implementation should
be able to handle any valid XML 'Name', and ignore these NETCONF
distinctions.



Note that ... I will send more later if I have time. ;-)

[a quick glance at security considerations - I recommend this section
include a discussion of the threats specific to notifications, and
specifically how to mitigate those threats (e.g., use the SSH
transport defined in RFCxxxx). I think this whole section will need
work to pass security review. I'll try to make some recommendations
later.]


Please do.  The sooner the better (i.e., better we do it now
then wait for the DISCUSS from Sam ;-)



David Harrington


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