Hello, I proposed the simple rules: startTime in future -> error stopTime in future -> error stopTime =< StartTime -> error stopTime present and startTime absent -> error The startTime must be in the past or must be absent. The stopTime must be in the past, or just Now, or absent. I think Andy's special value NOW for stopTime is a good idea. Balazs Martin Bjorklund wrote:
Andy Bierman <ietf@andybierman.com> wrote:Balazs Lengyel wrote:Hello Andy,My mail was about replay in the future not interleaving. There I vote for "the client MUST NOT" support replay in the future.And yes interleaving is complicated.IMO, there is WG consensus that startTime in the future MUST be an error. The alternative is to rewrite major portions of the document to support a 'cron' like feature, added at the last minute.I don't know about WG consensus, but I think it's a good idea to forbid a startTime in the future, to make things simpler. /martin
-- Balazs Lengyel Ericsson Hungary Ltd. TSP System Manager ECN: 831 7320 Fax: +36 1 4377792 Tel: +36-1-437-7320 email: Balazs.Lengyel@ericsson.com -- 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/>