[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 4477 on Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues
A new Request for Comments is now available in online RFC libraries.
RFC 4477
Title: Dynamic Host Configuration Protocol (DHCP):
IPv4 and IPv6 Dual-Stack Issues
Author: T. Chown, S. Venaas,
C. Strauf
Status: Informational
Date: May 2006
Mailbox: tjc at ecs.soton.ac.uk, venaas at uninett.no,
strauf at rz.tu-clausthal.de
Pages: 14
Characters: 30440
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dhc-dual-stack-04.txt
URL: http://www.rfc-editor.org/rfc/rfc4477.txt
A node may have support for communications using IPv4 and/or IPv6
protocols. Such a node may wish to obtain IPv4 and/or IPv6
configuration settings via the Dynamic Host Configuration Protocol
(DHCP). The original version of DHCP (RFC 2131) designed for IPv4
has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This
document describes issues identified with dual IP version DHCP
interactions, the most important aspect of which is how to handle
potential problems in clients processing configuration information
received from both DHCPv4 and DHCPv6 servers. The document makes a
recommendation on the general strategy on how best to handle such
issues and identifies future work to be undertaken. This memo provides information for the Internet community.
This document is a product of the Dynamic Host Configuration
Working Group of the IETF.
INFORMATIONAL: 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFCFrom ietf-announce-bounces at ietf.org Fri May 05 20:45:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FcArK-0006DX-6d; Fri, 05 May 2006 20:41:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FcArI-0006DM-Tv; Fri, 05 May 2006 20:41:20 -0400
Received: from nit.isi.edu ([128.9.160.116])
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1FcArG-0001Hq-H0; Fri, 05 May 2006 20:41:20 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k460fHxx032502;
Fri, 5 May 2006 17:41:17 -0700
Received: (from apache at localhost)
by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k460fHEN032501;
Fri, 5 May 2006 17:41:17 -0700
Date: Fri, 5 May 2006 17:41:17 -0700
Message-Id: <200605060041.k460fHEN032501 at nit.isi.edu>
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
From: rfc-editor at rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: dhcwg at ietf.org, rfc-editor at rfc-editor.org
Subject: RFC 4477 on Dynamic Host Configuration Protocol (DHCP): IPv4 and
IPv6 Dual-Stack Issues
X-BeenThere: ietf-announce at 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 at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request at ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces at ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4477
Title: Dynamic Host Configuration Protocol (DHCP):
IPv4 and IPv6 Dual-Stack Issues
Author: T. Chown, S. Venaas,
C. Strauf
Status: Informational
Date: May 2006
Mailbox: tjc at ecs.soton.ac.uk, venaas at uninett.no,
strauf at rz.tu-clausthal.de
Pages: 14
Characters: 30440
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dhc-dual-stack-04.txt
URL: http://www.rfc-editor.org/rfc/rfc4477.txt
A node may have support for communications using IPv4 and/or IPv6
protocols. Such a node may wish to obtain IPv4 and/or IPv6
configuration settings via the Dynamic Host Configuration Protocol
(DHCP). The original version of DHCP (RFC 2131) designed for IPv4
has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This
document describes issues identified with dual IP version DHCP
interactions, the most important aspect of which is how to handle
potential problems in clients processing configuration information
received from both DHCPv4 and DHCPv6 servers. The document makes a
recommendation on the general strategy on how best to handle such
issues and identifies future work to be undertaken. This memo provides information for the Internet community.
This document is a product of the Dynamic Host Configuration
Working Group of the IETF.
INFORMATIONAL: 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at 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 at 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 at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce