Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF

Niels ten Oever <mail@nielstenoever.net> Thu, 14 April 2022 15:21 UTC

Return-Path: <mail@nielstenoever.net>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4F23A1BCF; Thu, 14 Apr 2022 08:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Duq_T8fXEoCi; Thu, 14 Apr 2022 08:21:10 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C08B63A1BD0; Thu, 14 Apr 2022 08:21:09 -0700 (PDT)
In-Reply-To: <BD1AA00F-A0B6-4FB1-8BC8-7AC0732E7038@kuehlewind.net>
References: <905c834c-30d7-ede7-6ea1-a5b200a249d7@nielstenoever.net> <45a73c1d-0564-10a6-4243-bf1a209da307@gmail.com> <0C41A5AD-CEFB-4A37-9229-64C03723193F@akamai.com> <c9679cee-afa4-f7d4-80a1-83e635d8ad26@gmail.com> <FE38E0F3-C368-42B6-9FD8-2804C38EC7E1@eggert.org> <62445876-1CCA-4D1A-9E30-00E7EDDEE130@ietf.org> <78BF279C-DEED-42BD-897D-1BC3DC972DE2@akamai.com> <BD1AA00F-A0B6-4FB1-8BC8-7AC0732E7038@kuehlewind.net>
X-Referenced-Uid: 41716
Thread-Topic: Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF
User-Agent: Android
X-Is-Generated-Message-Id: true
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----PEM3IIIX1W2N841Y6W1DGW00BVIYRN"
Content-Transfer-Encoding: 7bit
From: Niels ten Oever <mail@nielstenoever.net>
Date: Thu, 14 Apr 2022 16:20:56 +0100
To: Mirja Kuehlewind <ietf@kuehlewind.net>
CC: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Jay Daley <exec-director@ietf.org>, "tao-discuss@ietf.org" <tao-discuss@ietf.org>, IESG <iesg@ietf.org>, Lars Eggert <lars@eggert.org>, Greg Wood <ghwood@staff.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <4cd18fef-7621-48de-b7b6-c8f6ce8a9142@nielstenoever.net>
X-Authenticated-As-Hash: f1842a279235a42f6aa2a2a81130733515c5a4ec
X-Virus-Scanned: by clamav at smarthost1.greenhost.nl
X-Scan-Signature: 71c358205736690f5000c0a682c32dd6
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/aA3Av9A7t5akv7JtL9WWtRiKld4>
Subject: Re: [tao-discuss] Review Request for Possible Revision of the Tao of the IETF
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 15:21:15 -0000

Thank you for this. I fully agree. The name 'Tao' is not very helpful and the document itself is too long (something which we tried to address). 

However, I do think it is useful to have a document people can reference which holds the main processes and procedures of the IETF which is also citeable. This would be an argument to make the Tao (which would then not be called 'Tao' anymore) an RFC and have smaller more accessible bits on the website.

Best,

Niels

On 14 Apr 2022, 16:03, at 16:03, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>I would like to note that there is some kind of tradition or cultural
>identity of this community connected to the Tao. However having said
>this, Jay, I think your analysis is right: it doesn’t serve the
>intended audience well and there is not one intended audience. I’m all
>in to reorganise all content related to participation on the webpage in
>a more useful way but then let’s do that and just not call it Tao
>anymore.
>
>> On 14. Apr 2022, at 16:53, Salz, Rich
><rsalz=40akamai.com@dmarc.ietf.org> wrote:
>> 
>> Very nice analysis!
>> 
>>>   While I admire the effort that has gone into the Tao, I think we
>need to move on from this style of documentation.  Replacing it with
>several smaller documents/sites/pages would be much more useful: "Guide
>to the role and structure of the IETF", "Guide to participating in IETF
>working groups", "Guide to making the most of IETF meetings", and so
>on.
>> 
>> Works for me.  I am happy to completely stop working on it.  Although
>what's on the website is seriously cringe-worthy. How that should be
>addressed I leave to you. I note that the RFC requiring IESG review is
>informational, not even BCP. Hint, hint.
>> 
>>