few quick comments on notification-07

[Andy Bierman <ietf@andybierman.com>]

Hi,

Reading quickly through the new draft, I noticed a few things:

1) the namedProfile has an element called stream and the create-subscription
  RPC has a parameter called stream (in addition to named-profile 
parameter).

  The stream element in the namedProfile does not have any meaning,
  according to the create-subscription text.  The stream parameter is used,
  and the stream element in the namedProfile is ignored.  What is the point
  of having the stream element in the namedProfile?

2) There is nothing in the XSD that would indicate to an XSD tool that
  the read-only timestamp in the namedProfile must not be sent as part
  of the <edit-config> to configure a named profile.  I don't think
  this object should be in the data model, but if others think this
  is important, then I guess it will stay.  The value of this object
  is not explained anywhere -- it is just assumed that read-only
  timestamps should be mixed with config data without even mentioning 
it at all.

3) The replayComplete notification contains an eventClass element.
  The WG agreed that this notification will not have any content.
  This element must be removed.

4) The XSD for the replayCompleteNotificationType and the notification
  element are wrong.  The schema in the draft does not
  represent the normative text in the rest of the draft.

  The following notifications are valid, but this is not what the XSD 
allows:

   <notification>
     <replayComplete/>
   </notification>

   <notification>
    <blah xmlns="example.com"/>
   </notification>

I believe the XSD actually described the following XML:

  <replayComplete>
    <data/>
    <eventClass>blah</eventClass>
  </replayComplete>

which is completely wrong.

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