Making the Tao a web page

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 31 May 2012 23:04 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 28EC321F8636 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.019
X-Spam-Level:
X-Spam-Status: No, score=-102.019 tagged_above=-999 required=5 tests=[AWL=0.580, 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 hyX5ux2AXIdV for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:04:31 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8B70321F8630 for <ietf@ietf.org>; Thu, 31 May 2012 16:04:31 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4VN4UDt057855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 31 May 2012 16:04:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Making the Tao a web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CE474406564976FC0A885D95@PST.JCK.COM>
Date: Thu, 31 May 2012 16:04:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
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: Thu, 31 May 2012 23:04:32 -0000

On May 31, 2012, at 8:19 AM, John C Klensin wrote:

> (1) Establish the Tao as a modified Wiki, complete with live
> HTML links to relevant documents and other relevant
> discussions.. Provide some mechanism for comments to the editor
> or even discussion that works better than the RFC Errata
> process.  Turn maintenance of that page over to a volunteer or
> two (ideally someone young enough to learn a lot from the
> process) or the Secretariat.   Before someone says "cost",
> please calculate the costs to the community of an extended Last
> Call in which people debate details of wording.
> 
> (2) Appoint Paul as chair of an editorial committee with zero or
> more additional members to be appointed at his discretion
> subject to advice and consent of the IESG.  That committee gets
> to consider whether to make changes.  If they get it wrong, they
> are subject to the community's normal forms of abuse and, in
> principle, appeals.  That could add a bit of work for the IESG
> but I suggest only a bit and less than running a Last Call.
> 
> (3) Replace/ obsolete RFC 4677 by a document modeled on RFC
> 5000.  I.e., it should explain why we are maintaining the Tao as
> one or more web pages and should provide a durable pointer to
> how the web page can be found.


Works for me, other than it should not be a "wiki". It should have one editor who takes proposed changes from the community the same way we do it now. Not all suggestions from this community, even from individuals in the leadership, are ones that should appear in such a document.

Simpler than the above: make it a web page (as Brian points out, we already have a good URL), have one editor, have one leadership person who approves non-trivial changes (I think "IETF Chair" fits here well), have a "last modified" date on it, and update it as needed. If there is consensus in the community to do this, I'm happy to take on the HTMLizing and skip the RFCizing for this round.

--Paul Hoffman