datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Forcerenew Nonce Authentication
draft-ietf-dhc-forcerenew-nonce-07

RFC
Document Stream: IETF
Last updated: 2012-06-14
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (dhc)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6704
IANA Action State: RFC-Ed-Ack 
Responsible AD: Ralph Droms
IESG Note: Ted Lemon (ted.lemon@nominum.com) is the document shepherd.
Send notices to: dhc-chairs@tools.ietf.org, draft-ietf-dhc-forcerenew-nonce@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-dhc-forcerenew-nonce.

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]

Authors:
David Miles
Wojciech Dec <wdec@cisco.com>
James Bristow <James.Bristow@swisscom.com>
Roberta Maglione <roberta.maglione@telecomitalia.it>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)