[rfc-dist] RFC 3646 on DNS Configuration options for Dynamic Host
Tue, 09 Dec 2003 12:05:20 -0800
A new Request for Comments is now available in online RFC libraries.
Title: DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)
Author(s): R. Droms, Ed.
Status: Standards Track
Date: December 2003
I-D Tag: draft-ietf-dhc-dhcpv6-opt-dnsconfig-04.txt
This document describes Dynamic Host Configuration Protocol for IPv6
(DHCPv6) options for passing a list of available DNS recursive name
servers and a domain search list to a client.
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:
Subject: getting 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
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.
Content-Type: Multipart/Alternative; Boundary="OtherAccess"