[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

Attn WG:

Are there any objections to adding 'eventTime' to the notification
message, as described by Martin?

Andy


Andy Bierman <ietf@andybierman.com> wrote:

Martin Bjorklund wrote:

I think that in order to make replay interopable, we need to add the
eventTime to the notifications.  Here are two small modifications to
the XSD that will allow this:

As an attribute:

  <xs:complexType name="NotificationContentType">
    <xs:attribute name="eventTime" type="xs:dateTime" use="required"/>
  </xs:complexType>

or as an element:

  <xs:complexType name="NotificationContentType">
    <xs:sequence>
      <xs:element name="eventTime" type="xs:dateTime"/>
    </xs:sequence>
  </xs:complexType>


Which namespace would the 'eventTime' element be defined in?
Wouldn't it be different for every <fooEvent> element definition?


No.


If it was an attribute in the <notification> element,
it would be in the same namespace as that element.


If it's defined the way I wrote above, the eventTime element is in
the same namespace as 'notification',
i.e. "urn:ietf:params:xml:ns:netmod:notification".  An example of an
notification on the wire:

  <ncn:notification xmlns:ncn="urn:ietf:params:xml:ns:netconf:notification:1.0">
    <linkUp xmlns="http://example.com/ns/interface";>
      <ncn:eventTime>2007-08-17T08:56:05</ncn:eventTime>
      <ifIndex>3</ifIndex>
    </linkUp>
  </ncn:notification>


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





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