Re: replayLogStartTime

[Andy Bierman <ietf@andybierman.com>]

Sharon Chisholm wrote:
> Huh? I think I missed something.
>
> 1. Capability # notification is <create-subscription>
>
> 2. Presence of replaySupport object against a stream means that stream
> supports replay.

oops -- you are right.
I confused it with the #interleave capability

> Then we are discussing specific behaviour of the replayLogStartTime
> object. Nothing in this object indicates whether or not functionality is
> supported. It only tells you how much stuff is available in the log at
> this point in time.  
>
> I don't think we want it conditional like Martin indicated. I think we
> need to pick one of
>
> A. It is the timestamp of the earliest notification in the log
> B. It is the timestamp of the start of the log.

Agreed -- it should be (A), since from a NETCONF manager POV,
there is no difference between no replay log and an empty replay log.


> Sharon

Andy


> -----Original Message-----
> From: Andy Bierman [mailto:ietf@andybierman.com] 
> Sent: Wednesday, September 05, 2007 11:00 AM
> To: Martin Bjorklund
> Cc: Chisholm, Sharon (CAR:ZZ00); netconf@ops.ietf.org
> Subject: Re: replayLogStartTime
>
> Martin Bjorklund wrote:
> > "Sharon Chisholm" <schishol@nortel.com> wrote:
> > > Hi
> > >
> > > Fair enough. It does allow you to tell the difference if the start 
> > > time is 1pm, you asked for 2pm, and the first notification replayed 
> > > was from 2:30. We could change it to be the timestamp of the start of
>
> > > the log which handles both cases.
> > So you want the value to be the timestamp of the first notification in
>
> > the log if any notifications are present, and log creation time
> > otherwise?   That would work, but more descriptive text that "start of
> > log" is needed.
> >
> > > And did people only want this object present when replay is supported
>
> > > on that stream?
> > Yes.
>
> So:
>
> capability #notification set means the <create-subscription> operation
> will be accepted.
>
> capability #replay set means the startTime and stopTime parameters will
> be accepted.
>
> replayLogStartTime set means there is a replay log.
>
> Capability #replay set but no replayLogStartTime means that the
> completely proprietary replay log collection control setup has not been
> done.
>
> Since there are no standard controls over the size and start time of the
> replay log, this timestamp object is the read-only indication of any
> replay config changes, plus an indication of the implied
> 'delete-oldest-first' garbage collection activity.
>
> > /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/>