From mailman-bounces@ietf.org  Mon Nov  1 05:27:25 2004
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 FAA12462
	for <rgchairs-archive@ietf.org>; Mon, 1 Nov 2004 05:27:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COZeE-0003fQ-1T
	for rgchairs-archive@ietf.org; Mon, 01 Nov 2004 05:42:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZ4x-00077d-ML
	for rgchairs-archive@ietf.org; Mon, 01 Nov 2004 05:06:23 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: lists.ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rgchairs-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.1909.1099303353.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:02:33 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your lists.ietf.org
mailing list memberships.  It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@lists.ietf.org) containing just
the word 'help' in the message body, and an email message will be sent
to you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@lists.ietf.org.  Thanks!

Passwords for rgchairs-archive@ietf.org:

List                                     Password // URL
----                                     --------  
rgchairs@lists.ietf.org                  oxazwu    
https://www1.ietf.org/mailman/options/rgchairs/rgchairs-archive%40ietf.org


From rgchairs-bounces@ietf.org  Mon Nov  1 12:32:40 2004
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 MAA06968;
	Mon, 1 Nov 2004 12:32:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COgHo-00059v-S8; Mon, 01 Nov 2004 12:48:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COfhn-0002VN-79; Mon, 01 Nov 2004 12:10:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COX63-0000Qd-Ge
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 02:59: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 CAA03332
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 02:59:22 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COXKu-0008M2-Os
	for rgchairs@ietf.org; Mon, 01 Nov 2004 03:14:45 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id D41A9621F1; Mon,  1 Nov 2004 08:58:51 +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 20803-03; Mon,  1 Nov 2004 08:58:50 +0100 (CET)
Received: from [192.168.1.4] (162.80-203-220.nextgentel.com [80.203.220.162])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3597861AD5; Mon,  1 Nov 2004 08:58:50 +0100 (CET)
Date: Mon, 01 Nov 2004 08:58:50 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John R Levine <johnl@iecc.com>, Vern Paxson <vern@icir.org>
Subject: Re: [Rgchairs] thoughs about the IRTF
Message-ID: <F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 01 Nov 2004 12:10:54 -0500
Cc: 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: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable



--On s=F8ndag, oktober 31, 2004 00:26:09 -0400 John R Levine =
<johnl@iecc.com>=20
wrote:

> I agree with Juergen that the IRTF could use more visibility.  A clearer
> path to publishing informaitional and experimental RFCs would both be
> useful on its own merits and for the visibility issue.

Being somewhat disingenious:

What path could be clearer than "write a good internet-draft, get RG=20
consensus on it, and ask the RFC Editor to publish it"?

I don't believe we can make it much simpler than that. (And the IESG has=20
promised to mostly get out of the way of independent-submission publication =

- gives more responsibility to RG folks to get things right, but less=20
hassle in the publication path)

                      Harald

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


