RE: [dhcwg] DHC WG charter

"Bound, Jim" <Jim.Bound@hp.com> Fri, 11 October 2002 18:39 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 OAA01757 for <dhcwg-archive@odin.ietf.org>; Fri, 11 Oct 2002 14:39:13 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BIetm09729 for dhcwg-archive@odin.ietf.org; Fri, 11 Oct 2002 14:40:55 -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 g9BIetv09726 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 11 Oct 2002 14:40:55 -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 OAA01752 for <dhcwg-web-archive@ietf.org>; Fri, 11 Oct 2002 14:38:42 -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 g9BIc8v09645; Fri, 11 Oct 2002 14:38:08 -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 g9BIawv09060 for <dhcwg@optimus.ietf.org>; Fri, 11 Oct 2002 14:36:58 -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 OAA01664 for <dhcwg@ietf.org>; Fri, 11 Oct 2002 14:34:46 -0400 (EDT)
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id F006F7FC; Fri, 11 Oct 2002 14:36:51 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Fri, 11 Oct 2002 14:36:51 -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="iso-8859-1"
Subject: RE: [dhcwg] DHC WG charter
Date: Fri, 11 Oct 2002 14:36:51 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B02BE94BC@tayexc13.americas.cpqcorp.net>
Thread-Topic: [dhcwg] DHC WG charter
Thread-Index: AcJxS+CXJ//RcqMaQaitnxkTRkyDeAACLskQ
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Ralph Droms" <rdroms@cisco.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 11 Oct 2002 18:36:51.0808 (UTC) FILETIME=[2A722E00:01C27155]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9BIawv09061
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

OK with your update and replaces.

> - 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...
> 

Both topics above have charateristics that will require the IETF to develop protocol operations or extensions to make them happen.  They also both have market needs so we have a customer.  As they will be using dhc to perform these functions and that the necessary routing, application, dhc, and IP stack expertise exists in the dhc working group and that is a clear effort by the dhc group these should be part of our charter.

If there are any backroom statements about the expertise in this group to solve this problem let them have integrity and state so on this list or do not use it to prevent this charter ammendment.

regards,
/jim
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg