Re: [Rgchairs] thoughs about the IRTF

Pete Resnick <presnick@qualcomm.com> Tue, 02 November 2004 03:24 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 WAA19663; Mon, 1 Nov 2004 22:24:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COpWD-0005Oi-DE; Mon, 01 Nov 2004 22:39:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COpAC-00030z-R6; Mon, 01 Nov 2004 22:16:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COoss-0003sJ-OI for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 21:58:58 -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 VAA06614 for <rgchairs@ietf.org>; Mon, 1 Nov 2004 21:58:55 -0500 (EST)
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COp7u-0004ot-CL for rgchairs@ietf.org; Mon, 01 Nov 2004 22:14:30 -0500
Received: from [216.43.25.67] (10.0.2.4) by episteme-software.com with ESMTP (Eudora Internet Mail Server X 3.2.5); Mon, 1 Nov 2004 20:58:27 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p07000c12bdac9700031a@[216.43.25.67]>
In-Reply-To: <6.0.1.1.2.20041102103708.0256ad80@kahuna.telstra.net>
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>
X-Mailer: Eudora [Macintosh version 6.2a9]
Date: Mon, 1 Nov 2004 20:58:25 -0500
To: Geoff Huston <gih@apnic.net>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Rgchairs] thoughs about the IRTF
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, iab@iab.org, 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: 8b30eb7682a596edff707698f4a80f7d

On 11/2/04 at 10:41 AM +1100, Geoff Huston wrote:

>At 09:09 AM 2/11/2004, Pete Resnick wrote:
>>
>>In among all of the other discussions we've been having about the 
>>future of the IRTF, one of the things (at least some of us have) 
>>talked about was a separate "Research" track (akin to the Standards 
>>track) for IRTF documents so that research folks could have some 
>>recognition other than "just another Informational document". 
>>Personally, I think this would be a good thing.
>
>Personally, I agree with this proposition. In my mind IRTF documents 
>are much closer to the original spirit of an actual "request for 
>comment" than our standards track and information documents these 
>days.
>
>It seems to me there are two things here that split off in different 
>directions if we want to pursue this - the creation of a RFC 
>document track for IRTF-sourced documents would probably be a newtrk 
>WG consideration, as far as I can see. The process to follow to get 
>IRTF outputs to the RFC editor directly would be something for the 
>IAB to work through with the RFC Editor and the IRTF chair I would 
>guess.

I don't see how a research track in the RFC series would require any 
action from newtrk. They're working on the IETF track of documents. I 
see no reason why we (as the sponsor/organizer of the IRTF and policy 
approvers of the RFC Editor) can't just ask the RFC Editor to make a 
new track (should we decide that that's what we and the IRTF want).

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

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