Re: [OPS-AREA] [OPS-DIR] SNMP notification configuration

["David Harrington" <ietfdbh at comcast.net>]

As an SNMP "old dog", I have been indoctrinated with many assumptions
that were true in the 80s, but might be less true now. Startup keeps
getting smaller as a percentage of overall uptime; notifications may
not be as desirable during startup as they once were; UDP may not be
any more reliable than TCP for getting through broken networks, and so
on.

The ISMS WG is trying to make sure we don't change the basic
assumptions of how SNMP works, but we occasionally need to question
whether certain old assumptions are still valid.

dbh

> -----Original Message-----
> From: Phil Shafer [mailto:phil at juniper.net] 
> Sent: Tuesday, June 03, 2008 12:20 PM
> To: David Harrington
> Cc: ops-dir at ietf.org; 'OPS Area'; isms at ietf.org
> Subject: Re: [OPS-DIR] SNMP notification configuration 
> 
> "David Harrington" writes:
> >SNMP can send notifications when an event happens, without having
to
> >wait for a manager to initiate a connection first. This distinction
> >can be important, especially during startup.
> 
> Sure, but in practice, startup is a painful time to send 
> notifications,
> since the delays of interface bringup and learning routes may mean
> your manager is unreachable.  Waiting for a connection turns out
> to be more useful than firing off packets into nowhere.
> 
> Thanks,
>  Phil
> 

_______________________________________________
OPS-AREA mailing list
OPS-AREA at ietf.org
https://www.ietf.org/mailman/listinfo/ops-area