Re: Making the Tao a web page

Dave Crocker <dhc@dcrocker.net> Mon, 04 June 2012 06:03 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FC921F8547 for <ietf@ietfa.amsl.com>; Sun, 3 Jun 2012 23:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level:
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31X05xNQi8zt for <ietf@ietfa.amsl.com>; Sun, 3 Jun 2012 23:03:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B84021F8542 for <ietf@ietf.org>; Sun, 3 Jun 2012 23:03:01 -0700 (PDT)
Received: from [192.168.2.101] (g231207152.adsl.alicedsl.de [92.231.207.152]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q5462wFP007236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 3 Jun 2012 23:02:59 -0700
Message-ID: <4FCC4F8F.1060800@dcrocker.net>
Date: Mon, 04 Jun 2012 08:02:55 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie> <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org> <4FC8AFA9.1020200@inex.ie> <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com> <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
In-Reply-To: <6.2.5.6.2.20120603145115.09cfc558@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 03 Jun 2012 23:03:00 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 06:03:01 -0000

On 6/4/2012 12:36 AM, SM wrote:
> At 14:33 01-06-2012, Russ Housley wrote:
>> So, I am left with a few questions:
>> - What is the similar forcing function if we use a wiki?
>> - Will the number of people that can make updates eliminate the need
>> for such a forcing function?
>> - Who designates the editor-in-chief of the wiki?
...
>   ...  Instead of discussing the above questions it is easier
> to create an Wiki page and leave it to anyone with a tools login who
> cares to update it.


In effect, the wiki construct becomes a form of incrementally-updatable 
internet draft.  For documents involving procedures rather than 
products, this well might be a better working base than I-Ds...

But with the I-D model superimposed.

That is, perhaps what makes this workable is imposing an editor role 
onto the wiki and assign responsibility for monitoring changes to the 
editors?  (It might even be worth integrating it into the rest of the 
I-D administration environment?)

Note that this still leaves a place for published snapshots as RFCs.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net