Last Call: <draft-ietf-dhc-triggered-reconfigure-05.txt> (Reconfigure Triggered by DHCPv6 Relay Agents) to Proposed Standard
The IESG <noreply@ietf.org> Mon, 22 April 2013 14:16 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 7EE0421F91CE; Mon, 22 Apr 2013 07:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7H9CYxo+pvJ;
Mon, 22 Apr 2013 07:16:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com
(Postfix) with ESMTP id F215221F91B7; Mon, 22 Apr 2013 07:15:59 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <noreply@ietf.org>
To: IETF-Announce:;
Subject: Last Call: <draft-ietf-dhc-triggered-reconfigure-05.txt> (Reconfigure
Triggered by DHCPv6 Relay Agents) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p3
Sender: <iesg-secretary@ietf.org>
Message-ID: <20130422141559.20207.20713.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2013 07:15:59 -0700
X-Mailman-Approved-At: Mon, 22 Apr 2013 10:00:32 -0700
Cc: dhcwg@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF Discussion List <ietf@ietf.org>
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 16:35:36 -0000
The IESG has received a request from the Dynamic Host Configuration WG (dhc) to consider the following document: - 'Reconfigure Triggered by DHCPv6 Relay Agents' <draft-ietf-dhc-triggered-reconfigure-05.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-05-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines new DHCPv6 messages: Reconfigure-Request and Reconfigure-Reply. Reconfigure-Request message is sent by a DHCPv6 relay agent to notify a DHCPv6 server about a configuration information change, so that the DHCPv6 server can send a Reconfigure message accordingly. Reconfigure-Reply message is used by the server to acknowledge the receipt of Reconfigure-Request. This document updates RFC 3315 and RFC 6422. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-dhc-triggered-reconfigure/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-dhc-triggered-reconfigure/ballot/ No IPR declarations have been submitted directly on this I-D.