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

Joel Halpern <jmh@joelhalpern.com> Fri, 09 September 2022 18:58 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 5F93EC152711 for <tao-discuss@ietfa.amsl.com>; Fri, 9 Sep 2022 11:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, 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 JE89A00fNchx for <tao-discuss@ietfa.amsl.com>; Fri, 9 Sep 2022 11:58:41 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C061EC152568 for <tao-discuss@ietf.org>; Fri, 9 Sep 2022 11:58:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4MPQJ138Sdz1pMVK; Fri, 9 Sep 2022 11:58:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1662749921; bh=DEgGIbov7yjF42DsGsqOtiwmMiVFcB3QquWsyxgaVxE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=LYPPlAs5EGvrBM4ENWYdjJR6ao7OsHWR/j/vKGSAl/SQUarsiBBWhr554HjOkBFuz PoqkeoP3h58+z8CfG2xDJpVGr0ITgxNumfhN4n0nyejGadLHyK/PV2uPy/sRuq/+Cb AlCVlRHnabCcKmpwbL1f6PQMKXYDKhnAcg5fXy0s=
X-Quarantine-ID: <8J9Rgh2gFKEA>
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 4MPQJ05pPFz1pMJ1; Fri, 9 Sep 2022 11:58:39 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------0TvBRydgoNuxXiSHnxDGPHGS"
Message-ID: <a9de220b-b79a-b709-2761-b84758a354ba@joelhalpern.com>
Date: Fri, 09 Sep 2022 14:58:35 -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: Niels ten Oever <mail@nielstenoever.net>
Cc: tao-discuss@ietf.org
References: <64E2EB34-AD95-479D-BCE8-998967380C04@ietf.org> <85c844e3-f5f1-6851-e4d6-f57e837fe159@joelhalpern.com> <5ea192bf-b64c-47bb-b98b-d7474619a569@nielstenoever.net>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <5ea192bf-b64c-47bb-b98b-d7474619a569@nielstenoever.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/OWunPZ1q6ABolxV-9s3PY_WewsE>
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 18:58:45 -0000

That, the IESG reviewing all IDs for RFC publication, is why I suggested 
the second modification.  My concern is that although the IESG does 
indeed review IRTF and ISE documents, the review choices, criteria, 
votes, etc. are not those you carefully (and accurately) list for the 
IETF stream.  So I was looking for someway to simply avoid the inaccuracy.

Yours,

Joel

On 9/9/2022 1:48 PM, Niels ten Oever wrote:
> Hi Joel,
>
> Is it not the case that the IESG also reviews  the other stream RFCs 
> to ensure that there is no overlap?  I thought that is how it is 
> described in several process documents, at least I  case for IRTF 
> RFCs, but i think also for IS.
>
> But then of course theory and practice might vary.
>
> Best,
>
> Niels
> On 9 Sep 2022, at 18:46, Joel Halpern <jmh@joelhalpern.com> wrote:
>
>     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 
>
>
>     ------------------------------------------------------------------------
>
>     tao-discuss mailing list
>     tao-discuss@ietf.org
>     https://www.ietf.org/mailman/listinfo/tao-discuss
>
>
> _______________________________________________
> tao-discuss mailing list
> tao-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tao-discuss