[dhcwg] I-D ACTION:draft-bakke-dhc-snmp-trap-00.txt

Internet-Drafts@ietf.org Thu, 12 September 2002 12:07 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20303 for <dhcwg-archive@odin.ietf.org>; Thu, 12 Sep 2002 08:07:16 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CC8SJ01268 for dhcwg-archive@odin.ietf.org; Thu, 12 Sep 2002 08:08:28 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CC8Sv01265 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 12 Sep 2002 08:08:28 -0400
Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20259 for <dhcwg-web-archive@ietf.org>; Thu, 12 Sep 2002 08:06:46 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CC0tv00411; Thu, 12 Sep 2002 08:00:55 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CBwEv32743 for <dhcwg@optimus.ietf.org>; Thu, 12 Sep 2002 07:58:14 -0400
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19749; Thu, 12 Sep 2002 07:56:30 -0400 (EDT)
Message-Id: <200209121156.HAA19749@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
CC: dhcwg@ietf.org, snmpv3@lists.tislabs.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 12 Sep 2002 07:56:30 -0400
Subject: [dhcwg] I-D ACTION: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>

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: DHCP Option for SNMP Notifications
	Author(s)	: M. Bakke
	Filename	: draft-bakke-dhc-snmp-trap-00.txt
	Pages		: 4
	Date		: 2002-9-11
The Dynamic Host Configuration Protocol [RFC1531] provides a method
for a host to retrieve common configuration parameters at boot time.
These include the host's IP address, default gateway, subnet mask,
DNS server, and other useful things.
When a host is booted from the network, it does not have access to
these configuration parameters from its local or network disk right
away; it relies instead on DHCP to provide them.  One such parameter
that is not yet provided is a list of IP hosts to which to send SNMP
notifications [RFC1448] during the boot process, particularly if the
boot fails.  As the host is already gleaning similar information from
DHCP, a new option to specify these SNMP 'trap' hosts appears to be
the simplest method to gain this information.  Hosts not booting from
the network benefit as well, since SNMP notification hosts can now be
configured centrally through DHCP.
This document describes a proposed DHCP option that specifies a list
of SNMP notification hosts to which SNMP notifications should be

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-bakke-dhc-snmp-trap-00.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-bakke-dhc-snmp-trap-00.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the