[dhcwg] RFC 3315 Bis Update (& New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt)

"Bernie Volz (volz)" <volz@cisco.com> Mon, 27 October 2014 14:44 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 602F51A87EE for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id olyk9mAxeEQ7 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:44:31 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F8D21A87E2 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 07:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4680; q=dns/txt; s=iport; t=1414421072; x=1415630672; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=poGNmom7Tr0Fca2fwi9id3/uH6ecJNpng8bF7RBBUxQ=; b=frJzn+sSxxspFONyJncnh2/VDpQUAsHdk9iOrMBtS6SAPm180znSUoDd HLZRx6KHcQrO4lp/aTZ8tIjlRon8OUv9HuvP+JlAmAJhJDE4+RPFVPlFQ 9BE668m0nK5uLlwXC2MVhyiNIhlS2SqWhcuh5gqyjvY4O7MjHLewQSV4e Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.04,796,1406592000"; d="scan'208";a="366852403"
Received: from alln-core-7.cisco.com ([]) by rcdn-iport-4.cisco.com with ESMTP; 27 Oct 2014 14:44:31 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com []) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9REiUkd019370 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 27 Oct 2014 14:44:30 GMT
Received: from xmb-rcd-x04.cisco.com ([]) by xhc-rcd-x03.cisco.com ([]) with mapi id 14.03.0195.001; Mon, 27 Oct 2014 09:44:30 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: RFC 3315 Bis Update (& New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt)
Thread-Index: Ac/x9IOEHPk6gLsLTfi6awL5bD/Jow==
Date: Mon, 27 Oct 2014 14:44:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B6F7B72@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/7tULwOr_2vlNuT1BecnxO5Jen9I
Subject: [dhcwg] RFC 3315 Bis Update (& New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Oct 2014 14:44:33 -0000

For those interested in this work, here's a brief update:

1. There will be a DHCPv6bis team meeting at IETF-91. It will be:

Tuesday, 11/11 from 0900-1130 (HST, UTC - 10h) in South Pacific 2.

This is a working session to review open issues, assign work, and discuss outstanding work items to move them forward. This meeting is open to anyone, but is preliminary for the DHCPv6bis team to meet face-to-face. (An agenda should be available shortly.)

We will update the DHC WG on the status at the DHC WG session (late Thursday afternoon).

2. We have published an updated RFC-3315bis document (see announcement below). This include some additional changes but is not yet "complete" (see http://trac.tools.ietf.org/group/dhcpv6bis/report/3 for the open tickets).

Appendix A in the document tracks most of the changes, and the new entries since the 02 version are:

   30.  Clarified that encapsulated options must be requested using top	 		
        level ORO (ticket #38).	 		
   31.  Clarified that configuration for interface X should be requested	 		
        over interface X (ticket #48).	 		
   32.  CONFIRM is now an optional message (MUST send Confirm eased to	 		
        SHOULD) (ticket #120).	 		
   33.  Added reference to RFC7227: DHCPv6 Option Guidelines (ticket	 		
   34.  Added new section 5 providing an overview of DHCPv6 operational	 		
        modes and removed two prefix delegation sections from section 1.	 		
        See tickets #53, #100, and #102.	 		
   35.  Addressed ticket #115 - don't use DHCPv6 for DHCPv4	 		

This version also includes a few unfinished items. Progress has been a bit slower than hoped in the past several months.

- Bernie

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, October 27, 2014 10:02 AM
Subject: New Version Notification for draft-dhcwg-dhc-rfc3315bis-03.txt

A new version of I-D, draft-dhcwg-dhc-rfc3315bis-03.txt
has been successfully submitted by Bernie Volz and posted to the
IETF repository.

Name:		draft-dhcwg-dhc-rfc3315bis
Revision:	03
Title:		Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis
Document date:	2014-10-27
Group:		Individual Submission
Pages:		123
URL:            http://www.ietf.org/internet-drafts/draft-dhcwg-dhc-rfc3315bis-03.txt
Status:         https://datatracker.ietf.org/doc/draft-dhcwg-dhc-rfc3315bis/
Htmlized:       http://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis-03
Diff:           http://www.ietf.org/rfcdiff?url2=draft-dhcwg-dhc-rfc3315bis-03

   The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP
   servers to pass configuration parameters such as IPv6 network
   addresses to IPv6 nodes.  It offers the capability of automatic
   allocation of reusable network addresses and additional configuration
   flexibility.  This protocol is a stateful counterpart to "IPv6
   Stateless Address Autoconfiguration" (RFC 4862), and can be used
   separately or concurrently with the latter to obtain configuration


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat