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

Mark Bakke <mbakke@cisco.com> Fri, 13 September 2002 20:32 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18031 for <dhcwg-archive@odin.ietf.org>; Fri, 13 Sep 2002 16:32:21 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8DKXcD15566 for dhcwg-archive@odin.ietf.org; Fri, 13 Sep 2002 16:33:38 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DKXcv15563 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 13 Sep 2002 16:33:38 -0400
Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18026 for <dhcwg-web-archive@ietf.org>; Fri, 13 Sep 2002 16:31:50 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DKOxv14512; Fri, 13 Sep 2002 16:24:59 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DKNev14458 for <dhcwg@optimus.ietf.org>; Fri, 13 Sep 2002 16:23:40 -0400
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17655 for <dhcwg@ietf.org>; Fri, 13 Sep 2002 16:21:52 -0400 (EDT)
Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com []) by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g8DKMwds006281; Fri, 13 Sep 2002 13:22:58 -0700 (PDT)
Received: from nisser.cisco.com (localhost []) by sj-msg-av-3.cisco.com (8.12.2/8.12.2) with ESMTP id g8DKMv27027862; Fri, 13 Sep 2002 13:22:57 -0700 (PDT)
Received: from cisco.com (mbakke-lnx.cisco.com []) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA25793; Fri, 13 Sep 2002 13:22:55 -0700 (PDT)
Message-ID: <3D824DA5.8039B55A@cisco.com>
Date: Fri, 13 Sep 2002 15:42:13 -0500
From: Mark Bakke <mbakke@cisco.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-3.uid32 i686)
X-Accept-Language: en, de
MIME-Version: 1.0
To: "Harrington, David" <dbh@enterasys.com>
CC: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
References: <6D745637A7E0F94DA070743C55CDA9BA0757E1@NHROCMBX1.ets.enterasys.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


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?


> "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
dhcwg mailing list