IETF Logo Mail Archive

Re: [tao-discuss] New version of the "Tao of the IETF" published

Joel Halpern <jmh@joelhalpern.com> Fri, 09 September 2022 16:45 UTC

Return-Path: <jmh@joelhalpern.com>
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 CC589C1524B3 for <tao-discuss@ietfa.amsl.com>; Fri, 9 Sep 2022 09:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUlXgcmBG_aU for <tao-discuss@ietfa.amsl.com>; Fri, 9 Sep 2022 09:45:47 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C973BC1524CB for <tao-discuss@ietf.org>; Fri, 9 Sep 2022 09:45:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4MPMLg4YTbz1pGqq for <tao-discuss@ietf.org>; Fri, 9 Sep 2022 09:45:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1662741947; bh=eLTnI9nkZmcjt8Z9NSqy1Gzkhh2kitd872TyRm2w9uo=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Z/LXedDmzSv+RasT4Mo4M3jqHzzy12R9r92+Xv1fYojCDvXNCv/S8hutMQZ2cc5WL b+2+/ggEIJX7IJRr6q5NYI41In+Lwb7jeF2DIpwYK4OqKrUob6e6o2tUrd7rZ+9mw7 ueKa65h8wzOqVez7DT4jeVUFVfsIr2e5zCM5QD1s=
X-Quarantine-ID: <aKaosU7LPAp9>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4MPMLf4LVSz1pW0d for <tao-discuss@ietf.org>; Fri, 9 Sep 2022 09:45:45 -0700 (PDT)
Message-ID: <85c844e3-f5f1-6851-e4d6-f57e837fe159@joelhalpern.com>
Date: Fri, 09 Sep 2022 12:45:41 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0
Content-Language: en-US
To: "tao-discuss@ietf.org" <tao-discuss@ietf.org>
References: <64E2EB34-AD95-479D-BCE8-998967380C04@ietf.org>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <64E2EB34-AD95-479D-BCE8-998967380C04@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/bejkHb8WA9rqOrJDZE5te07h3Hs>
Subject: Re: [tao-discuss] New version of the "Tao of the IETF" published
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 09 Sep 2022 16:45:51 -0000

I do not want to be too picky.  I understand that it is impossible to 
get the wording of the Tao perfect.  And I understand that it does not 
need to be precise or complete in describing our process.  (If it were, 
it would likely be unreadable.)

However, in the section describing the IESG processing of RFCs, I see 
that the text claims that the IESG reviews EACH (emphasis added) drafts 
that are becoming RFCs.  And the text as written implies that in all 
cases those reviews result in ballots with the described positions.  
However, that is not the case,  IRTF drafts and Independent Stream 
drafts do not get that treatment.   When we next edit this, could we 
change that slightly?

Maybe make it "each IETF produced RFC"?  Or at the section that says "As 
part of the document reviews" make that "For IETF produced RFCs, as part 
of the document reviews"?  (I would have used "stream" rather than 
"produced" but I think that might be confusing for newcomers as they  
often are not familiar with RFC streams.)

Yours,

Joel

On 9/9/2022 10:27 AM, IETF Chair wrote:
> [Forwarding this on behalf of the Tao editors - Lars]
>
> Dear all,
>
> I am very happy to announce the new version of the Tao of the IETF [0].
>
> This version significantly benefited from suggestions and contributions by the community, most notably from Rich Salz, for which I as editor am very thankful.
>
> This publication would also not have been possible without the support of Greg Wood and the review of the IESG.
>
> The IESG requested for future iterations to have smaller changes, so I intend to increase the publication pace. However, this also depends on the discussion about the future of the Tao.
>
> Best,
>
> Niels
> Editor of the Tao
>
> PS New suggestions are of course always welcome on tao-discuss and on Github as PR (https://github.com/ietf/tao/blob/main/Tao.md)
>
> [0] https://ietf.org/tao
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

v2.23.0 | Report a Bug | By Email