[dhcwg] Status of DHCPv6 specification

Ralph Droms <rdroms@cisco.com> Mon, 04 November 2002 12:15 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10377 for <dhcwg-archive@odin.ietf.org>; Mon, 4 Nov 2002 07:15:26 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA4CHND22096 for dhcwg-archive@odin.ietf.org; Mon, 4 Nov 2002 07:17:23 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4CHNv22093 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 07:17:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10360 for <dhcwg-web-archive@ietf.org>; Mon, 4 Nov 2002 07:14:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4C9sv21917; Mon, 4 Nov 2002 07:09:55 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4C6tv21302 for <dhcwg@optimus.ietf.org>; Mon, 4 Nov 2002 07:06:55 -0500
Received: from funnel.cisco.com (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10202 for <dhcwg@ietf.org>; Mon, 4 Nov 2002 07:04:27 -0500 (EST)
Received: from rdroms-w2k.cisco.com (rtp-vpn1-415.cisco.com []) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id HAA20435 for <dhcwg@ietf.org>; Mon, 4 Nov 2002 07:06:54 -0500 (EST)
Message-Id: <>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 04 Nov 2002 07:06:51 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Status of DHCPv6 specification
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Earlier this year, the DHCPv6 spec (draft-ietf-dhc-dhcpv6-26.txt) was reviewed
by the IESG.  Based on feedback from that review, we (the DHCPv6 authors) 
draft-ietf-dhc-dhcpv6-27.txt.  The majority of the changes were related to 
authentication.  I've included a summary of the changes in the -27 rev of 
the specification below.

draft-ietf-dhc-dhcpv6-27.txt is now under review by the IESG.

- Ralph

     -  Use of Reconfigure Key message is a new protocol in DHCP

     -  Added "DHCP Realm" to authentication to disambiguate
        keys from different administrative domains

     -  Renamed IA to IA_NA throughout; now IA refers collectively to
        IA_NA and IA_TA

     -  Reconfigure Accept option allows client to tell server if it
        will do Reconfigure and allows server to control whether client
        accepts Reconfigure

     -  Add desynchronizing randomization for Confirm and
        Information-request messages

     -  Added requirement for Client Identifier option if
        Information-request message is to be authenticated

     -  Deleted restriction against more than one Vendor-specific
        Information option with same enterprise number

     -  Added text in section 15 requiring that a server discards
        messages received via unicast such as Solicit that must be sent
        via multicast, to ensure relay agents can add relay agent
        options when needed

     -  Eliminated use of "message code" in section 5

     -  Eliminated "AddrUnavail" and "ConfNoMatch" status codes because
        they are no longer used

     -  Edited to use "IA" for a non-differentiated IA; "IA_NA" and
        "IA_TA" for specific types of addresses.

     -  Deleted AuthFailed status code; spec requires that receiver
        discard messages that fail authentication with no response to the

     -  DUID now limited to 128 bytes (was 256)

     -  Reconfigure message includes IA option to specifically identify
        IAs that are to be modified.

dhcwg mailing list