IETF Logo Mail Archive

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

"Spencer Dawkins" <spencer@mcsr-labs.org> Fri, 20 January 2006 12:55 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 1Ezvo4-0006Uv-DL; Fri, 20 Jan 2006 07:55:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ezvo3-0006UJ-2o for pesci-discuss@megatron.ietf.org; Fri, 20 Jan 2006 07:55:55 -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 HAA10203 for <pesci-discuss@ietf.org>; Fri, 20 Jan 2006 07:54:28 -0500 (EST)
Received: from [216.148.227.153] (helo=rwcrmhc12.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ezvwk-0003Is-Rj for pesci-discuss@ietf.org; Fri, 20 Jan 2006 08:04:57 -0500
Received: from s73602 (c-24-1-104-165.hsd1.tx.comcast.net[24.1.104.165]) by comcast.net (rwcrmhc13) with SMTP id <2006012012554101500aenn3e>; Fri, 20 Jan 2006 12:55:41 +0000
Message-ID: <2f0901c61dc0$a5157110$d0087c0a@china.huawei.com>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: Brian E Carpenter <brc@zurich.ibm.com>, Harald Tveit Alvestrand <harald@alvestrand.no>
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>
Subject: Re: [Pesci-discuss] [Fwd: I-DACTION:draft-davies-pesci-initial-considerations-01.txt]
Date: Fri, 20 Jan 2006 06:54:25 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
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

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