Re: [Netconf] WGLC on restconf-notif-08

["Eric Voit (evoit)" <[e-mail]>]

Cutting this part of the thread to one topic

>     >       Also, "modify-subscription" may be sent on some other session.
>
>     > <RR> As long as from same subscriber I assume. Do we care about NAT
>     >     scenarios?
> 
>     There is nothing in SN that says that modify-subscription must be from
>     the same subscriber.

Up until  SN -v13, the text ensured the subscriber was the only one able to make any changes.  The current text -v17 does not have this constraint, and does allow an operator to modify a subscription in-flight.  Personally I don't like this flexibility.  I think it opens a security hole.   If other people have security configuration concerns with this flexibility (i.e., a new non-administrative subscriber might have permissions enabling them to make changes to a subscription), we should return the constraint to SN.  This re-introduced text would mirror that which exists for delete subscription.  I.e., "Dynamic subscriptions can only be modified via this RPC using a transport session connecting to the subscriber."

>     IMO the idea of restricting some rpcs to "the same transport session"
>     is unnecessary, and obviously problematic.
> <RR2> Problematic from an implementation view or from a functionality view?
> Would like to hear from others on this.
> 
>     I think that the
>     restriction should be removed from delete-subscription (and then
>     remove kill-subscription, since it is the same as
>     delete-subscription).

Some of the first comments received on SN were to segment RPC permissions for 'delete-subscription' and 'kill-subscription'.  Many have seen this differentiation as worthwhile.  

Eric

> Regards,
> Reshad.
> 
> 
>     /martin
>