SNMPv2c: Get real, get on with it
MCCORMACK_JOHN@tandem.com Sat, 04 November 1995 21:35 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13125; 4 Nov 95 16:35 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13121; 4 Nov 95 16:35 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa18018; 4 Nov 95 16:35 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13112; 4 Nov 95 16:35 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13108; 4 Nov 95 16:35 EST
Received: from comm.cpd.tandem.com by CNRI.Reston.VA.US id aa17970; 4 Nov 95 16:35 EST
Received: by gateway.cpd.tandem.com (4.13/4.5) id AA7481; 4 Nov 95 13:36:15 -0800
Date: Sat, 04 Nov 1995 12:11:00 -0800
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: MCCORMACK_JOHN@tandem.com
Message-Id: <199511041336.AA7481@gateway.cpd.tandem.com>
To: iesg@CNRI.Reston.VA.US, ietf@CNRI.Reston.VA.US, snmpv2@tis.com
Cc: kostick@qsun.ho.att.com
Subject: SNMPv2c: Get real, get on with it
As group manager for Tandem's distributed system management technologies I would like to voice our STRONG support for the SNMPv2c specifications. We consider several aspects of the SNMPv2c specifications to be defect corrections to the original SNMPv1 specifications and LONG overdue. Any viable commercial technology requires timely updates wrt defects and the length of time of this SNMPv2 debate has exceeded this window by more than 1 year. Do we need the new security features? Proabably, depending on how this can be made to work with our current server security system, DCE based security, SSL, etc. Do our customers require the fixes embodied in the SNMPv2c specifications? YES, and we must deliver this within the next year for SNMP technology to continue to be a viable open management strategy for us. Thank You John McCormack Group Manager Distributed Systems Management Tandem Computers, Inc.
- SNMPv2c: Get real, get on with it MCCORMACK_JOHN