Subject: [Netconf] Key Issues: draft-voit-netconf-restconf-notif

From: "Eric Voit (evoit)" <[email-masked]>
Date: Thu, 23 Jun 2016 21:44:27 +0000

There are four NETCONF subscription drafts recently posted.  The scope for each draft<http://www.voit.org/IETF/Subscriptions-NETCONF-Interim-18May2016.ppt> was proposed during the May NETCONF interim.  To get people ready to consider upcoming draft adoption requests, we are going to highlight some issues now being worked.   This email describes some recent thinking on draft-voit-netconf-restconf-notif<https://datatracker.ietf.org/doc/draft-voit-netconf-restconf-notif/>.

draft-voit-netconf-restconf-notif<https://datatracker.ietf.org/doc/draft-voit-netconf-restconf-notif/>  provides a specification for transporting Subscriptions and Event notifications Restconf and HTTP.  Three top issues currently being discussed are:

*        We plan on using Event notifications from RESTCONF as a normative reference.   Does the draft include all the augmentations needed?

*        HTTP native transport option doesn't currently use Server Sent Events (SSE).  Can we adopt SSE?

*        Do we include support for 3rd party signaled subscriptions over HTTP native transport?

If you read this draft and have questions on these or other issues, please chime in...

Eric Voit
(on behalf of the authors and the NETCONF members attending the weekly calls)