Community strings/IP Addr

David Arneson <arneson@ctron.com> Tue, 21 July 1992 14:08 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA07525; Tue, 21 Jul 92 10:08:00 -0400
Received: from nic.near.net by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA07515; Tue, 21 Jul 92 10:07:56 -0400
Received: from [134.141.2.2] by nic.near.net id aa21526; 21 Jul 92 10:07 EDT
Received: from cardinals.ctron by ctron.com (4.1/SMI-4.1) id AA04831; Tue, 21 Jul 92 10:04:38 EDT
Received: from rockies.ctron by cardinals.ctron (4.1/SMI-4.1) id AA27411; Tue, 21 Jul 92 10:06:06 EDT
Date: Tue, 21 Jul 1992 10:06:06 -0400
From: David Arneson <arneson@ctron.com>
Message-Id: <9207211406.AA27411@cardinals.ctron>
To: chassismib@cs.utk.edu
Subject: Community strings/IP Addr


Since we are moving in the direction of party based SNMP and there will
be a limited number of implementations of the MIB using community
based SNMP.  I vote to remove the community string and the IP address
from the chasEntityTable as Keith suggested.


Any complaints/ comments from anybody else?

/David Arneson (arneson@ctron.com)