Re: [Netconf] LC on subscribed-notifications-10

[Kent Watsen <[e-mail]>]

<Kent14>

<Eric13> Per this thread, this is now a configured-replay empty object (rather than a start-time).  This empty object simply tells the publisher to push off all events retained from a stream since reboot.  And yes, all configured subscriptions will restart simultaneously.  But without this feature, receivers will not see events from boot to transport establishment.  And without this feature, two different configured receivers might get different initial events as the transport might not be brought up simultaneously.
 
<Kent13> I'm unsure how this addresses my concern that replaying is unnecessary for configured subscriptions…I somehow thought that it might be related since it's listed here.   Separately, I'm unclear about what this change does, I know you provide some explanation above, but you can say it differently or provide an example or two to illustrate what you mean?   Does this change introduce the problem you mentioned before about duplicates events being sent?  
 
<Eric14>  Here is a link to the slides which I have put together for IETF 102 which hopefully hits your request above:
 
https://github.com/netconf-wg/rfc5277bis/blob/master/draft-configured-replay-slides-ietf102.pdf  
 
 
<Kent14> not really.  The switch to "configured-replay" seems orthogonal, likely due to it being perceived as easier than specifying an exact time.  Separately, as a comment on the slides, perhaps list both Pros and Cons?  I provided 4 perceived benefits in a recent email…




BTW, the description statement on replay-start-time seems incorrect, with the node now being config false, how can it be used to "trigger" anything?  
 
<Eric14>  replay-start-time exists as part of the establish-subscription RPC.   The RPC is where the triggering occurs.

<Kent14> right, and that's fine, but it's not okay for configured subscriptions.   Subscription-policy uses subscription-policy-dynamic, the description needs to be refined, like it was for the subscription-started notification.


Kent // contributer