Re: draft-klensin-nomcom-term-00.txt

John Leslie <john@jlc.net> Wed, 27 July 2005 14:42 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxn73-0002rf-T5; Wed, 27 Jul 2005 10:42:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxn72-0002ra-EE for ietf@megatron.ietf.org; Wed, 27 Jul 2005 10:42:24 -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 KAA03374 for <ietf@ietf.org>; Wed, 27 Jul 2005 10:42:21 -0400 (EDT)
Received: from mailhost.jlc.net ([199.201.159.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxncI-0007RC-Pr for ietf@ietf.org; Wed, 27 Jul 2005 11:14:44 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104) id E4113E04AD; Wed, 27 Jul 2005 10:42:22 -0400 (EDT)
Date: Wed, 27 Jul 2005 10:42:22 -0400
From: John Leslie <john@jlc.net>
To: Brian E Carpenter <brc@zurich.ibm.com>
Message-ID: <20050727144222.GD99806@verdi>
References: <12ab01c5922f$e6f5bdf0$4b087c0a@DFNJGL21> <42E78869.5020106@zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <42E78869.5020106@zurich.ibm.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: draft-klensin-nomcom-term-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

Brian E Carpenter <brc@zurich.ibm.com> wrote:
> Spencer Dawkins wrote:
> 
>>If there is community consensus that this draft proposes something 
>>reasonable, would we give the draft to the incoming NOMCOM as part of 
>>their instructions and perform a BCP 93 process experiment?
> 
> in answer to your question, I'm sure the answer is no, because the
> two-stage process suggested in the draft will add a significant number
> of weeks to the process, and we would almost certainly have to start
> about two months earlier.

   I'm not at all sure that we can't have sufficient overlap to fit
it all into approximately the existing timeframe, but...

   We shouldn't even _try_ to make this "part of their instructions".
The Nomcom will be aware of this discussion: I'm pretty sure that
someone will make sure all Nomcom members see it. We should let the
Nomcom we're about to assemble consider this and make their own
decision about how much of it to try.

   Then that Nomcom can make recommendations about necessary schedule
changes for the next Nomcom.

--
John Leslie <john@jlc.net>

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