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

On Fri, Sep 14, 2018 at 12:14 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Fri, Sep 14, 2018 at 09:11:20AM +0200, Martin Bjorklund wrote:
> > >
> > > > However, I think that for all RPC-based transport-protocols
> (currently
> > > > NETCONF and RESTCONF) it makes sense to have a common way to get the
> > > > notifications to be sent.
> > >
> > > Perhaps something will be needed for NETCONF.  But for configured
> > > RESTCONF subscriptions, RESTCONF-Notif has been assuming that RESTCONF
> > > not be used.  Instead raw HTTP2 with the Publisher being the HTTP
> > > client and the receiver the HTTP server seems cleaner.
> >
> > This has been pointed out before - the restconf-notif draft should
> > define *RESTCONF* mechanisms for subscribed notifications.
> >
> > If you want to define a new "notif-only" protocol that uses HTTP/2,
> > that should be done in a separate document.
> >
>
> +1
>

So how should this be fixed?
It seems this draft could be renamed (e.g., s/RESTCONF/HTTP2/) since it
does not use RESTCONF in any way.  I don't think RESTCONF notifications
are used very much, but I don't see why the same SSE delivery of the
<notification> element
would not work (e.g., different resource to GET for establish-subscription
parameters)

The WG seems to refactor drafts a lot, only to end up with even more
unfinished work
than before.  We should learn to drop work that is not backed with lots of
active support
and reviews.

> /js
>

Andy

>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>