Re: [Netconf] activate-configured-subecription - WGLC subscribed-notifications-16

[Douglas Hubler <[e-mail]>]

On Tue, Sep 18, 2018 at 3:40 PM Martin Bjorklund <[e-mail]> wrote:

> So it seems you support my point to make this draft use SSE.  Then if
> you use HTTP/2 you (the client) can simply create one HTTP/2 stream per
> notification stream.  This just falls out for free with HTTP/2.
>

yes, with caveat that I haven't attempted actual implementation yet.


>
> > I don't understand the details surrounding using an RPC to make a dynamic
> > subscription.  Unless it's optional, then I can start to understand.
>
> The client would POST to the "rpc" establish-subscripion, and in the
> reply to the POST is a "location" leaf (*) that contains a URI.  The
> client then GET this URI; this is the SSE event stream.
>

I see.  But if a client reads the YANG as

 module my-module {
    ...
    notification my-event {
    }
}

and client knew base stream URI was:

   /restconf/my-streams

Couldn't the client then deduce SSE URL as:

 GET  /restconf/my-streams/my-module:my-event?...

Thereby saving a trip to server?  Would it be wrong for a client to make
any assumptions?  I realize this ASSUMEs a transport protocol, but
could/would there be a one-time, capability check the client could make to
test for available transports?

I really appreciate your time explaining, I have been following the emails
best I could but I think some basic things are still eluding me.