Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities

[Kent Watsen <[e-mail]>]

In reviewing the draft, I don't see where the file format is defined.    I understand the module defining a 'container' for protocol-accessible nodes, but shouldn't it define an 'sx:structure' for the file format?  I suggest moving the contents of the "datastore-subscription-capabilities" container to a 'grouping' and then have both the container and an 'sx:structure' use that grouping.

On the below:

> I suspect that you will need to do a security analysis per YANG object.   This has been done the other YANG push family.
> BALAZS: The full module is readOnly and not sensitive or private in any manner.  The security text for the readOnly parts of YangPush is the exact same text: not very informative, but gives you the illusion of security awareness.
>  
> I suspect that manipulating the reporting intervals could have some security implications.   E.g., a hacker could push up the damping period or periodic interval to a level where the information they are changing then becomes invisible to a monitoring system.
> BALAZS: The full YAM is read-only so manipulating the data is not a concern.


The draft should say something like:

1. All protocol-accessible are read-only and cannot be modified.  The nature of the read-only data is not deemed to be sensitive in a way necessitating access-control restrictions (e.g., NACM) beyond the client being authenticated.

2. When a file format, the protection afforded by a mutually authenticated transport protocol.  Protection of the data must be performed manually, so as to ensure that the data is neither seen nor modified in transit.

Reword as needed.


Kent // contributor