From rgchairs-bounces@ietf.org  Mon Nov  1 15:31:18 2004
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 PAA27489;
	Mon, 1 Nov 2004 15:31:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COj4i-000285-F9; Mon, 01 Nov 2004 15:46:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COicu-0000yj-EC; Mon, 01 Nov 2004 15:18:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COiOD-0003eh-MQ
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 15:02:53 -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 PAA23369
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 15:02:51 -0500 (EST)
Received: from tom.iecc.com ([208.31.42.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COidA-0001Iu-Gj
	for rgchairs@ietf.org; Mon, 01 Nov 2004 15:18:22 -0500
Received: (qmail 28573 invoked from network); 1 Nov 2004 20:02:50 -0000
Received: (ofmipd 127.0.0.1); 1 Nov 2004 20:02:28 -0000
Date: 1 Nov 2004 15:02:50 -0500
Message-ID: <Pine.BSI.4.56.0411011501320.27089@tom.iecc.com>
From: "John R Levine" <johnl@iecc.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
Subject: Re: [Rgchairs] thoughs about the IRTF
In-Reply-To: <F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
	<F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: 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: 08170828343bcf1325e4a0fb4584481c

> What path could be clearer than "write a good internet-draft, get RG
> consensus on it, and ask the RFC Editor to publish it"?

That seems pretty clear.  Once we do that, is it an irtf draft or an
independent submission?  I've gotten conflicting messages recently.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://iecc.com/johnl, Mayor
"I dropped the toothpaste", said Tom, crestfallenly.

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


From rgchairs-bounces@ietf.org  Mon Nov  1 17:09:35 2004
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 RAA10564;
	Mon, 1 Nov 2004 17:09:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COkbq-0005mw-H4; Mon, 01 Nov 2004 17:25:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COk5p-0003i1-8U; Mon, 01 Nov 2004 16:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COj2G-0006Fb-Ib
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 15:44:16 -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 PAA28844
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 15:44:15 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COjHD-0002OH-Vs
	for rgchairs@ietf.org; Mon, 01 Nov 2004 15:59:45 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0D1CD6224D; Mon,  1 Nov 2004 21:43:44 +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 04207-04; Mon,  1 Nov 2004 21:43:42 +0100 (CET)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 97A7361AD5; Mon,  1 Nov 2004 21:43:40 +0100 (CET)
Date: Mon, 01 Nov 2004 21:37:57 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John R Levine <johnl@iecc.com>
Subject: Re: [Rgchairs] thoughs about the IRTF
Message-ID: <6F8930B12DB00FCA154F29BB@B50854F0A9192E8EC6CDA126>
In-Reply-To: <Pine.BSI.4.56.0411011501320.27089@tom.iecc.com>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
	<F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
	<Pine.BSI.4.56.0411011501320.27089@tom.iecc.com>
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: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: 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: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit



--On 1. november 2004 15:02 -0500 John R Levine <johnl@iecc.com> wrote:

>> What path could be clearer than "write a good internet-draft, get RG
>> consensus on it, and ask the RFC Editor to publish it"?
>
> That seems pretty clear.  Once we do that, is it an irtf draft or an
> independent submission?  I've gotten conflicting messages recently.

IRTF drafts are treated like independent submissions - there are no special 
processing rules for them. Do we need any?

>
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for
> Dummies", Information Superhighwayman wanna-be, http://iecc.com/johnl,
> Mayor "I dropped the toothpaste", said Tom, crestfallenly.
>
>





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


From rgchairs-bounces@ietf.org  Mon Nov  1 17:25:33 2004
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 RAA13222;
	Mon, 1 Nov 2004 17:25:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COkrH-0006bn-0y; Mon, 01 Nov 2004 17:41:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COk9k-0006IK-HG; Mon, 01 Nov 2004 16:56:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COjkY-0002V0-N2
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 16:30:02 -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 QAA06029
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 16:30:01 -0500 (EST)
Received: from tom.iecc.com ([208.31.42.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COjzU-0004Yt-CB
	for rgchairs@ietf.org; Mon, 01 Nov 2004 16:45:31 -0500
Received: (qmail 10002 invoked from network); 1 Nov 2004 21:29:57 -0000
Received: (ofmipd 127.0.0.1); 1 Nov 2004 21:29:35 -0000
Date: 1 Nov 2004 16:29:57 -0500
Message-ID: <Pine.BSI.4.56.0411011629270.9799@tom.iecc.com>
From: "John R Levine" <johnl@iecc.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
Subject: Re: [Rgchairs] thoughs about the IRTF
In-Reply-To: <6F8930B12DB00FCA154F29BB@B50854F0A9192E8EC6CDA126>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
	<F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
	<Pine.BSI.4.56.0411011501320.27089@tom.iecc.com>
	<6F8930B12DB00FCA154F29BB@B50854F0A9192E8EC6CDA126>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 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: 856eb5f76e7a34990d1d457d8e8e5b7f

> > That seems pretty clear.  Once we do that, is it an irtf draft or an
> > independent submission?  I've gotten conflicting messages recently.
>
> IRTF drafts are treated like independent submissions - there are no special
> processing rules for them. Do we need any?

Just that they're called draft-irtf-group-whatever so people who are
looking for them can find them.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://iecc.com/johnl, Mayor
"I dropped the toothpaste", said Tom, crestfallenly.

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


From rgchairs-bounces@ietf.org  Mon Nov  1 19:02:35 2004
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 TAA24065;
	Mon, 1 Nov 2004 19:02:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COmNC-00014z-9g; Mon, 01 Nov 2004 19:18:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COlj9-0004d2-8P; Mon, 01 Nov 2004 18:36:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COkTZ-0004IW-Ih
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 17:16:33 -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 RAA11711
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 17:16:32 -0500 (EST)
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COkiY-000643-G7
	for rgchairs@ietf.org; Mon, 01 Nov 2004 17:32:03 -0500
Received: from gihz1.apnic.net (issquid.telstra.net [203.50.0.177])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id iA1MF2ch049467;
	Tue, 2 Nov 2004 09:15:02 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.0.1.1.2.20041102091148.023061e0@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 02 Nov 2004 09:15:09 +1100
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
        John R Levine <johnl@iecc.com>, Vern Paxson <vern@icir.org>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Rgchairs] thoughs about the IRTF
In-Reply-To: <F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
	<F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 01 Nov 2004 18:36:41 -0500
Cc: 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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable

I would be reluctant to confuse this publication stream with individual=20
submissions, and I think it would be useful to define a clear path via the=
=20
IRTF Chair (or the IRSG) from the IRTF to the RFC Editor to a published=20
document.


    Geoff



At 06:58 PM 1/11/2004, Harald Tveit Alvestrand wrote:


>--On s=F8ndag, oktober 31, 2004 00:26:09 -0400 John R Levine=20
><johnl@iecc.com> wrote:
>
>>I agree with Juergen that the IRTF could use more visibility.  A clearer
>>path to publishing informaitional and experimental RFCs would both be
>>useful on its own merits and for the visibility issue.
>
>Being somewhat disingenious:
>
>What path could be clearer than "write a good internet-draft, get RG=20
>consensus on it, and ask the RFC Editor to publish it"?
>
>I don't believe we can make it much simpler than that. (And the IESG has=20
>promised to mostly get out of the way of independent-submission=20
>publication - gives more responsibility to RG folks to get things right,=20
>but less hassle in the publication path)
>
>                      Harald
>



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


From rgchairs-bounces@ietf.org  Mon Nov  1 19:02:45 2004
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 TAA24083;
	Mon, 1 Nov 2004 19:02:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COmNM-00015C-D0; Mon, 01 Nov 2004 19:18:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COlj9-0004dE-EI; Mon, 01 Nov 2004 18:36:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COl8j-0008Mr-9C
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 17:59:05 -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 RAA16432
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 17:59:03 -0500 (EST)
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COlNi-0007TW-K1
	for rgchairs@ietf.org; Mon, 01 Nov 2004 18:14:35 -0500
Received: from gihz1.apnic.net (issquid.telstra.net [203.50.0.177])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id iA1Mvlch050618;
	Tue, 2 Nov 2004 09:57:48 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.0.1.1.2.20041102091527.023a6ec0@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 02 Nov 2004 09:17:39 +1100
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
        John R Levine <johnl@iecc.com>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Rgchairs] thoughs about the IRTF
In-Reply-To: <6F8930B12DB00FCA154F29BB@B50854F0A9192E8EC6CDA126>
References: <20041029083030.GE2249@james>
	<Pine.BSI.4.56.0410310022460.17494@tom.iecc.com>
	<F308DD21C5FEBD44F7D97DCC@askvoll.hjemme.alvestrand.no>
	<Pine.BSI.4.56.0411011501320.27089@tom.iecc.com>
	<6F8930B12DB00FCA154F29BB@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-Mailman-Approved-At: Mon, 01 Nov 2004 18:36:41 -0500
Cc: 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: 9466e0365fc95844abaf7c3f15a05c7d

At 07:37 AM 2/11/2004, Harald Tveit Alvestrand wrote:


>--On 1. november 2004 15:02 -0500 John R Levine <johnl@iecc.com> wrote:
>
>>>What path could be clearer than "write a good internet-draft, get RG
>>>consensus on it, and ask the RFC Editor to publish it"?
>>
>>That seems pretty clear.  Once we do that, is it an irtf draft or an
>>independent submission?  I've gotten conflicting messages recently.
>
>IRTF drafts are treated like independent submissions - there are no 
>special processing rules for them. Do we need any?

I would assert that we do. This is a replay of the same old conversation 
about publication of individual submissions, so I will not repeat all the 
content, but I believe that the IRTF is far better served by a defined 
publication process that does not simply say 'these are individual submissions'

Geoff





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


From rgchairs-bounces@ietf.org  Mon Nov  1 19:02:55 2004
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 TAA24104;
	Mon, 1 Nov 2004 19:02:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COmNT-00015S-PY; Mon, 01 Nov 2004 19:18:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COlj9-0004dX-K7; Mon, 01 Nov 2004 18:36:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COlJ5-0001xq-NO
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 18:09:47 -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 SAA18205
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 18:09:45 -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 1COlY4-0007rN-CU
	for rgchairs@ietf.org; Mon, 01 Nov 2004 18:25:17 -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 17:09:10 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p07000c0ebdac640b11ba@[216.43.25.67]>
In-Reply-To: <6.0.1.1.2.20041102091148.023061e0@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>
X-Mailer: Eudora [Macintosh version 6.2a9]
Date: Mon, 1 Nov 2004 17:09:08 -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: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Mon, 01 Nov 2004 18:36:41 -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: 7655788c23eb79e336f5f8ba8bce7906

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


From rgchairs-bounces@ietf.org  Mon Nov  1 19:19:36 2004
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 TAA25203;
	Mon, 1 Nov 2004 19:19:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COmde-0001TB-Rr; Mon, 01 Nov 2004 19:35:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COmB9-0003xP-4z; Mon, 01 Nov 2004 19:05:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COlpC-0000D9-U8
	for rgchairs@megatron.ietf.org; Mon, 01 Nov 2004 18:42:59 -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 SAA21516
	for <rgchairs@ietf.org>; Mon, 1 Nov 2004 18:42:56 -0500 (EST)
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COm4C-0000GP-IY
	for rgchairs@ietf.org; Mon, 01 Nov 2004 18:58:29 -0500
Received: from gihz1.apnic.net (issquid.telstra.net [203.50.0.177])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id iA1NfVcj052629;
	Tue, 2 Nov 2004 10:41:32 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.0.1.1.2.20041102103708.0256ad80@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 02 Nov 2004 10:41:13 +1100
To: Pete Resnick <presnick@qualcomm.com>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Rgchairs] thoughs about the IRTF
In-Reply-To: <p07000c0ebdac640b11ba@[216.43.25.67]>
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]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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: 9ed51c9d1356100bce94f1ae4ec616a9

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


