{
  "draft": "draft-ietf-dhc-forcerenew-nonce-07",
  "doc_id": "RFC6704",
  "title": "Forcerenew Nonce Authentication",
  "authors": [
    "D. Miles",
    "W. Dec",
    "J. Bristow",
    "R. Maglione"
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "12",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Dynamic Host Configuration",
  "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]",
  "pub_date": "August 2012",
  "keywords": [
    "DHCP"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [
    "RFC3203"
  ],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC6704",
  "errata_url": "https://www.rfc-editor.org/errata/rfc6704"
}