Re: [Netconf] Draft Charter Proposal for NETCONF WG

[Juergen Schoenwaelder <[e-mail]>]

On Mon, Mar 20, 2017 at 05:32:41PM +0100, Mehmet Ersue wrote:
>    - Definition of notifications sent over NETCONF and how YANG 
>      notifications are encoded in XML and JSON. Include considerations 
>      for parallel support / implementation compatibility with RFC-5277.
> 
>    - Definition of notifications sent over RESTCONF and HTTP2 and how 
>      YANG notifications are encoded in XML and JSON. Include specifics 
>      of call-home and heartbeat for subscriptions.

I believe we do have specifications how YANG defined notifications are
encoded in XML and JSON. Do we plan to redo this? I do not think so.
Perhaps it needs to be state more clearly what the scope of this work
is and what it is not.

And what is HTTP2 doing here? I assume this is about replacing the
Server-Sent Events (SSE) mechanism with HTTP/2 push. I checked RFC
8040 and it specifically says:

   This document defines a protocol based on HTTP [RFC7230] called
   "RESTCONF", for configuring data defined in YANG version 1 [RFC6020]
   or YANG version 1.1 [RFC7950], using the datastore concepts defined
   in the Network Configuration Protocol (NETCONF) [RFC6241].

Note that RFC 7230 is HTTP/1.1. I think the WG really needs to write a
document that defines RESTCONF over HTTP/2 and not just notifications
over HTTP/2. Such a document may very well say that almost nothing
needs changes to run over HTTP/2 except the notification delivery
being done differently. But I think the scope should be RESTCONF over
HTTP2 and not RESTCONF notifications over HTTP2.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>