RFC 2937 on The Name Service Search Option for DHCP
RFC Editor <rfc-ed@ISI.EDU> Wed, 04 October 2000 22:44 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03315; Wed, 4 Oct 2000 18:44:26 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA17553 for ietf-123-outbound.10@ietf.org; Wed, 4 Oct 2000 18:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA17531 for <all-ietf@loki.ietf.org>; Wed, 4 Oct 2000 18:32:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03198 for <all-ietf@ietf.org>; Wed, 4 Oct 2000 18:32:01 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA13766; Wed, 4 Oct 2000 15:32:00 -0700 (PDT)
Message-Id: <200010042232.PAA13766@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2937 on The Name Service Search Option for DHCP
Cc: rfc-ed@ISI.EDU, dhcp-v4@bucknell.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 04 Oct 2000 15:32:00 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2937 Title: The Name Service Search Option for DHCP Author(s): C. Smith Status: Standards Track Date: September 2000 Mailbox: cs@Eng.Sun.COM Pages: 5 Characters: 8368 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-nsso-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2937.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 order in which name services should be consulted when resolving hostnames and other information. This document is a product of the Dynamic Host Configuration Working Group of the IETF. 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.