Skip to content

Minutes 2016 05 17

Jump to bottom
ericvoit edited this page May 18, 2016 · 3 revisions
Meeting Materials Attending
PPT WebEx password: 3Exy9ejK Ambika Prasad Tripathy, Einar Nilsen-Nygaard, Alexander Clemm, Alberto Gonzalez Prieto, Andy Bierman, Sharon Chisholm, Eric Voit, Peipei Guo

Action Items

  • Agreement on Slides for Netconf Interim (see PPT above)

  • Names of Dynamic Subscription and Configured Subscription adopted.

  • YANG Model review

  • Periodic interval goes to seconds from timeticks. At this point dampening period stays as timeticks

  • Question: Can we get rid of subscription start/stop time for a subscription, and move an anchor time under periodic?

    • This will mean the start/stop times may have different meanings for different types of subscriptions/streams. This needs to be worked through as perhaps the start time does not have to be pre-loaded. There is also resistance to changing the definition for what is in RFC5277.

  • Add "GET": text to no-synch-on-start to show the information pushed initially is just like a GET

  • Are there modify parameters listed which realistically cannot be changed?

  • We need to ensure only those parameters which might be changed are included. More review needed here.

  • Do we need all the notifications? We need to keep an eye on over-complexity

  • QoS parameters.

    • Is there a layer violation here? Assertion: We need to ensure that the dscp, priority, and dependency parameters provide the needed hints to lower layer protocols. Also that providing these hints is typical networking behavior.

    • General discussion on the worth of standardize all these parameters which might not be needed by all transport implementations

    • FYI after the call: QoS/priority info can have relevance for replay even with NETCONF transport. For example, what happens if there is a lost connection? Which buffered information should go first?

  • Filtering rules discussed.

    • Alex to update the text within subtree-filter definition so that 6241 doesn't apply field filtering. Need the filters for Notification not for GET. Don't want to drop the whole notification if a filtering event is hit.

  • Completed first pass a YANG model review, except for Notifications.

Clone this wiki locally