From rgchairs-bounces@ietf.org  Mon Nov  1 22:24:05 2004
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


From rgchairs-bounces@ietf.org  Tue Nov  2 14:58:59 2004
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


From rgchairs-bounces@ietf.org  Tue Nov  2 15:24:46 2004
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 PAA07271;
	Tue, 2 Nov 2004 15:24:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP5S7-0004No-Vp; Tue, 02 Nov 2004 15:40:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP4zI-0007Ex-Gp; Tue, 02 Nov 2004 15:10:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP4dJ-0005rj-4l
	for rgchairs@megatron.ietf.org; Tue, 02 Nov 2004 14:47:57 -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 OAA02906
	for <rgchairs@ietf.org>; Tue, 2 Nov 2004 14:47:55 -0500 (EST)
Received: from cougar.icir.org ([192.150.187.76])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP4sT-0003S7-NP
	for rgchairs@ietf.org; Tue, 02 Nov 2004 15:03:38 -0500
Received: from cougar.icir.org (localhost [127.0.0.1])
	by cougar.icir.org (8.12.11/8.12.8) with ESMTP id iA2Jlgbi009738;
	Tue, 2 Nov 2004 11:47:47 -0800 (PST)
	(envelope-from floyd@cougar.icir.org)
Message-Id: <200411021947.iA2Jlgbi009738@cougar.icir.org>
To: "John R Levine" <johnl@iecc.com>
From: Sally Floyd <floyd@icir.org>
Subject: Re: [Rgchairs] thoughs about the IRTF 
Date: Tue, 02 Nov 2004 11:47:42 -0800
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Tue, 02 Nov 2004 15:10:39 -0500
Cc: 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: 2409bba43e9c8d580670fda8b695204a

