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

Mark Bakke <mbakke@cisco.com> Fri, 20 September 2002 18:21 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 OAA03183 for <dhcwg-archive@odin.ietf.org>; Fri, 20 Sep 2002 14:21:46 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8KIN9E15569 for dhcwg-archive@odin.ietf.org; Fri, 20 Sep 2002 14:23:09 -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 g8KIN9v15566 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 20 Sep 2002 14:23:09 -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 OAA03173 for <dhcwg-web-archive@ietf.org>; Fri, 20 Sep 2002 14:21:15 -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 g8KIGSv15295; Fri, 20 Sep 2002 14:16:29 -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 g8KICev15186 for <dhcwg@optimus.ietf.org>; Fri, 20 Sep 2002 14:12:40 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02765 for <dhcwg@ietf.org>; Fri, 20 Sep 2002 14:10:47 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151]) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8KIBr1X017931; Fri, 20 Sep 2002 11:11:53 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1]) by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8KIBqed006409; Fri, 20 Sep 2002 11:11:53 -0700 (PDT)
Received: from cisco.com (mbakke-lnx2.cisco.com [64.101.211.59]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA25408; Fri, 20 Sep 2002 11:11:46 -0700 (PDT)
Message-ID: <3D8B64E2.78634E28@cisco.com>
Date: Fri, 20 Sep 2002 13:11:46 -0500
From: Mark Bakke <mbakke@cisco.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-34.cisco.2 i686)
X-Accept-Language: en, de
MIME-Version: 1.0
To: "Harrington, David" <dbh@enterasys.com>
CC: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, "snmpv3@lists. tislabs. com (E-mail)" <snmpv3@lists.tislabs.com>
Subject: Re: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt
References: <6D745637A7E0F94DA070743C55CDA9BA0757E3@NHROCMBX1.ets.enterasys.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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

David-

I'm copying the mibs@ops.ietf.org list on this as well; is it
sufficient?  Should I not send this to snmpv3?

Thanks,

Mark

> "Harrington, David" wrote:
> 
> 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
> >

-- 
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg