RFC 6704: Forcerenew Nonce Authentication
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6704
- Published
- August 2012
- Authors
- D. Miles; W. Dec; J. Bristow; R. Maglione
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 3203
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6925The DHCPv4 Relay Agent Identifier Sub-OptionCurrent
April 2013
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 5071Dynamic Host Configuration Protocol Options Used by PXELINUXCurrent
December 2007
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
- RFC 8801Discovering Provisioning Domain Names and DataCurrent
July 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?