Re: [Netconf] Anyone want just Configured Subscriptions?

[Andy Bierman <[e-mail]>]

On Tue, Jul 10, 2018 at 1:59 PM, Juergen Schoenwaelder <
[e-mail]> wrote:

> On Tue, Jul 10, 2018 at 08:37:30PM +0000, Kent Watsen wrote:
> >
> >
> > > So in short, after RFC 8071 call home, you get NC/RC client and server
> > > starting with a <hello> exchange. Ideally, the client would indicate
> > > its readiness to receive unsolicited notifications before you push
> > > notifications to the client (and the notification sender may even be
> > > interested to know that it is sending notifications to a remote system
> > > that does not just drop them). So either the clients invokes an RPC to
> > > start the notification flow or, if you want to optimize one round
> > > trip, the client includes a special
> > >
> > >  :willing-to-receive-unsolicited-notifications
> > >
> > > capability in the <hello> exchange.
> >
> > I agree that a client-advertised capability would be goodness here, but
> > it only works for NC-clients, there is no corollary for RC-clients.
> >
> > Maybe clients should send a "willing-to-receive-
> unsolicited-notifications"
> > RPC instead?
>
> RFC 8040 (RESTCONF) uses SSE and the client has to fetch an event
> stream resource in order to receive events (section 6.3). This is not
> a big surprise since HTTP 1/1 is purely client driven. This in fact
> implies that the client knows the event stream resource.
>
>
SSE should be an available option for configured notifications.
There could be a pre-determined URL for the client to GET
like GET /restconf/SSE/<subscription-id>


/js
>

Andy



>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>
>
> _______________________________________________
> Netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf
>