[dhcwg] Re: DHCP Option for SNMP Notifications

Mark Bakke <mbakke@cisco.com> Wed, 11 September 2002 21:49 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 RAA26216 for <dhcwg-archive@odin.ietf.org>; Wed, 11 Sep 2002 17:49:34 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8BLopN13497 for dhcwg-archive@odin.ietf.org; Wed, 11 Sep 2002 17:50:51 -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 g8BLopv13494 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 11 Sep 2002 17:50:51 -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 RAA26212 for <dhcwg-web-archive@ietf.org>; Wed, 11 Sep 2002 17:49:03 -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 g8BLm4v13397; Wed, 11 Sep 2002 17:48:04 -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 g8BLl9v13352 for <dhcwg@optimus.ietf.org>; Wed, 11 Sep 2002 17:47:09 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26088 for <dhcwg@ietf.org>; Wed, 11 Sep 2002 17:45:21 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g8BLkS3x022204; Wed, 11 Sep 2002 14:46:28 -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 g8BLkVh6016938; Wed, 11 Sep 2002 14:46:31 -0700 (PDT)
Received: from cisco.com (mbakke-lnx.cisco.com [64.101.211.87]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA27818; Wed, 11 Sep 2002 14:46:28 -0700 (PDT)
Message-ID: <3D7FBE44.487A0EDB@cisco.com>
Date: Wed, 11 Sep 2002 17:05:56 -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: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: dhcwg@ietf.org, mibs@ops.ietf.org
References: <A451D5E6F15FD211BABC0008C7FAD7BC0EE4558C@nl0006exch003u.nl.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Re: DHCP Option for SNMP Notifications
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

I had figured IPv6 addresses would be handled along with DHCPv6,
but that's mainly because we worried about v6 a whole lot yet.
I also noticed that all of the previously-specified "list of
IP address" options only mentioned v4.  Is there a standard method
used in DHCP to specify whether an address that follows is an
IPv4 or v6 address?

I hadn't given security any thought.

I assume that I need to look at the notification MIB module
in RFC2573.  Where should I look for these in the others?

Anyway, I'll be out for a few days, and will try to read the
four RFCs you mentioned in the meantime.  I'd prefer to do
this the right way, rather than limit it to v1.

Thanks,

Mark

"Wijnen, Bert (Bert)" wrote:
> 
> Seems pretty IPv4 specific. Can there be IPv6 addresses?
> 
> How ould the agent know security parameters and SNMP version
> to use and such?
> 
> I assume you would want the paramters to fit into the
> SNMP architecure (as per RFC2571), and the trap (or
> better) notification destinations (and other parameters)
> to be mappable inot the MIBs in RFC2573, 2574 and 2575?
> 
> Thanks,
> Bert
> 
> > -----Original Message-----
> > From: Mark Bakke [mailto:mbakke@cisco.com]
> > Sent: woensdag 11 september 2002 18:23
> > To: dhcwg@ietf.org; mibs@ops.ietf.org
> > Subject: DHCP Option for SNMP Notifications
> >
> >
> > Hi-
> >
> > I needed a method to configure a list of SNMP notification (AKA trap)
> > hosts for use by diskless workstations booting from a network device.
> > Since none of the usual SNMP configuration information is available
> > at this time, I would like to use a DHCP option to provide a list of
> > IP addresses to which to send notifications when, for
> > instance, booting
> > from a network device fails for some reason.  This could also be used
> > to centrally configure the list of SNMP notification hosts,
> > rather than
> > setting them individually on each machine.
> >
> > Anyway, I've submitted a short draft describing the proposed option
> > as draft-bakke-dhc-snmp-trap-00.txt.  I'll forward the message to
> > these two groups when the draft is published.  In the mean time, it
> > is available at:
> >
> > ftp://ftpeng.cisco.com/mbakke/ips/dhcp/draft-bakke-dhc-snmp-tr
> ap-00.txt
> 
> I'm guessing that these two mailing lists (dhcwg and mibs) are the
> correct places to discuss this (please let me know if there's a more
> appropriate list).
> 
> Regards,
> 
> 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