notification-07 issue list

[Andy Bierman <ietf@andybierman.com>]

Hi,

We need to finish up this document by the end of the Chicago IETF.
This is a first draft issue list, based on mailing list comments
so far.  It is getting increasingly difficult to get people to
review successive versions of the draft.  It seems that each time,
not all approved changes are made, and one or two new things show
up that were never even discussed by the WG.  This has the combined
effect of discouraging people from reviewing new versions,
and keeps generating new issues to resolve.

Therefore, we need to focus on creating a final edit list and
making sure that it is applied exactly as approved by the WG,
so we can finally forward the draft to the IESG.

The issue list below highlights the recent comments made on notification-07:

http://ops.ietf.org/lists/netconf/netconf.2007/msg00136.html

http://ops.ietf.org/lists/netconf/netconf.2007/msg00137.html

http://ops.ietf.org/lists/netconf/netconf.2007/msg00148.html

http://ops.ietf.org/lists/netconf/netconf.2007/msg00153.html

http://ops.ietf.org/lists/netconf/netconf.2007/msg00196.html

---------------------------------------------

1) named profiles

 a) <stream> element in named profile is not used for anything

 b) need <key> (==<name>) to properly support edit-config operation

 c) edit-config not applicable to contents of <filter> because
    its base type is 'any'

 d) filter element is optional. Not clear what use case a named
    profile without a filter supports.

2) <eventStreams> data model element

a) definition is not extensible, such that XSD cannot be properly used
   to specify extensions and restrictions

b) new element named 'replayLogStartTime' has been added to the XSD.
   This is not mentioned anywhere in the draft.  The WG never discussed
   adding this element.

3) XSD and Xpath corrections

  [see message list for details]

4) XSD template for <notification> wrapper

  a) current definition is not what the WG agreed to, and does not
     even support the replayComplete notification correctly

  b) definition is not extensible, such that XSD cannot be properly used
     to specify extensions and restrictions

5) XML representation of the <replayComplete> notification

  a) new element named <eventClass> has been added to the XSD.
     The WG never discussed adding this element.

          <xs:element name="eventClass"/>

     There is no text in the document about this element, including
     its actual XML type definition, purpose, or value for the 
<replayComplete>
     notification.

    
6) SSH Transport Support Text

  a) need separate document to support top-level <notification> element
     explicitly by NETCONF over SSH


------------------------------------------------------------------


Please try to use a separate email for each existing topic or new topic,
instead of responding to this thread, if you want to comment on
any of the open issues.

We would like to finish up as much as possible on the mailing list,
and not defer these decisions until the meeting in Chicago.

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