%% You should probably cite rfc6704 instead of this I-D.
@techreport{ietf-dhc-forcerenew-nonce-07,
    number =    {draft-ietf-dhc-forcerenew-nonce-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-forcerenew-nonce/07/},
    author =    {David Miles and Wojciech Dec and James Bristow and Roberta Maglione},
    title =     {{Forcerenew Nonce Authentication}},
    pagetotal = 12,
    year =      2012,
    month =     jun,
    day =       14,
    abstract =  {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{]}},
}