[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: notification issues update (draft)

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.

So is it okay with everyone if we have both event types?




Sharon



Andy



-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] Sent: Thursday, August 23, 2007 7:50 AM 
To: Chisholm, Sharon (CAR:ZZ00)
Cc: netconf@ops.ietf.org
Subject: Re: notification issues update (draft)

"Sharon Chisholm" <schishol@nortel.com> wrote:

<Andy>
   - the replayComplete event type is renamed to notificationComplete.
     It is sent if stopTime is present, just before the agent returns
     to accepting all RPC operations (normal mode).
</Andy>

I'm not sure I agree with this one. This is the notification that gets
sent after replayed notifications are sent and before real-time ones are sent (if applicable). Calling it notificationComplete would seem to imply something else. 

We discussed this in Chicago.  There are two things that can happen:

  1.  when the last replayed notif has been sent, and the live feed
      starts. (replayComplete)

  2.  when a stopTime is given, and the last notif has been sent;
      after this the session switches back to normal command-response
      mode. (notificationsComplete)

A manager needs to know when the session switches back to normal mode,
so item 2 must be signalled.  However, it has been argued that a manager
doesn't care about item 1.



/martin


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





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