<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dhc-sedhcpv6" target="https://datatracker.ietf.org/doc/html/draft-ietf-dhc-sedhcpv6-21">
   <front>
      <title>Secure DHCPv6</title>
      <author initials="L." surname="Li" fullname="Lishan Li">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="S." surname="Jiang" fullname="Sheng Jiang">
         <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author initials="Y." surname="Cui" fullname="Yong Cui">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="T." surname="Jinmei" fullname="Tatuya Jinmei">
         <organization>Infoblox Inc.</organization>
      </author>
      <author initials="T." surname="Lemon" fullname="Ted Lemon">
         <organization>Nominum, Inc.</organization>
      </author>
      <author initials="D." surname="Zhang" fullname="Dacheng Zhang">
         </author>
      <date month="February" day="21" year="2017" />
      <abstract>
	 <t>   DHCPv6 includes no deployable security mechanism that can protect
   end-to-end communication between DHCP clients and servers.  This
   document describes a mechanism for using public key cryptography to
   provide such security.  The mechanism provides encryption in all
   cases, and can be used for authentication based on pre-sharing of
   authorized certificates.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dhc-sedhcpv6-21" />
   
</reference>
