IETF Logo Mail Archive

Re: [Pesci-discuss] [Fwd: I-DACTION:draft-davies-pesci-initial-considerations-01.txt]

Brian E Carpenter <brc@zurich.ibm.com> Mon, 23 January 2006 14:30 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F12id-00045L-9M; Mon, 23 Jan 2006 09:30:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F12ib-00044v-RJ for pesci-discuss@megatron.ietf.org; Mon, 23 Jan 2006 09:30:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22906 for <pesci-discuss@ietf.org>; Mon, 23 Jan 2006 09:29:21 -0500 (EST)
Received: from mtagate4.uk.ibm.com ([195.212.29.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F12jM-0007jw-Ak for pesci-discuss@ietf.org; Mon, 23 Jan 2006 09:31:40 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id k0NELMfw274902 for <pesci-discuss@ietf.org>; Mon, 23 Jan 2006 14:21:26 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k0NEJksw205480 for <pesci-discuss@ietf.org>; Mon, 23 Jan 2006 15:19:46 +0100
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id k0NEJkPE026158 for <pesci-discuss@ietf.org>; Mon, 23 Jan 2006 15:19:46 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av04.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id k0NEJjee026155; Mon, 23 Jan 2006 15:19:45 +0100
Received: from zurich.ibm.com (sig-9-146-217-94.de.ibm.com [9.146.217.94]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id PAA30364; Mon, 23 Jan 2006 15:19:44 +0100
Message-ID: <43D4E5FF.7070509@zurich.ibm.com>
Date: Mon, 23 Jan 2006 15:19:43 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [Pesci-discuss] [Fwd: I-DACTION:draft-davies-pesci-initial-considerations-01.txt]
References: <43C92D1B.8040103@zurich.ibm.com> <Pine.LNX.4.64.0601161542050.5861@netcore.fi> <43CBA9CC.6040601@dial.pipex.com><43D09AC6.7060104@employees.org><A44E27939797290D30CD63E6@svartdal.hjemme.alvestrand.no> <43D0DB18.6020804@zurich.ibm.com> <2f0901c61dc0$a5157110$d0087c0a@china.huawei.com>
In-Reply-To: <2f0901c61dc0$a5157110$d0087c0a@china.huawei.com>
Content-Type: multipart/mixed; boundary="------------050101070502090606050604"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: pesci-discuss@ietf.org
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

I've just submitted an update for the IETF site (attached fyi).

     Brian


Spencer Dawkins wrote:
> From: "Brian E Carpenter" <brc@zurich.ibm.com>
> 
>>
>> My thought is that the spaghetti-like nature of the current documents is
>> actually a problem, especially for newcomers. But it's separate from
>> the core problem. It's why I wrote draft-carpenter-procdoc-roadmap and 
>> why
>> I intend to maintain that draft.
> 
> 
> Just to chime in here, since both the IETF home page and the RFC Editor 
> page point directly to RFC 2026 with no qualifiers as "the Standards 
> Process", it is possible that we are confusing more than newcomers :-(
> 
> Just for fun, follow the "updates/obsoletes" chain for 2026, and see how 
> clear our document structure really is to anyone who doesn't do IETF for 
> a living.
> 
> Spencer
> 

_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss

v2.23.0 | Report a Bug | By Email