Phil Shafer wrote:
Balazs Lengyel writes:I think Andy's special value NOW for stopTime is a good idea.IMHO it's generally better to make a new element than to overload an existing one. In JUNOS, we use the <recorded/> element to indicate that we match on only recorded messages, ending the RPC as soon as we see the end of recorded messages.
But our data model doesn't work that way (yet). This doesn't affect the startTime. Wouldn't the <recorded/> flag match everything in the notification log? What if the <create-subscription> RPC used a 'choice' instead of a 'union' for this parameter? A choice of <now/> or <stopTime> can be used. If the <now/> choice is used, the agent will generate the <stopTime> from the current system time. We ruled that the <recorded/> element was part of the notification data model, just like <eventClass>.
Thanks, Phil
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/>