RE: [dhcwg] DHC WG charter

"Bound, Jim" <Jim.Bound@hp.com> Thu, 24 October 2002 13:08 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 JAA05531 for <dhcwg-archive@odin.ietf.org>; Thu, 24 Oct 2002 09:08:15 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9ODA6b15124 for dhcwg-archive@odin.ietf.org; Thu, 24 Oct 2002 09:10:06 -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 g9ODA5v15121 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 24 Oct 2002 09:10:05 -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 JAA05522 for <dhcwg-web-archive@ietf.org>; Thu, 24 Oct 2002 09:07:44 -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 g9OD7nv15059; Thu, 24 Oct 2002 09:07:49 -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 g9OD6Cv14348 for <dhcwg@optimus.ietf.org>; Thu, 24 Oct 2002 09:06:12 -0400
Received: from zmamail05.zma.compaq.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05297 for <dhcwg@ietf.org>; Thu, 24 Oct 2002 09:03:51 -0400 (EDT)
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net [16.103.130.96]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 9129747DD; Thu, 24 Oct 2002 09:06:09 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Thu, 24 Oct 2002 09:06:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [dhcwg] DHC WG charter
Date: Thu, 24 Oct 2002 09:06:09 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B02BE9696@tayexc13.americas.cpqcorp.net>
Thread-Topic: [dhcwg] DHC WG charter
Thread-Index: AcJ6xGPBIEF+709JScWjYNVoNhuZBAAmZmEQ
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Ralph Droms" <rdroms@cisco.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 24 Oct 2002 13:06:09.0478 (UTC) FILETIME=[1EDDA660:01C27B5E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9OD6Cv14349
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Looks good to me.  If the prefix option in v6 covers us for prefix
delegation that is fine otherwise a no or yeah on that would be good on
the list.  I vote yeah.

/jim

> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com] 
> Sent: Wednesday, October 23, 2002 2:26 PM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] DHC WG charter 
> 
> 
> Here's a revised charter, based on input from mailing list 
> discussion (this 
> charter also available at http://www.dhcp.org/charter-update.html); 
> comments or acknowledgments (this looks OK) strongly encouraged...
> 
> 
> 
> 		   Dynamic Host Configuration (dhc)
> 
> The dhc working group (DHCWG) has developed DHCP for 
> automated allocation, configuration and management of IP 
> addresses and TCP/IP protocol stack parameters. DHCP is 
> currently a "Draft Standard".  The base protocol is document 
> in RFC2131 and RFC2132.  Additional options are documented in 
> a series of RFCs (see http://www.dhcp.org/rfcs.html).  The 
> working group now has four main
> objectives:
> 
> * RFC 3118 defines current security mechanisms for DHCPv4.
>    Unfortunately, RFC 3118 has neither been implemented nor 
> deployed to
>    date. There is widespread feeling that its current restriction to
>    manual keying of clients limits its deployability. It is 
> the goal of
>    DHCWG to rectify this situation by defining extensions that have
>    better deployability properties. In order to achive this 
> goal, DHCWG
>    will develop a threat model and analysis of the authentication
>    protection provided by RFC3118; specific issues to be addressed
>    might 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
>    - Complete or terminate work on published DHCPv6 options:
>        IPv6 Prefix Options for DHCPv6
>          <draft-troan-dhcpv6-opt-prefix-delegation-01.txt>
>        DSTM Options for DHCP
>          <draft-ietf-dhc-dhcpv6-opt-dstm-01.txt>
>        DSTM Ports Option for DHCPv6
>          <draft-ietf-dhc-dhcpv6-opt-dstm-ports-01.txt>
>        DNS Configuration options for DHCPv6
>          <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
>        Load Balancing for DHCPv6
>          <draft-ietf-dhc-dhcpv6-loadb-02.txt>
>        NIS Configuration Options for DHCPv6
>          <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
>        Time Configuration Options for DHCPv6
>          <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
>        Client Preferred Prefix option for DHCPv6
>          <draft-ietf-dhc-dhcpv6-opt-cliprefprefix-00.txt>
>    - Encourage independent implementations and report on
>      interoperability testing
> 
> * Complete or terminate work on DHCP extensions and new options that
>    are currently work in progress:
>    - Failover protocol
>    - DHCP/DDNS interaction
>      <draft-ietf-dhc-fqdn-option-04.txt>
>      <draft-ietf-dhc-ddns-resolution-04.txt>
>    - DHCP Server MIB
>      <draft-ietf-dhc-server-mib-07.txtDHCP MIB>
>    - Host name options (Smith/Lemon?)
>    - DHCP Leasequery
>    - DHCP Option for CableLabs Client Configuration
>      <draft-ietf-dhc-packetcable-03.txt>
>    - KDC Server Address Sub-option
>      <draft-ietf-dhc-suboptions-kdc-serveraddress-00.txt>
>    - DHCP Options for Internet Storage name Service
>      <draft-ietf-dhc-isnsoption-03.txt>
>    - The Authentication Suboption for the DHCP Relay Agent Option
>      <draft-ietf-dhc-auth-suboption-00.txt>
>    - Link Selection sub-option for the Relay Agent Information Option
>      <draft-ietf-dhc-agent-subnet-selection-03.txt>
>    - DHCP VPN Information Option
>    - VPN Identifier sub-option for the Relay Agent Information Option
>    - RADIUS Attributes Sub-option for the DHCP Relay Agent 
> Information Option
> 
> * DHCWG is responsible for reviewing (and sometimes developing) DHCP
>    options or other extensions (for both IPv4 and IPv6). DHCWG is
>    expected to review all proposed extensions to DHCP to ensure that
>    they are consistent with the DHCP specification and other option
>    formats, that they do not duplicate existing mechanisms, 
> etc.  DHCWG
>    will not (generally) be responsible for evaluating the semantic
>    content of proposed options. DHCWG will not adopt new proposals for
>    extensions to DHCP as working group documents without first
>    coordinating with other relevant working groups and determining who
>    has the responsibility for reviewing the semantic content of an
>    option.
> 
> * 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.
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg