Re: [dhcwg] DHC WG charter

Thomas Narten <narten@us.ibm.com> Tue, 15 October 2002 02:37 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 WAA08819 for <dhcwg-archive@odin.ietf.org>; Mon, 14 Oct 2002 22:37:27 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9F2dDX07976 for dhcwg-archive@odin.ietf.org; Mon, 14 Oct 2002 22:39:13 -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 g9F2dDv07973 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 14 Oct 2002 22:39:13 -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 WAA08813 for <dhcwg-web-archive@ietf.org>; Mon, 14 Oct 2002 22:36:56 -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 g9F2afv07362; Mon, 14 Oct 2002 22:36:43 -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 g9F2Zkv07334 for <dhcwg@optimus.ietf.org>; Mon, 14 Oct 2002 22:35:46 -0400
Received: from cichlid.adsl.duke.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08707 for <dhcwg@ietf.org>; Mon, 14 Oct 2002 22:33:28 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g9F2Xiq06688; Mon, 14 Oct 2002 22:33:44 -0400
Message-Id: <200210150233.g9F2Xiq06688@cichlid.adsl.duke.edu>
To: "Bound, Jim" <Jim.Bound@hp.com>
cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] DHC WG charter
In-Reply-To: Message from "Bound, Jim" <Jim.Bound@hp.com> of "Mon, 14 Oct 2002 18:25:55 EDT." <9C422444DE99BC46B3AD3C6EAFC9711B02BE94F2@tayexc13.americas.cpqcorp.net>
Date: Mon, 14 Oct 2002 22:33:43 -0400
From: Thomas Narten <narten@us.ibm.com>
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>

> And who defines who a subject matter expert is?

I would hope that this will generally be obvious. The folks who
understand/develop the technology that the DHC option is to be used
for. That could the SIP, IPS, LDAP, Kerberos, and SLP folk, etc. In
general, the DHC WG won't know much about how such options will be
used, so they can't really evaluate whether the option (other than its
encoding) makes sense. What I'm trying to avoid is having the charter
imply (or seem to imply) that the WG will take on any/all options
someone brings to the WG. I think it is fine for the WG to review any
option from the perspective of DHC, but it should be clear that
approval of all DHC options is a two step process. Acceptance from the
DHC community and the actual users of the option.

Thomas
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg