RE: replayLogStartTime

["Sharon Chisholm" <schishol@nortel.com>]

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. Is that what people want to do.

And did people only want this object present when replay is supported on
that stream?

Sharon 

-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] 
Sent: Tuesday, August 28, 2007 2:50 PM
To: Chisholm, Sharon (CAR:ZZ00)
Cc: ietf@andybierman.com; netconf@ops.ietf.org
Subject: Re: replayLogStartTime

"Sharon Chisholm" <schishol@nortel.com> wrote:
> Hi
> 
> This timestamp helps differentiate the cases that there are no logs in

> the log for a particular time period and there were no logs generated 
> for that period. The replayed events start at 2pm, is that because the

> log start them or there were no events between 1 and 2, for example.
> 
> We have seen two designs of this object
> 	- present only when replay is supported
> 	- always present, but with a particular value when replay isn't 
> supported
> 
> Back when we could replay the future, the latter was the better option

> since it was possible to just return 'now' as the value while replay 
> is supported to only support future replays.
> 
> Now, I could go either ways. I know that in the past not all SNMP 
> tools faired well with holes. I expect XML tools to fair better. The 
> important thing is to be clear in whichever we choose.

And the current text isn't very clear, since it says

  The timestamp of the earliest available notification in the log

so what happens if there is no such notification at all?


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