>> IRTF drafts are treated like independent submissions - there are no special
>> processing rules for them. Do we need any?
>
>Just that they're called draft-irtf-group-whatever so people who are
>looking for them can find them.

That already happens with internet drafts: internet-drafts
listed under individual submissions include:
 draft-irtf-asrg-lmap-discussion-01.txt,
 draft-irtf-routing-history-01.txt,
 draft-irtf-routing-reqs-03.txt
 draft-irtf-aaaarch-generic-policy-06.txt,
 draft-irtf-dtnrg-bundle-spec-02.txt,
and more.  

It sounds like we would prefer them to be listed on the web page
at "http://www.ietf.cnri.reston.va.us/1id-abstracts.html" separately
under irtf, or under the RG, even though they are treated as
individual submissions.

- Sally


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


From rgchairs-bounces@ietf.org  Thu Nov  4 07:50:27 2004
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


From rgchairs-bounces@ietf.org  Thu Nov  4 13:03:46 2004
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 NAA16713;
	Thu, 4 Nov 2004 13:03:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPmDB-0002g9-DU; Thu, 04 Nov 2004 13:19:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPlhw-0000Q9-UY; Thu, 04 Nov 2004 12:47:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPlUF-0006D1-1P; Thu, 04 Nov 2004 12:33:28 -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 MAA14343;
	Thu, 4 Nov 2004 12:33:24 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPljo-0001wW-5m; Thu, 04 Nov 2004 12:49:32 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iA4HWfi11163;
	Thu, 4 Nov 2004 09:32:41 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA03776;
	Thu, 4 Nov 2004 09:32:41 -0800 (PST)
