draft-ietf-dhc-dhcpv4-over-ipv6-05.txt   draft-ietf-dhc-dhcpv4-over-ipv6-06.txt 
Network Working Group Y. Cui Network Working Group Y. Cui
Internet-Draft P. Wu Internet-Draft P. Wu
Intended status: Standards Track J. Wu Intended status: Informational J. Wu
Expires: March 20, 2013 Tsinghua University Expires: September 21, 2013 Tsinghua University
T. Lemon T. Lemon
Nominum, Inc. Nominum, Inc.
September 16, 2012 March 20, 2013
DHCPv4 over IPv6 Transport DHCPv4 over IPv6 Transport
draft-ietf-dhc-dhcpv4-over-ipv6-05 draft-ietf-dhc-dhcpv4-over-ipv6-06
Abstract Abstract
In IPv6 networks, there remains a need to provide IPv4 service for In IPv6 networks, there remains a need to provide IPv4 service for
some residual devices. This document describes a mechanism for some residual devices. This document describes a mechanism for
allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6 allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6
transport. It is done by putting a special relay agent function transport. It is done by putting a special relay agent function
(Client Relay Agent) on the client side, as well as extending the (Client Relay Agent) on the client side, as well as extending the
behavior of the server; in the case where DHCP server only supports behavior of the server; in the case where DHCP server only supports
IPv4 transport, a relay agent is extended to support IPv6 transport IPv4 transport, a relay agent is extended to support IPv6 transport
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 20, 2013. This Internet-Draft will expire on September 21, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 37 skipping to change at page 3, line 37
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Terminology 3. Terminology
This document makes use of the following terms: This document makes use of the following terms:
o DHCPv4: IPv4 Dynamic Host Configuration Protocol [RFC2131]. o DHCPv4: IPv4 Dynamic Host Configuration Protocol [RFC2131].
o Client Relay Agent(CRA): a special DHCPv4 Relay Agent which relays o Client Relay Agent(CRA): a special DHCPv4 Relay Agent which relays
between DHCPv4 client and DHCPv4 server using an IPv6 network. A between DHCPv4 client and DHCPv4 server using an IPv6 network. A
CRA either sits on the same, IPv6-accessable host with the DHCPv4 CRA either sits on the same, IPv6-accessible host with the DHCPv4
client, or sits on the same link with the host. client, or sits on the same link with the host running DHCPv4
client.
o Host Client Relay Agent(HCRA): a CRA which sits on the same, IPv6- o Host Client Relay Agent(HCRA): a CRA which sits on the same, IPv6-
accessible host with the DHCPv4 client. accessible host with the DHCPv4 client.
o On-Link Client Relay Agent(LCRA): a CRA which sits on the same o On-Link Client Relay Agent(LCRA): a CRA which sits on the same
link with the host that runs DHCPv4 client. link with the host that runs DHCPv4 client.
o IPv6-Transport Server(TSV): a DHCPv4 Server that supports IPv6 o IPv6-Transport Server(TSV): a DHCPv4 Server that supports IPv6
transport. TSV listens on IPv6 for incoming DHCPv4 messages, and transport. TSV listens on IPv6 for incoming DHCPv4 messages, and
sends DHCPv4 messages in IPv6 packets. sends DHCPv4 messages in IPv6 packets.
skipping to change at page 10, line 4 skipping to change at page 10, line 4
Email: danipko@microsoft.com Email: danipko@microsoft.com
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-dhc-client-id] [I-D.ietf-dhc-client-id]
Swamy, N., Halwasia, G., and S. Unit, "Client Identifier Swamy, N., Halwasia, G., and S. Unit, "Client Identifier
Option in DHCP Server Replies", Option in DHCP Server Replies",
draft-ietf-dhc-client-id-05 (work in progress), draft-ietf-dhc-client-id-07 (work in progress),
September 2012. November 2012.
[I-D.ietf-dhc-dhcpv4-relay-encapsulation] [I-D.ietf-dhc-dhcpv4-relay-encapsulation]
Lemon, T., Deng, H., and L. Huang, "Relay Agent Lemon, T., Deng, H., and L. Huang, "Relay Agent
Encapsulation for DHCPv4", Encapsulation for DHCPv4",
draft-ietf-dhc-dhcpv4-relay-encapsulation-01 (work in draft-ietf-dhc-dhcpv4-relay-encapsulation-01 (work in
progress), July 2011. progress), July 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 10, line 41 skipping to change at page 10, line 41
Version Four (DHCPv4)", RFC 4361, February 2006. Version Four (DHCPv4)", RFC 4361, February 2006.
[RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, "Softwire [RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand, "Softwire
Problem Statement", RFC 4925, July 2007. Problem Statement", RFC 4925, July 2007.
12.2. Informative References 12.2. Informative References
[I-D.ietf-softwire-public-4over6] [I-D.ietf-softwire-public-4over6]
Cui, Y., Wu, J., Wu, P., Vautrin, O., and Y. Lee, "Public Cui, Y., Wu, J., Wu, P., Vautrin, O., and Y. Lee, "Public
IPv4 over IPv6 Access Network", IPv4 over IPv6 Access Network",
draft-ietf-softwire-public-4over6-03 (work in progress), draft-ietf-softwire-public-4over6-05 (work in progress),
August 2012. February 2013.
Appendix A. Motivation for selecting this particular solution Appendix A. Motivation for selecting this particular solution
We considered three possible solutions to the problem of configuring We considered three possible solutions to the problem of configuring
IPv4 addresses on an IPv6 network. IPv4 addresses on an IPv6 network.
A.1. Configuring IPv4 with DHCPv6 A.1. Configuring IPv4 with DHCPv6
Use DHCPv6 instead of DHCPv4, to provision IPv4-related connectivity. Use DHCPv6 instead of DHCPv4, to provision IPv4-related connectivity.
In DHCPv6, the provisioned IPv4 address can be embedded into IPv6 In DHCPv6, the provisioned IPv4 address can be embedded into IPv6
 End of changes. 8 change blocks. 
12 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/