RFC 4076 on Renumbering Requirements for Stateless Dynamic HostConfiguration Protocol for IPv6 (DHCPv6)

rfc-editor@rfc-editor.org Mon, 23 May 2005 22:32 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTW-0007XB-QY; Mon, 23 May 2005 18:32:42 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTO-0007VJ-6i; Mon, 23 May 2005 18:32:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05723; Mon, 23 May 2005 18:32:31 -0400 (EDT)
From: rfc-editor@rfc-editor.org
Received: from council.ci.sugar-land.tx.us ([] helo=mail.ci.sugar-land.tx.us) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaLlR-0006Pm-74; Mon, 23 May 2005 18:51:13 -0400
Received: from svrpd14 ([]) by mail.ci.sugar-land.tx.us; Mon, 23 May 2005 17:31:42 -0500
MIME-Version: 1.0
Date: Mon, 23 May 2005 17:31:41 -0500
X-Priority: 3 (Normal)
To: ietf-announce@ietf.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-Mailer: GWAVA Archive Mailer
Content-Type: multipart/mixed; boundary="----=_NextPart_282_8243_584e4fe6.ca3ec44e_.MIX"
Message-ID: <CHILKAT-MID-af2ca4a9-7955-4f4d-b128-44eb1ffe58b1@svrpd14>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
Subject: RFC 4076 on Renumbering Requirements for Stateless Dynamic HostConfiguration Protocol for IPv6 (DHCPv6)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        RFC 4076

        Title:      Renumbering Requirements for Stateless
                    Dynamic Host Configuration Protocol for IPv6
        Author(s):  T. Chown, S. Venaas, A. Vijayabhaskar
        Status:     Informational
        Date:       May 2005
        Mailbox:    tjc@ecs.soton.ac.uk, venaas@uninett.no,
        Pages:      8
        Characters: 15745
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt

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

IPv6 hosts using Stateless Address Autoconfiguration are able to
configure their IPv6 address and default router
settings automatically.  However, further settings are not available.
If these hosts wish to configure their DNS, NTP, or other
specific settings automatically, the stateless variant of the Dynamic
Host Configuration Protocol for IPv6 (DHCPv6) could be used.  This 
combination of Stateless Address Autoconfiguration and stateless
DHCPv6 could be used quite commonly in IPv6 networks.  However, hosts
using this combination currently have no means by which to be
informed of changes in stateless DHCPv6 option settings; e.g., the
addition of a new NTP server address, a change in DNS search paths,
or full site renumbering.  This document is presented as a problem
statement from which a solution should be proposed in a subsequent

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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

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.

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.
IETF-Announce mailing list