Date: Thu, 4 Nov 2004 09:32:41 -0800 (PST)
Message-Id: <200411041732.JAA03776@gra.isi.edu>
To: iab@ietf.org, harald@alvestrand.no
Subject: Re: [Rgchairs] thoughs about the IRTF
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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: 69a74e02bbee44ab4f8eafdbcedd94a1


  *> 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?
  *> 

The RFC Editor would certainly like some additional oversight of IRTF
document quality before they reach us, no matter what the process is.
Frankly, the quality of some IRTF-originated documents in the past several
years has been disappointing and required a lot of editing to reach
an acceptable level.  Since the authors are researchers, you would expect
publication-quality documentation to emerge, but some of the submissions
would not pass muster for any academic publication I know of.

Bob Braden for the RFC Editor

  *> 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
  *> 

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


From rgchairs-bounces@ietf.org  Wed Nov 10 08:19:45 2004
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 IAA05441;
	Wed, 10 Nov 2004 08:19:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRsP0-0001jz-Ol; Wed, 10 Nov 2004 08:20:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRsKL-0006eo-J7; Wed, 10 Nov 2004 08:15:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRsH1-0006CP-4n
	for rgchairs@megatron.ietf.org; Wed, 10 Nov 2004 08:12:31 -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 IAA04733
	for <rgchairs@ietf.org>; Wed, 10 Nov 2004 08:12:29 -0500 (EST)
From: avri@psg.com
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRsHy-0001XM-Im
	for rgchairs@ietf.org; Wed, 10 Nov 2004 08:13:30 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.41 (FreeBSD))
	id 1CRsGz-000LKd-Fm; Wed, 10 Nov 2004 13:12:29 +0000
In-Reply-To: <B615900698C87ABA35D70528@B50854F0A9192E8EC6CDA126>
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]>
	<B615900698C87ABA35D70528@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2620EAAC-331A-11D9-9B32-000393CC2112@psg.com>
Content-Transfer-Encoding: 7bit
Subject: Re: [Rgchairs] thoughs about the IRTF
Date: Wed, 10 Nov 2004 08:12:18 -0500
To: rgchairs@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: rajeev.koodli@nokia.com
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.3 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: 7bit


On 4 nov 2004, at 07.35, Harald Tveit Alvestrand wrote:

> 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?
>

I have been in favor of an IRTF process for documents for a while now 
and I am happy to see the discussion get as far as it has.  I am 
certainly willing to work with others in documenting such a process as 
an I-D that gets submitted after IETF week.  I would think, though that 
we should come to an agreement on the general structure of that 
proposal before any of us submit it for further review.

In terms of thinking about a procedure, it seems reasonable that there 
should be a wider review that just that by one research group.

So as a first cut at a process, how about:

- RG documents would have an RG last call.

- Each research group that intends to send documents to the RFC editor 
as IRTF documents should set up a review team (of maybe 3 individuals) 
that would need to do a detailed public review of any document before 
submission (these could be permanent groups or set up per draft).  The 
review team could work with the author/editor of the document to bring 
it up to a point where they could send the RG chair a recommendation 
regarding the document.

