Re: Making the Tao a web page

SM <> Mon, 04 June 2012 05:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4D93B21F8873 for <>; Sun, 3 Jun 2012 22:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7EdubJOTbpnL for <>; Sun, 3 Jun 2012 22:49:22 -0700 (PDT)
Received: from ( [IPv6:2001:470:f329:1::1]) by (Postfix) with ESMTP id B8EDC21F8869 for <>; Sun, 3 Jun 2012 22:49:15 -0700 (PDT)
Received: from (IDENT:sm@localhost []) (authenticated bits=0) by (8.14.5/8.14.5) with ESMTP id q545n9l7010166; Sun, 3 Jun 2012 22:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail2010; t=1338788953;; bh=11a4NCqLyLPtCfnAEvUWmkUH/C+qt0H+XlSf409JuNg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KygaP0U4bttwFEOxz874SNKwj1vEgF/qG0NfgynwOD+9xX4E7UcBGBZvp5x3r+Ryg MLY8QtkCs+4qpQG9//NZffH7X2GQe4xSbSDP2hSRXWk4ZHVvdJSCQ7yEg6Cag5QZZO slHt96QDhm261z7tmgU4bVcF3IfMR+v8AoSZTuFs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail; t=1338788953;; bh=11a4NCqLyLPtCfnAEvUWmkUH/C+qt0H+XlSf409JuNg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2RLoGpCVpQe6P3aS8fbAQgbCPEWDo+ntBUcYIyDywWv18tdu5HddRIictsP+kV/Hm Jll06Hp6uzOrfi3PetLqrxu6rC5YXHMw+UivKVHyLHIlnIgY6sIUQ7JgOSrcSvQzA9 SBmc9DHKFODsu80MnYUQsxBNozOVmS6SHcPG9o2s=
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version
Date: Sun, 03 Jun 2012 22:18:54 -0700
To: John C Klensin <>
From: SM <>
Subject: Re: Making the Tao a web page
In-Reply-To: <35398D42C139212863F6D771@PST.JCK.COM>
References: <> <CE474406564976FC0A885D95@PST.JCK.COM> <> <> <> <> <> <> <35398D42C139212863F6D771@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: IETF <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jun 2012 05:49:24 -0000

Hi John,
At 18:34 03-06-2012, John C Klensin wrote:
>I don't think that is a fair comparison.  First of all, the Last
>Call spawned the whole thread about colloquial language.  I
>don't have any way to know how many of those who participated in
>that thread read all the way through the document and even less
>way to guess how many people were enough turned off by it to
>lose interest in the Last Call, maybe after having read the
>document.  Second and more important, my suggestion that we go

Fair enough.  My guess was that the Last Call was not really a Last Call. :-)

>in the direction of a web page or wiki spawned a separate thread
>that is more about the philosophy of how to handle the document
>rather than about the detailed content of the document itself.
>Again, I have no idea how many people other than myself looked
>through the document, decided that "publish as RFC?" was the
>wrong question, and as the result of that decision, concluded
>that my time was better spent on medium and editorial process
>than on reporting specific document comments.  So you don't know
>to what extent I, or anyone else in the "making it a web page"
>threads read the document through either.


At 18:14 03-06-2012, John C Klensin wrote:
>Well, as long as the document is informational and an overview,
>I think that can be accomplished as easily with a web page, an
>editor who can be trusted to exercise a certain amount of good
>sense (and whose intentions are trusted) and a process for
>forcing a review if needed.   The thing that bothers me about
>trying to do this by RFC is that the entire community then
>wastes a huge amount of time debating the choice and style of
>words and relatively minor details, after which everyone runs
>out of energy to make further changes for years (other than
>posting I-Ds on which there are no real controls, even an appeal
>process (not that I'd expect Paul to ignore input)).   If we go
>the web page and editor route, expect revisions only when real
>problems are identified and otherwise do a review every year or
>so, I think we can get a pretty good balance between the
>slowness of the RFC-and-community-consensus process and the
>difficulties of the Wiki one.

In 1994 it was mentioned that due to the nature of the document it 
can become outdated quite quickly.  The web page approach was 
recommended.  The EDU Team ( ) could be an 
alternative to take on the task.