%% You should probably cite draft-ietf-dhc-sedhcpv6-21 instead of this revision.
@techreport{ietf-dhc-sedhcpv6-07,
    number =    {draft-ietf-dhc-sedhcpv6-07},
    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-sedhcpv6/07/},
    author =    {Sheng Jiang and Sean Shen and Dacheng Zhang and Tatuya Jinmei},
    title =     {{Secure DHCPv6}},
    pagetotal = 23,
    year =      2015,
    month =     mar,
    day =       23,
    abstract =  {The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables DHCPv6 servers to pass configuration parameters. It offers configuration flexibility. If not being secured, DHCPv6 is vulnerable to various attacks, particularly spoofing attacks. This document analyzes the security issues of DHCPv6 and specifies a Secure DHCPv6 mechanism for communications between DHCPv6 clients and DHCPv6 servers. This document provides a DHCPv6 client/server authentication mechanism based on sender's public/private key pairs or certificates with associated private keys. The DHCPv6 message exchanges are protected by the signature option and the timestamp option newly defined in this document.},
}