security considerations section

[Andy Bierman <ietf@andybierman.com>]

Hi,

I want to start a thread to discuss what needs to be in the
Security Considerations section of the Notifications draft.

IMO, there does not seem to be that much we need to say, because
the <notification> elements are never sent before the transport
layer and the netconf layer (capabilities exchange) have been
established, and the manager has been identified and authenticated.

We need to explain all the vulnerabilities in some detail,
and identify what can and should "be secured" by an operator:

- <create-subscription> invocation
- use of <kill-session>
- read-only data models
- read-write data models
- notification content

Is this list complete?
Does anyone want to volunteer to write text for the Editor
to incorporate into the next draft?

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