[dhcwg] WG Action: Rechartered Dynamic Host Configuration (dhc)

The IESG <iesg-secretary@ietf.org> Fri, 13 September 2013 17:15 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 B762A21F9F2B; Fri, 13 Sep 2013 10:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level:
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=0.168, 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 cpiutSU2xebe; Fri, 13 Sep 2013 10:15:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC9611E816D; Fri, 13 Sep 2013 10:15:47 -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.71.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130913171546.20349.63828.idtracker@ietfa.amsl.com>
Date: Fri, 13 Sep 2013 10:15:46 -0700
Cc: dhc WG <dhcwg@ietf.org>
Subject: [dhcwg] WG Action: Rechartered Dynamic Host Configuration (dhc)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 13 Sep 2013 17:15:47 -0000

The Dynamic Host Configuration (dhc) working group in the Internet Area
of the IETF has been rechartered. For additional information please
contact the Area Directors or the WG Chairs.

Dynamic Host Configuration (dhc)
------------------------------------------------
Current Status: Active WG

Chairs:
  Bernie Volz <volz@cisco.com>
  Tomek Mrugalski <tomasz.mrugalski@gmail.com>

Assigned Area Director:
  Ted Lemon <ted.lemon@nominum.com>

Mailing list
  Address: dhcwg@ietf.org
  To Subscribe: http://www.ietf.org/mailman/listinfo/dhcwg
  Archive: http://www.ietf.org/mail-archive/web/dhcwg/

Charter:

The Dynamic Host Configuration working group (DHC WG) has developed DHCP
for automated allocation, configuration and management of IP addresses
and TCP/IP protocol stack parameters. DHCPv4 is currently a Draft
Standard and is documented in RFC 2131 and RFC 2132. DHCPv6 is currently
a Proposed Standard and is documented in RFC 3315. Subsequent RFCs
document additional options and other enhancements to the specifications.

The DHC WG is responsible for defining DHCP protocol extensions.
Definitions of new DHCP options that are delivered using standard
mechanisms with documented semantics are not considered a protocol
extension and thus are outside of scope for the DHC WG. Such options
should be defined within their respective WGs and reviewed by the DHCP
Directorate. However, if such options require protocol extensions or new
semantics, the protocol extension work must be done in the DHC WG.

The DHC WG has the following main objectives:
  
1. Develop extensions to the DHCPv6 infrastructure as required to meet
   new applications and deployments of DHCP. The topics currently in
   development are:
   - DHCPv6 Failover, High Availability and Load Balancing
   - Extend DHCPv6 to work with multiple provisioning domains
   - DHCP provisioning of IPv4 clients over IPv6 networks
   - SOLMAXRT counter update
   - Container option 
   - Access Network Identifier
   - DNS registration for SLAAC

   Additional topics may only be added with approval from the responsible
   Area Director or by re-chartering.

2. Develop a replacement for OPTION_NTP_SERVER (RFC 5908).   The
   DHC working group will develop this option, taking input from the NTP
   working group during the development process.   Last call on this
option
   will be done in the DHC working group.

3. Specify guidelines for creating new DHCPv6 options.

4. Develop documents that help explain operational considerations for
   the wider community.

5. Issue updated versions of the DHCP base specifications--
   RFC 3315 (DHCPv6), RFC 3633 (DHCPv6 Prefix Delegation) and
   RFC 3736 (Stateless DHCPv6) so as to fix errata and bring
   the documents to the point where they can advance along the
   IETF Standards Track.

6. In the process of updating the DHCP base specifications, in
   cases where time is of the essence, issue corrections and
   clarifications of the specifications in order to quickly address
   interoperability problems.

7. Write analyses and interoperability reports on existing DHC
   documents, including base specs.

8. When serious interoperability problems are found in other DHCP
   specifications, issue updated versions of those problems to
   address the interoperability problems.

Milestones:
  Jul 2008 - Recharter, if needed
  Sep 2013 - Submit 'Guidelines for Creating New DHCP Options'
(draft-ietf-dhc-option-guidelines) to IESG for Best Current Practice
  Sep 2013 - Convert RFC3315 nroff sources into XML format
  Oct 2013 - Appoint editor, assemble design team for 3315bis work
  Oct 2013 - WG last call on v4configuration draft
  Oct 2013 - Submit dhcpv6-failover-design to IESG
  Oct 2013 - Submit stateful issues draft to IESG
  Nov 2013 - Decide which RFCs and drafts to merge in 3315bis
  Nov 2013 - WG last call on dhcpv6-unknown-msg
  Nov 2013 - WG last call on dhcpv4-over-dhcpv6
  Dec 2013 - Submit v4configuration draft to IESG
  Dec 2013 - Submit dhcpv6-unknown-msg to IESG
  Dec 2013 - WG last calll on draft-ietf-dhc-addr-registration
  Feb 2014 - Submit dhcv4-over-dhcpv6 to IESG
  Feb 2014 - Submit draft-ietf-dhc-addr-registration to IESG
  Mar 2014 - Adopt 3315bis draft
  Mar 2014 - WG last call on access-network-identifier
  Jun 2014 - Submit access-network-identifier to IESG
  Nov 2014 - WG last call on 331bis draft
  Apr 2015 - Submit 3315bis draft to IESG