Re: [netconf] time to meet today after 5pm

[Patrick McManus <[e-mail]>]

On Thu, Apr 4, 2019 at 4:33 PM Martin Bjorklund <[e-mail]> wrote:

>
> I don't think this is correct.  In what way do you think RESTCONF
> tries to use HTTP as a stateful transport?
>
>
below


>
> > >> On Tue, Apr 2, 2019 at 6:44 PM Kent Watsen <[e-mail]>
>
> > >> Actually, "managing persistence" is exactly what we're trying to
> > >> achieve here.  Our show-stopping driving use-case regards RESTCONF
> > >> Call Home (RFC 8071) and, in particular, point "S7" on page 8 of that
> > >> document, without which a remote device may become a "brick" and
> > >> require a technician to perform on-site repair.
>

also, in an exchange that wasn't copied to the wg,:

> To give a concrete example, there may be a device, deployed behind a NAT,
requiring a persistent management connection to its controller
application.  Because the device is behind a NAT, it MUST initiate the
connection (the controller cannot) and, thus the device MUST ensure
aliveness of the connection to the controller (the controller *needs* the
device-initiated connection to be up in order to send commands to the
device).   In case the controller disappears, perhaps due to its
data-center being hit by a meteor, the device must promptly detect to loss
and initiate reconnection to another controller.



>