DHCPv4 over DHCPv6 Source Address Option
draft-fsc-softwire-dhcp4o6-saddr-opt-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Ian Farrer , Qi Sun , Yong Cui | ||
Last updated | 2015-04-03 (Latest revision 2014-09-30) | ||
Replaced by | draft-ietf-dhc-dhcp4o6-saddr-opt, draft-ietf-dhc-dhcp4o6-saddr-opt, RFC 8539 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
DHCPv4 over DHCPv6 [RFC7341] describes a mechanism for dynamically configuring IPv4 over an IPv6-only network. For DHCPv4 over DHCPv6 to function with some IPv4-over-IPv6 softwire mechanisms, the operator must obtain information about the IPv4 address and Port Set ID allocated to the DHCP 4o6 client, as well as the /128 IPv6 prefix that the client will use as the source of IPv4-in-IPv6 tunnel. This memo defines a DHCPv6 container option and two DHCPv6 sub-options used to communicate the source tunnel IPv6 address between the DHCP 4o6 client and server. It is designed to work in conjunction with the IPv4 address allocation process.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)