Re: Underspecified CallHome

[Phil Shafer <phil@juniper.net>]

Andy Bierman writes:
>   - data model to NV-configure an agent to call home

The config needed to get a device to call home is might
well be device specific.

>   - callhome agent protocol procedures
>   - callhome manager protocol procedures

The big job here is getting the protocol mappings for reverse
direction connections, and having a mechanism to uniquely identify
the device to the app.

BEEP handles the device-initiated connection easily, and one can
use 'sshd -i' on the device side to pass a device-initiated connection
into the ssh daemon code, allowing us to preserve the existing
client/server relationship in netconf.  I'm clueless about how soap
would handle this.

As far as device identification, the device's ssh host-key (or its
fingerprint?) should suffice.

>   - agent needs to convey reason for connect when calling home
>     (operations or notifications or ?)

For this, I was imagining a specific log, where the newly connected
manager could do a simple RPC saying "Who dares to disturb the great
and powerful Oz?"  The reply would be a list of recent reasons the
device has called home, which the manager can inspect to find both
the current reason (the last one on the list) and the past reasons
(to see if any were lost).

Thanks,
 Phil

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>