Re: notification issues update (draft)

[Andy Bierman <ietf@andybierman.com>]

Martin Bjorklund wrote:
> Andy Bierman <ietf@andybierman.com> wrote:
> > Sharon Chisholm wrote:
> > > Hi
> > >
> > > Actually we do. I've just heard from a colleague on this and he says
> > > they need this notification to trigger that it is time to perform
> > > mark&delete resynch clean-ups. 
> > Hmmm... the manager could do that based on eventTime, but whatever.
>
> Yes I don't quite understand what "mark&delete resynch clean-ups"
> means... why can't it be done with notificationComplete?

I'm not that sure either, but I figure it's not important
enough to argue over.  Perhaps it refers to overlap in the
replayed notifications stored on the manager?

> > So is it okay with everyone if we have both event types?
>
> So notificationsComplete marks the switch back to normal mode, and
> replayComplete marks the end-of-buffered events.
>
> What if stopTime < now?  Will you get both events?  Or will you get
> replayComplete *only* when EOF on the log is reached?

Yes, you would get both events, so the meaning of replayComplete
is not overloaded, and event-specific handlers do not have to be
aware of the stopTime value at all.

> /martin

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