Re: [dhcwg] DHC WG charter
Ralph Droms <rdroms@cisco.com> Thu, 24 October 2002 20:26 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 QAA22192 for <dhcwg-archive@odin.ietf.org>; Thu, 24 Oct 2002 16:26:24 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OKSHU08839 for dhcwg-archive@odin.ietf.org; Thu, 24 Oct 2002 16:28:17 -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 g9OKSHv08836 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 24 Oct 2002 16:28:17 -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 QAA22188 for <dhcwg-web-archive@ietf.org>; Thu, 24 Oct 2002 16:25:53 -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 g9OKPdv08781; Thu, 24 Oct 2002 16:25:39 -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 g9OKOqv08730 for <dhcwg@optimus.ietf.org>; Thu, 24 Oct 2002 16:24:52 -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 QAA22099 for <dhcwg@ietf.org>; Thu, 24 Oct 2002 16:22:29 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (dhcp-128-107-133-128.cisco.com [128.107.133.128]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA00486 for <dhcwg@ietf.org>; Thu, 24 Oct 2002 16:24:46 -0400 (EDT)
Message-Id: <4.3.2.7.2.20021024162427.03bd3a30@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 24 Oct 2002 16:24:42 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHC WG charter
In-Reply-To: <200210241834.g9OIYWh19187@rotala.raleigh.ibm.com>
References: <Message from Ralph Droms <rdroms@cisco.com> <4.3.2.7.2.20021023161441.03ecb358@funnel.cisco.com>
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>
The idea behind "complete or terminate..." was to be conscious about the progress (or lack thereof) on expired documents. Mostly an explicit and visible sanity check with the authors to find out if progress will be made in the future (with a pretty low bar on "progress"). There may be some docs that the WG wants to take off the charter (but I doubt it). - Ralph At 02:34 PM 10/24/2002 -0400, Thomas Narten wrote: > > The posted charter has been revised based on Bernie's input... > >Looks pretty good overall. > >But one thing seems odd: > > > Complete or terminate work on DHCP ... > >And then lists all the relevant WG drafts. > >I think everyone will agree that the majority of the listed IDs stay >as WG items. Maybe a small number should be terminated? > >We should have the discussion now about which documents are in and >which are no longer needed/appropriate. After all, the (re)chartering >process is about aligning the charter with the work being done. > >There may be cases where there is a specific document that we don't >really know today what to do with it, that's OK, so long as it is >clear in the milestone (or charter) that the first order of business >is to figure out what to do with it (i.e., before additional work is >done on it). > >But I don't think the charter should leave it so open ended as to >which IDs may or may not be kept. > >Thomas > > >_______________________________________________ >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
- [Dhcwg] Re: Change to 'seconds' field in DHCP mes… Ralph Droms
- RE: [Dhcwg] Re: Change to 'seconds' field in DHCP… Bernie Volz (EUD)
- [dhcwg] RE: Change to 'seconds' field in DHCP mes… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ralph Droms
- Re: [Dhcwg] Re: Change to 'seconds' field in DHCP… Ted Lemon
- [dhcwg] Changes to remove "client-link-local-addr… Ralph Droms
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- Re: [dhcwg] Changes to remove "client-link-local-… Ralph Droms
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- Re: Re[2]: [dhcwg] Lease database storage in DHCP… Thomas Narten
- Re: [dhcwg] Assigning DHCPv6 option codes Thomas Narten
- Re: [dhcwg] dhcpv6-24: randomization delay before… Thomas Narten
- Re: [dhcwg] dhcpv6-24: randomization delay before… Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Thomas Narten
- Re: [dhcwg] dhcpv6-24: use of anycast Thomas Narten
- Re: [dhcwg] dhcpv6-24: use of anycast Thomas Narten
- Re: [dhcwg] dhcpv6-24: vendor-specific issues Thomas Narten
- Re: [dhcwg] status of draft-ietf-dhc-agent-subnet… Thomas Narten
- Re: [dhcwg] status of draft-ietf-dhc-agent-subnet… Thomas Narten
- Re: [dhcwg] DHC WG charter Thomas Narten
- Re: [dhcwg] DHC WG charter Thomas Narten
- RE: [dhcwg] DHC WG charter Ralph Droms
- Re: [dhcwg] DHC WG charter Thomas Narten
- Re: [dhcwg] DHC WG charter Ralph Droms
- Re: [dhcwg] Agenda items for IETF-59, Seoul Naiming Shen
- Re: [dhcwg] *DRAFT* minutes from WG meeting in Se… Naiming Shen
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Thomas Narten