IPP Mail Archive: Re: SENSE> Re: IPP> Re: SNMPv3 unsuited for IPP/JMP Notifica

IPP Mail Archive: Re: SENSE> Re: IPP> Re: SNMPv3 unsuited for IPP/JMP Notifica

Re: SENSE> Re: IPP> Re: SNMPv3 unsuited for IPP/JMP Notifica

Harry Lewis (harryl@us.ibm.com)
Mon, 23 Mar 1998 13:54:01 -0500

I response to Ira' comment...

> IEM> But, your examples are all of infrastructure (intermediate-syste=
ms),
> not printers, scanners, and other end-systems. Managing a hub or rou=
ter
> has essentially nothing in common with managing end-systems, except t=
hat
> they use a common protocol - SNMPv1, NOT SNMPv3, which is unlikely to=
be
> widely deployed for at least the next three years - look at the deplo=
yment

We (PWG) crossed the "using SNMP to manage printers" question long ago.=
Some
people have never been comfortable with it but no one can deny we did. =
To some
degree, one can argue that every network element is part of it's
infrastructure. That's pretty much how I believe we got where we are. I=
'm not
saying it's right or wrong. I've just been trying to make good use of i=
t rather
than judge it or wish for something different.

Also, I don't believe we can predict SNMPv3 rollout based on V2 lag. SN=
MPv2 had
a goory history - so bad that many chose not to implement. I view SNMPv=
3 as the
answer to the v2 problem, not a repeat of it.

Harry Lewis - IBM Printing Systems
=