Re: Proposed update of Tools Team charter
Bruce Lilly <blilly@erols.com> Tue, 12 July 2005 12:57 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsKKQ-0001Pp-CU; Tue, 12 Jul 2005 08:57:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsKKM-0001Li-DZ for ietf@megatron.ietf.org; Tue, 12 Jul 2005 08:57:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18640 for <ietf@ietf.org>; Tue, 12 Jul 2005 08:57:33 -0400 (EDT)
Received: from ns5a.townisp.com ([216.195.0.140] helo=ns5.townisp.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsKmY-000313-Gs for ietf@ietf.org; Tue, 12 Jul 2005 09:26:43 -0400
Received: from mail.blilly.com (dhcp-0-8-a1-c-fa-f7.cpe.townisp.com [216.49.158.220]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "marty.blilly.com", Issuer "Bruce Lilly" (not verified)) by ns5.townisp.com (Postfix) with ESMTP id 23E3B29948; Tue, 12 Jul 2005 08:57:32 -0400 (EDT)
Received: from marty.blilly.com (marty.blilly.com [192.168.99.98] (may be forged)) by mail.blilly.com with ESMTP id j6CCvVV3019243(8.13.1/8.13.1/mail.blilly.com /etc/sendmail.mc.mail 1.26 2005/06/24 20:47:59) (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) ; Tue, 12 Jul 2005 08:57:31 -0400
Received: from marty.blilly.com (localhost [127.0.0.1]) (authenticated (0 bits)) by marty.blilly.com with ESMTP id j6CCvU0G019242(8.13.1/8.13.1/blilly.com submit.mc 1.3 2005/04/08 12:29:31) (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Tue, 12 Jul 2005 08:57:31 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
To: ietf@ietf.org
Date: Tue, 12 Jul 2005 08:57:29 -0400
User-Agent: KMail/1.8.1
References: <E1DsH1b-0001TX-Tb@newodin.ietf.org>
In-Reply-To: <E1DsH1b-0001TX-Tb@newodin.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200507120857.29356@mail.blilly.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: Proposed update of Tools Team charter
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Tue July 12 2005 05:25, Brian Carpenter wrote (via ietf-announce): > The Tools Team was set up by Harald Alvestrand and has made > good progress (e.g. draft-ietf-tools-draft-submission-09, > which has been approved as an Informational RFC). > > Now it's time to update the team's charter. Please see > the proposed new charter: > > http://tools.ietf.org/charters/charter-2005-06-17.html > > The current charter is at http://tools.ietf.org/charter-page [...] > If you have comments on the new charter, please write to > tools-discuss@ietf.org (or to ietf@ietf.org if you really > have a point for the whole IETF). I have a procedural question: is the intent to follow the rechartering procedures as specified in BCP 25 (RFC 2418) section 5 (which references "the same procedures that the initial chartering does (see section 2)")? If so, where on that process does the proposed new charter stand? In particular, was the ietf-announce message intended to be the "public notice" of BCP 25 section 2.3, and if so was the "new-work" list copied? _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Proposed update of Tools Team charter Bruce Lilly
- Re: Proposed update of Tools Team charter Brian E Carpenter