[dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt

"Harrington, David" <dbh@enterasys.com> Tue, 17 September 2002 22:18 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02475 for <dhcwg-archive@odin.ietf.org>; Tue, 17 Sep 2002 18:18:02 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8HMJPN13476 for dhcwg-archive@odin.ietf.org; Tue, 17 Sep 2002 18:19:25 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HMJPv13473 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 17 Sep 2002 18:19:25 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02470 for <dhcwg-web-archive@ietf.org>; Tue, 17 Sep 2002 18:17:32 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HMBAv13241; Tue, 17 Sep 2002 18:11:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8G3Gxv27306 for <dhcwg@optimus.ietf.org>; Sun, 15 Sep 2002 23:16:59 -0400
Received: from ctron-dnm.enterasys.com (firewall-user@[12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15472 for <dhcwg@ietf.org>; Sun, 15 Sep 2002 23:15:06 -0400 (EDT)
Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id XAA09837; Sun, 15 Sep 2002 23:24:45 -0400 (EDT)
Received: from unknown(134.141.77.96) by ctron-dnm.enterasys.com via smap (4.1) id xma009835; Sun, 15 Sep 02 23:24:04 -0400
Received: by cnc-exc1.enterasys.com with Internet Mail Service (5.5.2653.19) id <S4ZYLW70>; Sun, 15 Sep 2002 23:07:36 -0400
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA0757E3@NHROCMBX1.ets.enterasys.com>
From: "Harrington, David" <dbh@enterasys.com>
To: "'Mark Bakke'" <mbakke@cisco.com>
Cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, "snmpv3@lists. tislabs. com (E-mail)" <snmpv3@lists.tislabs.com>
Date: Sun, 15 Sep 2002 23:12:26 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C25D2E.E1E1D826"
Subject: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Hi Mark,

The bulk of the current usage of SNMP is for monitoring, not configuring.
There are few mib objects that would require dynamic configuration. However,
it could be a very interesting discussion to start with the SNMP community
via the SNMPv3 list.

We're trying to wrap up and close the SNMPv3 WG. I think the discussion
would need to move to a different forum, but which forum depends to a large
degree on nature of the proposals that might come out of the discussion.

dbh

> -----Original Message-----
> From: Mark Bakke [mailto:mbakke@cisco.com]
> Sent: Friday, September 13, 2002 4:42 PM
> To: Harrington, David
> Cc: 'dhcwg@ietf.org'
> Subject: Re: draft-bakke-dhc-snmp-trap-00.txt
> 
> 
> David-
> 
> Thanks for the advice.  I just had a chance to go over 2571, 
> 73, and 74, and
> I think I can take a better shot at this (at least the 
> notification part).  I'll
> post to both dhcwg and the snmpv3 lists.
> 
> As far as the scope for this, I was initially just setting out to do
> enough for notifications.  Do you think that there is interest in
> configuring other agent parameters as well?
> 
> -
> Mark
> 
> > "Harrington, David" wrote:
> > 
> > Hi Mark,
> > 
> > RFC1448 is a remnant of the obsolete SNMPv2 specs. Nobody 
> supports the old RFC144x specifications.
> > You should be using SNMPv3 specifications. The most current 
> RFCs are 2570-2580, and approved
> > updates are in the editor's RFC queue.
> > 
> > RFC2573 defines a number of mibs that can be configured to 
> identify notification targets. If you
> > examine those mibs, you will find that there is more 
> information needed than just an address.
> > Therefore, your proposed message would need to contain more 
> to centrally configure SNMP targets
> > properly.
> > 
> > dbh
> > 
> > David Harrington
> > co-chair SNMPv2 WG
> > Network Management Architect
> > Office of the CTO
> > Enterasys Networks
> > 
> 
> -- 
> Mark A. Bakke
> Cisco Systems
> mbakke@cisco.com
> 763.398.1054
>