[dhcwg] DHC WG charter

Ralph Droms <rdroms@cisco.com> Thu, 13 June 2002 12:29 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09309 for <dhcwg-archive@odin.ietf.org>; Thu, 13 Jun 2002 08:29:47 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA15591 for dhcwg-archive@odin.ietf.org; Thu, 13 Jun 2002 08:30:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15286; Thu, 13 Jun 2002 08:27:59 -0400 (EDT)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15272 for <dhcwg@optimus.ietf.org>; Thu, 13 Jun 2002 08:27:56 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09156 for <dhcwg@ietf.org>; Thu, 13 Jun 2002 08:27:20 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com []) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g5DCROHt001786 for <dhcwg@ietf.org>; Thu, 13 Jun 2002 05:27:24 -0700 (PDT)
Date: Thu, 13 Jun 2002 08:27:24 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Message-ID: <Pine.GSO.4.44.0206130826240.6993-100000@funnel.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [dhcwg] DHC WG charter
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

The Internet ADs have suggested it is time (likely
*way* past time) to revisit the DHC WG charter.  Here's a first pass at
what I see as the issues currently in front of the WG.  The objectives are
not presented in any particular order.

Please review and send your comments to the mailing list.  The goal is
to have consensus on a list of objectives for final review at the WG
meeting in Yokohama.

- Ralph


The working group has the following primary objectives:

* Develop additional authentication protocols within the framework
  defined in RFC3118, along with other mechanisms to mitigate the
  threat of attacks on DHCP clients and servers:
  - New RFC3118 protocols to address improved key management and
    improved scalability
  - Provide security for messages passed between relay agents and
  - Consider solutions for specific threats such as use of nonce
    identifier to defend against DoS attacks through FORCERENEW from
    off-path attackers

* Complete the specification of DHCP for IPv6 (DHCPv6):
  - Gain acceptance and publication of current Internet Draft as
    Proposed Standard
  - Develop and publish specifications for options and other
    extensions to DHCPv6, including those already published as
    Internet Drafts:
    + "DNS Configuration Options for DHCPv6"
    + "Time Configuration Options for DHCPv6"
    + "NIS Configuration Options for DHCPv6"
    + "DSTM Ports Option for DHCPv6", "DSTM Options for DHCPv6"
    + "Load Balancing for DHCPv6"
  - Encourage independent implementations and conduct interoperability
  - Revise specification and publish for acceptance as Draft Standard
    by 6/30/2002
  - Develop extensions to DHCPv6 for prefix delegation, DNS
    configuration, etc.

* Revise and submit the DHCP specification for acceptance as a Full

* Complete the specification and publish work in progress as
  - Failover protocol
  - DHCP/DDNS interaction
  - Host name options
  - Other client and relay agent options

* Review new options for DHCP, as deemed appropriate by the working
  group and/or the Internet area directors

dhcwg mailing list