- After that review, it would be up to the RG chair to decide on 
whether to submit documents to an IRSG and IAB last call or to inform 
the authors that the document was being rejected at that point.

- in the case of the IRSG/IAB LC it would be up to the RG chair to 
coordinate with the document author(s)/editor to deal with any of the 
issues that came out of that LC.

- After attempting to resolve, and hopefully resolving, any issues that 
came up in the IRSG/IAB LC, the RG chair would decide on whether to 
approve the submission to the RFC editor.

- If approving, the RG chair would then send notification to the RFC 
editor, describing specifics of the edit process, e.g. names of 
reviewers, location of the reviews.

- the Document would enter the RFC editor process at the same point 
where IESG/IAB documents enter and would be demarcated by IRTF branding 
language.


Questions I still have:

- I thought of including the IESG in the IRSG/IAB LC but, since they 
are represented in the IAB by the IETF chair and IESG liaison, figured 
this would give them access to the LC.  Since the IRTF is peer to the 
IESG, I did not think it necessarily made sense to subject IRTF work to 
IESG approval.  I am assuming, though, that Standards/BCPs are still 
not in the IRTF charter and thus could not be submitted by the IRTF - 
these belong to the IESG.  This process would apply only to 
informational and Experimental RFCs.

- Would we need some exception process for submissions where the RG 
chair was the author, especially for an RG with a single chair?

comments?

a.


(note I left the IAB off this reply, since i figured the RG chairs 
should first decide on what we want to suggest) 


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


From rgchairs-bounces@ietf.org  Fri Nov 12 14:05:22 2004
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 OAA02545;
	Fri, 12 Nov 2004 14:05:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSgkz-0008EN-AF; Fri, 12 Nov 2004 14:06:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSgcK-0002K7-EN; Fri, 12 Nov 2004 13:57:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSgbA-0001hg-7X
	for rgchairs@megatron.ietf.org; Fri, 12 Nov 2004 13:56: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 NAA01786
	for <rgchairs@ietf.org>; Fri, 12 Nov 2004 13:56:38 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSgca-000807-FF
	for rgchairs@ietf.org; Fri, 12 Nov 2004 13:58:09 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iACISF927314;
	Fri, 12 Nov 2004 10:28:15 -0800
X-mProtect: <200411121828> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com smtpdIN4LXu; Fri, 12 Nov 2004 10:28:14 PST
Received: from iprg.nokia.com (localhost [127.0.0.1]) by rajeev.iprg.nokia.com
	(8.9.3/8.6.12) with ESMTP id KAA51822;
	Fri, 12 Nov 2004 10:55:54 -0800 (PST)
Message-ID: <4195073A.D2B7D2BB@iprg.nokia.com>
Date: Fri, 12 Nov 2004 10:55:54 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: avri@psg.com
Subject: Re: [Rgchairs] thoughs about the IRTF
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]>
	<B615900698C87ABA35D70528@B50854F0A9192E8EC6CDA126>
	<2620EAAC-331A-11D9-9B32-000393CC2112@psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit
Cc: rajeev.koodli@nokia.com, rgchairs@ietf.org
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: rajeev@iprg.nokia.com
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: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: 7bit


Hello Avri,

I am glad we are taking this up after a lull. I hope
we do formalize a process this time. To that extent
I request Vern to proceed with this proposal unless
others speak up :-)

Some comments below.


avri@psg.com wrote:

> In terms of thinking about a procedure, it seems reasonable that there
> should be a wider review that just that by one research group.
>

Agree. There is _quite a bit of_ confusion in the community
about what IRTF documents mean. Even some proment folks have asked
me if there are any IRTF RFCs. Moreover, in our RG (MobOpts), folks
are keen on getting a formal review and status for their contributions.

>
> So as a first cut at a process, how about:
>
> - RG documents would have an RG last call.
>

Right. However, which documents are made RG docs are
up to each RG.

>
> - Each research group that intends to send documents to the RFC editor
> as IRTF documents should set up a review team (of maybe 3 individuals)
> that would need to do a detailed public review of any document before
> submission (these could be permanent groups or set up per draft).  The
> review team could work with the author/editor of the document to bring
> it up to a point where they could send the RG chair a recommendation
> regarding the document.
>

The review team is an opportunity to widen the awareness of RG work.
We could request IETF folks and-or academia.
Indeed, at the Mobopts meeting, we announced that we would proceed
with such a structure for a couple of documents.


>
> - After that review, it would be up to the RG chair to decide on
> whether to submit documents to an IRSG and IAB last call or to inform
> the authors that the document was being rejected at that point.
>

Check.

>
> - in the case of the IRSG/IAB LC it would be up to the RG chair to
> coordinate with the document author(s)/editor to deal with any of the
> issues that came out of that LC.
>

In Mobopts, we have been a little selective in picking which areas we
would like to shepherd. We had quite a few drafts submitted over the
year. One thing we all could consider in the interest of producing
high-quality documents within a reasonable timeframe and load (on
IRSG/IAB/RFC editor), is to arrive at an appropriate internal review
before making a doc an RG doc.


>
> - After attempting to resolve, and hopefully resolving, any issues that
> came up in the IRSG/IAB LC, the RG chair would decide on whether to
> approve the submission to the RFC editor.
>
> - If approving, the RG chair would then send notification to the RFC
> editor, describing specifics of the edit process, e.g. names of
> reviewers, location of the reviews.
>
> - the Document would enter the RFC editor process at the same point
> where IESG/IAB documents enter and would be demarcated by IRTF branding
> language.
>

I would suggest adding a paragraph towards the end that describes the
peer review process in the eventual RFC itself.


>
> Questions I still have:
>
> - I thought of including the IESG in the IRSG/IAB LC but, since they
> are represented in the IAB by the IETF chair and IESG liaison, figured
> this would give them access to the LC.  Since the IRTF is peer to the
> IESG, I did not think it necessarily made sense to subject IRTF work to
> IESG approval.  I am assuming, though, that Standards/BCPs are still
> not in the IRTF charter and thus could not be submitted by the IRTF -
> these belong to the IESG.  This process would apply only to
> informational and Experimental RFCs.
>

We ought to ensure that IESG is informed. However, I am not sure
if we would like them formally involved in the review process except
of course that a review team picked could consist of one
or more IESG members themselves. Nor am I sure if they would like
to be formally involved :-)


>
> - Would we need some exception process for submissions where the RG
> chair was the author, especially for an RG with a single chair?
>

hmm.. I would leave it for each chair to exercise good judgement.

Thanks,

-Rajeev


>
> comments?
>
> a.
>
> (note I left the IAB off this reply, since i figured the RG chairs
> should first decide on what we want to suggest)
>
> _______________________________________________
> 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


From rgchairs-bounces@ietf.org  Fri Nov 12 14:09:21 2004
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 OAA02875;
	Fri, 12 Nov 2004 14:09:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSgos-0008Ky-J1; Fri, 12 Nov 2004 14:10:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSgmb-0004hN-M5; Fri, 12 Nov 2004 14:08:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSglD-0004Pf-51; Fri, 12 Nov 2004 14:07:03 -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 OAA02718;
	Fri, 12 Nov 2004 14:07:01 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSgmc-0008H5-Jm; Fri, 12 Nov 2004 14:08:32 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iACIcd607036;
	Fri, 12 Nov 2004 10:38:39 -0800
X-mProtect: <200411121838> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90)
	by darkstar.iprg.nokia.com smtpdLpVJad; Fri, 12 Nov 2004 10:38:37 PST
Received: from iprg.nokia.com (localhost [127.0.0.1]) by rajeev.iprg.nokia.com
	(8.9.3/8.6.12) with ESMTP id LAA51839;
	Fri, 12 Nov 2004 11:06:18 -0800 (PST)
Message-ID: <419509AA.F1BDE8BB@iprg.nokia.com>
Date: Fri, 12 Nov 2004 11:06:18 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: [Rgchairs] thoughs about the IRTF
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]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, iab@iab.org,
        rgchairs@ietf.org, Geoff Huston <gih@apnic.net>
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: rajeev@iprg.nokia.com
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: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

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.
>

I definitely agree (again). This ("Research" track RFC)
provides us means to inform the community of a peer review
process and offer a "status" for refereed work. Quite a few folks,
especially from academia, are hesitant to bring in contributions
exactly due to this existing deficiency!

Regards,

-Rajeev





>
> 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


