Re: Notification #9: replay in the future consensus point

[Andy Bierman <ietf@andybierman.com>]

Martin Bjorklund wrote:
> Andy Bierman <ietf@andybierman.com> wrote:
> > Note that there is no standard for 'eventClass', 'eventSeverity',
> > or 'eventTime', and a vendor may choose to use XML attributes
> > or elements for these fields (if they exist at all).
>
> The entire replay feature relies on the presence of an eventTime (or
> similar).  If the manager can't figure out when the notifications were
> generated, he cannot set startTime and stopTime to get missing
> notifications.  IMO, it's a big mistake that this event time isn't
> standardized - it means that a manager, in order to use replay
> efficiently, has to know all datamodels of all notifications, and know
> where to find the non-standard event time in each one.

I agree.
It is a mistake to design the notification message assuming
these critical standard fields will be retro-fitted in
an inter-operable manner.

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