RFC 3397 on Dynamic Host Configuration Protocol (DHCP) Domain Search Option

rfc-editor@rfc-editor.org Sat, 09 November 2002 03:34 UTC

Message-Id: <200211082349.gA8NnmD23381@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3397 on Dynamic Host Configuration Protocol (DHCP) Domain Search Option
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 08 Nov 2002 15:49:48 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3397
                         
        Title:      Dynamic Host Configuration Protocol (DHCP) Domain
                    Search Option
        Author(s):  B. Aboba, S. Cheshire
        Status:     Standards Track
        Date:       November 2002
        Mailbox:    bernarda@microsoft.com, rfc@stuartcheshire.org
        Pages:      8
        Characters: 15446
        Updates/Obsoletes/SeeAlso:    None
                         
        I-D Tag:    draft-aboba-dhc-domsearch-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3397.txt


This document defines a new Dynamic Host Configuration Protocol (DHCP)
option which is passed from the DHCP Server to the DHCP Client to
specify the domain search list used when resolving hostnames using
DNS.

This is now a Proposed 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3397.txt"><ftp://ftp.isi.edu/in-notes/rfc3397.txt>

RFC 3397 on Dynamic Host Configuration Protocol (… rfc-editor