Balazs Lengyel wrote:
Hello, A) yes B) yes C) no I proposed a set of simple rules.
A B C D
+----------+-----------+------------+-----------
Log opens at time (A)
First log entry at time (B)
Second log entry at time (C)
<create-subscription> at time (D)
The actual values of startTime and stopTime are just
filter parameters. Any startTime <= (B) will return
both logged entries. If the stopTime is any time > (C)
then both entries are returned -- even if it > (D).
My concern (also raised by Randy) is that the agent
and manager clock skew will make it difficult for the
manager to give a value <= (D).
Balazs
Andy
Andy Bierman wrote:Hi, I would like people to speak up about the startTime and/or stopTime parameters in the future issue. Do you favor: A) return an error if parameters are in the future B) return whatever the agent has in its reply log that matches the search criteria (at the time the request is made). Parameters only refer to the timestamps of entries in the log. C) treat as a request to start returning notifications some time in the future, according to the parameters. Parameters refer to the 'time window' that notification delivery is desired. 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/>
-- 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/>