Re: [dhcwg] DHC WG charter

Ralph Droms <rdroms@cisco.com> Fri, 11 October 2002 17:07 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28371 for <dhcwg-archive@odin.ietf.org>; Fri, 11 Oct 2002 13:07:44 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BH9Pv05033 for dhcwg-archive@odin.ietf.org; Fri, 11 Oct 2002 13:09:25 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BH9Pv05030 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 11 Oct 2002 13:09:25 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28354 for <dhcwg-web-archive@ietf.org>; Fri, 11 Oct 2002 13:07:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BH69v04388; Fri, 11 Oct 2002 13:06:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BH5Wv04357 for <dhcwg@optimus.ietf.org>; Fri, 11 Oct 2002 13:05:32 -0400
Received: from funnel.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28155 for <dhcwg@ietf.org>; Fri, 11 Oct 2002 13:03:20 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn1-41.cisco.com [10.82.224.41]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA10348 for <dhcwg@ietf.org>; Fri, 11 Oct 2002 13:05:11 -0400 (EDT)
Message-Id: <4.3.2.7.2.20021011125559.03a78560@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 11 Oct 2002 13:05:07 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHC WG charter
In-Reply-To: <2C054C5A-8014-11D6-9A23-00039367340A@nominum.com>
References: <JCELKJCFMDGAKJCIGGPNOEOKDNAA.rbhibbs@pacbell.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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>

Here's a revised draft WG charter, with edits based on feedback from 
mailing list discussion.  The primary changes in this revision are:

* Rewrote the authentication charter item to require
   require development of a threat model and analysis
   of RFC3118, with suggestions about specific issues
   to consider in the analysis.  Added separate charter
   item to develop mechanisms to address issues identified
   by threat model and analysis.
* Deleted references to specific options to be published
   as part of DHCPv6; deleted reference to prefix delegation,
   DNS configuration (see below for more details)
* Replaced charter item on acceptance of DHCP as Standard
   with analysis of problems with current spec that impede
   development of interoperable implementations.

We need consensus on whether the following charter items should be included 
in the charter:

- Develop extensions to DHCPv6 for prefix delegation, DNS
   configuration, etc.
- Determine the requirements for DHC to support the dynamic
   renumbering of networks using fast path delegation as CPE
   front end between ISP and Private Networks.

Please reply with comments...

- Ralph

=====


		   Dynamic Host Configuration (dhc)

The working group has the following primary objectives:

* Develop a threat model and analysis of the authentication
   protection provided by RFC3118; specific issues to be addressed
   include:
   - Improved key management and scalability
   - Security for messages passed between relay agents and servers
   - Threats of DoS attacks through FORCERENEW

* Develop requirements for any new protocols to address threats or
   other enhancement identified by the threat model and analysis of
   3118

* 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
   - Encourage independent implementations and report on
     interoperability testing
   - Revise specification and publish for acceptance as Draft Standard
     by 10/18/2002

* Write an analysis of the DHCP specification, including RFC2131,
   RFC2132 and other RFCs defining additional options, which identifies
   ambiguities, contradictory specifications and other obstacles to
   development of interoperable implementations.  Recommend a process
   for resolving identified problems and incorporating the resolutions
   into the DHCP specification.

* Complete the specification and publish work in progress as
   standards:
   - Failover protocol
   - DHCP/DDNS interaction
   - SNMP MIB
   - Host name options
   - Leasequery
   - 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
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg