<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dhc-forcerenew-nonce" target="https://datatracker.ietf.org/doc/html/draft-ietf-dhc-forcerenew-nonce-07">
   <front>
      <title>Forcerenew Nonce Authentication</title>
      <author initials="D." surname="Miles" fullname="David Miles">
         <organization>Google</organization>
      </author>
      <author initials="W." surname="Dec" fullname="Wojciech Dec">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="J." surname="Bristow" fullname="James Bristow">
         <organization>Swisscom Schweiz AG</organization>
      </author>
      <author initials="R." surname="Maglione" fullname="Roberta Maglione">
         <organization>Telecom Italia</organization>
      </author>
      <date month="June" day="14" year="2012" />
      <abstract>
	 <t>Dynamic Host Configuration Protocol (DHCP) FORCERENEW allows for the reconfiguration of a single host by forcing the DHCP client into a Renew state on a trigger from the DHCP server.  In the Forcerenew Nonce Authentication protocol, the server sends a nonce to the client in the initial DHCP ACK that is used for subsequent validation of a FORCERENEW message.  This document updates RFC 3203. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dhc-forcerenew-nonce-07" />
   
</reference>
