%% You should probably cite draft-ietf-dhc-sedhcpv6-21 instead of this revision. @techreport{ietf-dhc-sedhcpv6-03, number = {draft-ietf-dhc-sedhcpv6-03}, 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/03/}, author = {Sheng Jiang and Sean Shen and Dacheng Zhang and Tatuya Jinmei}, title = {{Secure DHCPv6 with Public Key}}, pagetotal = 23, year = 2014, month = jun, day = 20, abstract = {The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables DHCPv6 servers to pass configuration parameters. It offers configuration flexibility. If not 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 communication between DHCPv6 clients and DHCPv6 servers. This mechanism is based on public/private key pairs. The authority of the sender may depend on either pre-configuration mechanism or Public Key Infrastructure.}, }