Re: [Rgchairs] thoughs about the IRTF

Harald Tveit Alvestrand <harald@alvestrand.no> Thu, 04 November 2004 12:50 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15536; Thu, 4 Nov 2004 07:50:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPhJv-0002zT-5B; Thu, 04 Nov 2004 08:06:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPgyG-0001P8-S7; Thu, 04 Nov 2004 07:44:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPgr2-0007qN-Eh; Thu, 04 Nov 2004 07:36:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14651; Thu, 4 Nov 2004 07:36:39 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPh6Z-0002YH-5I; Thu, 04 Nov 2004 07:52:43 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 069BA61E97; Thu, 4 Nov 2004 13:36:09 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12059-03; Thu, 4 Nov 2004 13:36:06 +0100 (CET)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 06627621B1; Thu, 4 Nov 2004 13:36:04 +0100 (CET)
Date: Thu, 04 Nov 2004 13:35:49 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: iab@ietf.org
Subject: Re: [Rgchairs] thoughs about the IRTF
Message-ID: <B615900698C87ABA35D70528@B50854F0A9192E8EC6CDA126>
In-Reply-To: <p0610052cbdad78698a29@[18.26.0.27]>
References: <20041029083030.GE2249@james> <Pine.BSI.4.56.0410310022460.17494@tom.iecc.com> <F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no> <6.0.1.1.2.20041102091148.023061e0@kahuna.telstra.net> <p07000c0ebdac640b11ba@[216.43.25.67]> <6.0.1.1.2.20041102103708.0256ad80@kahuna.telstra.net> <p0610052cbdad78698a29@[18.26.0.27]>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: rgchairs@ietf.org
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IRTF research group chairs list <rgchairs.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rgchairs>
List-Post: <mailto:rgchairs@lists.ietf.org>
List-Help: <mailto:rgchairs-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=subscribe>
Sender: rgchairs-bounces@ietf.org
Errors-To: rgchairs-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

I think the point has been made eminently clear now that it makes sense to 
formalize and document the way the IRTF handles documents - if the IAB and 
the RG chairs don't know what the current process is, how can anyone 
else.....?

The point that I see in some need of clarification still is the approval 
process for RG draft publication - should there be some explicit IRTF 
signoff (IRTF chair, IRSG or RG chair seem some possible candidates to give 
it) and have the drafts enter the RFC Editor's queue at the same point as 
IETF drafts, or should they come straight from the RG and enter (as today) 
as individual submissions?

When we reach this stage in other process discussions, I tend to say "do we 
have a volunteer to document this approach as an I-D?" - is that an 
appropriate thing to call for here, Vern?

(see <ftp://ftp.rfc-editor.org/in-notes/rfc-editor/rfc-editor-process.gif> 
for the flowchart I'm thinking about)

                   Harald

_______________________________________________
Rgchairs mailing list
Rgchairs@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/rgchairs