%% You should probably cite draft-ietf-dhc-dhcpv4-over-ipv6-09 instead of this revision.
@techreport{ietf-dhc-dhcpv4-over-ipv6-08,
    number =    {draft-ietf-dhc-dhcpv4-over-ipv6-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-over-ipv6/08/},
    author =    {Yong Cui and Peng Wu and Jianping Wu and Ted Lemon and Qi Sun},
    title =     {{DHCPv4 over IPv6 Transport}},
    pagetotal = 14,
    year =      2013,
    month =     oct,
    day =       21,
    abstract =  {In IPv6 networks, there remains a need to provide IPv4 service for some residual devices. This document describes a mechanism for allocating IPv4 addresses to such devices, using DHCPv4 with an IPv6 transport. It is done by putting a special relay agent function (Client Relay Agent) on the client side, as well as extending the behavior of the server; in the case where DHCP server only supports IPv4 transport, a relay agent is extended to support IPv6 transport (IPv6-Transport Relay Agent) and relay DHCP traffic for the server, with a new Relay Agent Information sub-option added to carry the IPv6 address of the Client Relay Agent. DHCPv4 over IPv6 has been developed in the IETF, and some implementations and deployments have been carried out. But this mechanism is not recommended for future implementation or deployment.},
}