[dhcwg] Protocol Action: DHCP reconfigure extension to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 30 August 2001 13:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16874; Thu, 30 Aug 2001 09:47:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28166; Thu, 30 Aug 2001 09:43:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA24004 for <dhcwg@ns.ietf.org>; Thu, 30 Aug 2001 07:22:33 -0400 (EDT)
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.9.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10209 for <dhcwg@ietf.org>; Thu, 30 Aug 2001 07:21:14 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mail.bucknell.edu (8.11.4/8.11.4) with ESMTP id f7UBMWq01094 for <dhcp-v4@bucknell.edu>; Thu, 30 Aug 2001 07:22:34 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10196; Thu, 30 Aug 2001 07:21:09 -0400 (EDT)
Message-Id: <200108301121.HAA10196@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: dhcp-v4@bucknell.edu
From: The IESG <iesg-secretary@ietf.org>
Date: Thu, 30 Aug 2001 07:21:09 -0400
Subject: [dhcwg] Protocol Action: DHCP reconfigure extension to Proposed Standard
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org


The IESG has approved the Internet-Draft 'DHCP reconfigure extension'
<draft-ietf-dhc-pv4-reconfigure-06.txt> as a Proposed Standard.  This
document is the product of the Dynamic Host Configuration Working
Group.  The IESG contact persons are Erik Nordmark and Thomas Narten.


 
Technical Summary
 
   This draft defines extensions to DHCP [RFC 2131] to allow dynamic
   reconfiguration of a single host triggered by the DHCP server
   (e.g., a new IP address). This is achieved by introducing a unicast
   FORCERENEW message that forces the client into the RENEW state. The
   behaviour for hosts using the DHCP INFORM message to obtain
   configuration information is also described.

Working Group Summary

  There has been support for this document in the WG for sometime, and
  the document has been waiting for the DHCP authentication document
  to complete, as the FORCERENEW messages is ignored unless
  authenticated. No issues were raised during the IETF Last Call.

Protocol Quality

  This document has been reviewed for the IESG by Thomas Narten.



_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg