RE: [newtrk] web-based lists of RFCs

<john.loughney@nokia.com> Wed, 06 July 2005 12:25 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dq8y3-0003E6-Va for newtrk-archive@megatron.ietf.org; Wed, 06 Jul 2005 08:25:32 -0400
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11578 for <newtrk-archive@lists.ietf.org>; Wed, 6 Jul 2005 08:25:30 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j66CNqYf008829; Wed, 6 Jul 2005 05:23:52 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j66CNpXs008825; Wed, 6 Jul 2005 05:23:51 -0700 (PDT)
Received: from mgw-ext04.nokia.com (mgw-ext04.nokia.com [131.228.20.96]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j66CNirM008790 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <newtrk@lists.uoregon.edu>; Wed, 6 Jul 2005 05:23:46 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j66CIjtE006579; Wed, 6 Jul 2005 15:18:50 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jul 2005 15:23:36 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jul 2005 15:23:36 +0300
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [newtrk] web-based lists of RFCs
Date: Wed, 06 Jul 2005 15:23:35 +0300
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CE85E@esebe100.NOE.Nokia.com>
Thread-Topic: [newtrk] web-based lists of RFCs
Thread-Index: AcWBhVTuDGncrkXfQeqBOPKU1IxS6QAnt4NQ
From: john.loughney@nokia.com
To: pekkas@netcore.fi, blilly@erols.com
Cc: newtrk@lists.uoregon.edu
X-OriginalArrivalTime: 06 Jul 2005 12:23:36.0427 (UTC) FILETIME=[886E7BB0:01C58225]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by darkwing.uoregon.edu id j66CNorL008819
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: john.loughney@nokia.com
Content-Transfer-Encoding: 8bit

Pekka,


> The work began as draft-duke-tcp-roadmap-00.txt (posted on Feb 2004), 
> the next version was the WG document.
> 
> So you could say from scratch to getting the doc approved probably 
> takes 1-2 years, depending on the interest level of the people working 
> on the technology.
> 
> Always an optimist, I'd say that it could be possible to get these 
> approved in something like 6-9 months, but this requires dedication 
> from the editors, sufficient interest level from the [WG] 
> participants, and resolution skills if tough consensus calls need to 
> be made.
> 
> But as long as you start classifying the RFCs and/or internet-drafts 
> somehow, and add discussion on their applicability etc., I believe the 
> requirement on the time spent is roughly equal.  It's the same sort of 
> issues (editing, getting the community interested, steering towards 
> consensus, etc.) that take time, not the publication format.

There's still another half you forgot to mention - RFC Editor's Queue.
I suppose you are familiar with 
ftp://ftp.isi.edu/internet-drafts/draft-ietf-ipv6-node-requirements-11.txt

Its been in the RFC Editor's queue since 2004/08/26. This document kicked
of a revision of a number of RFC's, which know are in IESG review, meaning
that by the time it is actually published, it will be out of date.  It was
first published as a draft on June 18th, 2002.

Of course, the above document is slightly more complicated that what I would
expect your average ISD would be; but then again, this draft was proceded by
http://www.ietf.org/rfc/rfc3316.txt "Internet Protocol Version 6 (IPv6) for 
Some Second and Third Generation Cellular Hosts" which was first submitted as
an individual submission on July 2, 2001 and finally published as an RFC 
on April 2003, so the WG was primed, so to speak, to discuss the Node Requirements.

YMMV,
John

.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html