FYI - New DHCP options RFC and Draft Standard status

Ralph Droms <droms@bucknell.edu> Tue, 08 April 1997 14:29 UTC

Received: from cnri by ietf.org id aa21048; 8 Apr 97 10:29 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa13290; 8 Apr 97 10:29 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA00731; Tue, 8 Apr 1997 10:12:45 -0400
Date: Tue, 08 Apr 1997 10:12:45 -0400
Message-Id: <v02130506af6ff5e78b16@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ralph Droms <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: FYI - New DHCP options RFC and Draft Standard status
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

A new Request for Comments is now available in online RFC libraries.


        RFC 2132:

        Title:      DHCP Options and BOOTP Vendor Extensions
        Author:     S. Alexander, R. Droms
        Date:       March 1997
        Mailbox:    sca@engr.sgi.com, droms@bucknell.edu
        Pages:      34
        Characters: 63670
        Updates/Obsoletes: 1533

        URL:        ftp://ds.internic.net/rfc/rfc2132.txt


The Dynamic Host Configuration Protocol (DHCP) provides a framework
for passing configuration information to hosts on a TCP/IP network.
Configuration parameters and other control information are carried in
tagged data items that are stored in the \'options' field of the DHCP
message.  The data items themselves are also called "options." This
document specifies the current set of DHCP options.  This document is
the product of the Dynamic Host Configuration Working Group of the
IETF.

This is now a Draft Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute

..