[dhcwg] Protocol Action: 'Rebind Capability in DHCPv6 Reconfigure Messages' to Proposed Standard (draft-ietf-dhc-dhcpv6-reconfigure-rebind-10.txt)
The IESG <iesg-secretary@ietf.org> Mon, 23 April 2012 17:21 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732EB21F86E1; Mon, 23 Apr 2012 10:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level:
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, 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 yHU09AzbKFuA; Mon, 23 Apr 2012 10:21:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9160421F86F4; Mon, 23 Apr 2012 10:21:30 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120423172130.15590.73925.idtracker@ietfa.amsl.com>
Date: Mon, 23 Apr 2012 10:21:30 -0700
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'Rebind Capability in DHCPv6 Reconfigure Messages' to Proposed Standard (draft-ietf-dhc-dhcpv6-reconfigure-rebind-10.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 17:21:31 -0000
The IESG has approved the following document: - 'Rebind Capability in DHCPv6 Reconfigure Messages' (draft-ietf-dhc-dhcpv6-reconfigure-rebind-10.txt) as a Proposed Standard This document is the product of the Dynamic Host Configuration Working Group. The IESG contact persons are Ralph Droms and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-reconfigure-rebind/ Technical Summary This document updates RFC 3315 to allow the Rebind message type to appear in the Reconfigure Message option of a Reconfigure message, which extends the Reconfigure message to allow a DHCPv6 server to cause a DHCPv6 client to send a Rebind message. The document also clarifies how a DHCPv6 client responds to a received Reconfigure message. Working Group Summary This document received a thorough review by the WG, and had broad support. Document Quality We are not aware of any implementations. Personnel Ted Lemon <Ted.Lemon@nominum.com> is the Document Shepherd. Brian Haberman is the Responsible AD. RFC Editor Note The last sentence of Section 7 should be changed from: OLD: Cryptographically Generated Addresses (CGA) [RFC3972], can provide source address ownership validation, message origin authentication and message integrity without requesting symmetric key pairs or supporting from any key management system. NEW: Cryptographically Generated Addresses (CGA) [RFC3972] can provide source address (for the DHCP server/relay) ownership validation, message origin authentication, and message integrity without requiring symmetric key pairs or support from a key management system.