Re: [Rgchairs] thoughs about the IRTF

"Karen R. Sollins" <sollins@csail.mit.edu> Tue, 02 November 2004 19:58 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 OAA03899; Tue, 2 Nov 2004 14:58:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP53A-0003hK-N7; Tue, 02 Nov 2004 15:14:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP4do-0006C7-E0; Tue, 02 Nov 2004 14:48:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP3lX-00043s-JP for rgchairs@megatron.ietf.org; Tue, 02 Nov 2004 13:52:24 -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 NAA27972 for <rgchairs@ietf.org>; Tue, 2 Nov 2004 13:52:22 -0500 (EST)
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP40g-00026p-Ij for rgchairs@ietf.org; Tue, 02 Nov 2004 14:08:03 -0500
Received: from [18.26.0.27] (tethys.lcs.mit.edu [18.26.0.27]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mercury.lcs.mit.edu (Postfix) with ESMTP id 3A09E872E3; Tue, 2 Nov 2004 13:51:47 -0500 (EST)
Mime-Version: 1.0
X-Sender: sollins@mercury.lcs.mit.edu
Message-Id: <p0610052cbdad78698a29@[18.26.0.27]>
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>
Date: Tue, 2 Nov 2004 13:52:29 -0400
To: Geoff Huston <gih@apnic.net>, Pete Resnick <presnick@qualcomm.com>
From: "Karen R. Sollins" <sollins@csail.mit.edu>
Subject: Re: [Rgchairs] thoughs about the IRTF
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
X-Mailman-Approved-At: Tue, 02 Nov 2004 14:48:27 -0500
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: 92df29fa99cf13e554b84c8374345c17

I am in full agreement with the previous voices that have clarified 
the point that IRTF RFCs should be distinctively identified as part 
of the IRTF processes.  There are at least two important and distinct 
reasons.

1. These are intended to be working papers, requests for comments, 
etc.  It is important that the broad audience out the broad audience 
out there treat them differently.  Too often any RFC is read as a 
"standard".  So, not only should the name be different, but perhaps 
there should be more boilerplate text that clarifies what they are 
(not just an individual submission).

2. This set of documents represents part of the IRTF process and 
contribution.  As such, it is important to identify that, because it 
is part of the definition of the IRTF and its WGs.

			Karen

At 10:41 AM +1100 11/2/04, Geoff Huston wrote:
>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.
>
>regards,
>
>    Geoff
>
>
>
>At 09:09 AM 2/11/2004, Pete Resnick wrote:
>>On 11/2/04 at 9:15 AM +1100, Geoff Huston wrote:
>>
>>>I would be reluctant to confuse this publication stream with 
>>>individual submissions, and I think it would be useful to define a 
>>>clear path via the IRTF Chair (or the IRSG) from the IRTF to the 
>>>RFC Editor to a published document.
>>
>>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.
>>
>>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



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