Re: [Netconf] netconf call home connection type

[Juergen Schoenwaelder <[e-mail]>]

On Tue, Aug 28, 2018 at 02:16:44AM +0000, Kent Watsen wrote:
> 
> Having an "on-demand" connection-type seems counter intuitive, as it is
> providing configuration for a connection that is driven by some external
> function, that may or may not be configuration.
>

LMAP would likely call home on demand as well, i.e., triggered by
other stuff going on in an LMAP agent. Do we really want an
augmentation for all the different reasons why a device may want to
call home?

> I'm disturbed by the "on-demand" part of the periodic/scheduled 
> definition.  The original idea was that the "demand" part would be
> something like the need to push logs but, as per the YP discussion,
> there might be a whole other connection for that purpose.  In a
> multi-manager scenario, it makes sense to periodically call-home
> to the "provisioning" system while separately send logs on-demand
> to the "monitoring" system.  If a device had configuration for a
> periodic or scheduled (or even persistent), it still wouldn't know
> to use that connection for the logs; the "demand" part, which 
> seems rational to define, never materializes.

The demand part in the system you are describing is a call home
triggered by the event "I am running out of log buffer space" or "I
had a partial restart event" or "a hardware compomnent is dying" or
... There are probably a number of situations where a device may want
to call home out of schedule and I am not sure it is reasonable to
model them each one of them as augmentations.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>