IETF Logo Mail Archive

Re: Making the Tao a web page

Russ Housley <housley@vigilsec.com> Fri, 01 June 2012 21:33 UTC

Return-Path: <housley@vigilsec.com>
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 9F79B11E80E0 for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2012 14:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level:
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8syd20r138Ra for <ietf@ietfa.amsl.com>; Fri, 1 Jun 2012 14:33:46 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A0A0D11E80BC for <ietf@ietf.org>; Fri, 1 Jun 2012 14:33:45 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id AE3039A470F for <ietf@ietf.org>; Fri, 1 Jun 2012 17:33:55 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 125aZ64KCYyL for <ietf@ietf.org>; Fri, 1 Jun 2012 17:33:36 -0400 (EDT)
Received: from [10.73.40.255] (unknown [70.42.157.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4BC16F2402F for <ietf@ietf.org>; Fri, 1 Jun 2012 17:33:52 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Making the Tao a web page
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FC8AFA9.1020200@inex.ie>
Date: Fri, 01 Jun 2012 17:33:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C30E960-D656-4651-9AB6-9ECEE5196E3D@vigilsec.com>
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>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 01 Jun 2012 21:33:46 -0000

I have a concern here.  When I did the AD review for this document, I was quite surprised how stale it had become.  For example, the document told people to send I-Ds to the Secretariat for posting instead of pointing to the online I-D submission tool.  If we put it in a wiki, there will be more people that can make update, but the publication process ensure that an end-to-end read takes place when an update published as an RFC.

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?

Russ

v2.26.15 | Report a Bug | By Email | System Status