Re: [tao-discuss] [Gendispatch] Requests for IETF 114

Joel Halpern <jmh@joelhalpern.com> Fri, 03 June 2022 17:08 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 F1976C14F73D; Fri, 3 Jun 2022 10:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.005
X-Spam-Level:
X-Spam-Status: No, score=-9.005 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=-1.876, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 1TgXDczrtvLm; Fri, 3 Jun 2022 10:08:19 -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 E4F41C14F75F; Fri, 3 Jun 2022 10:08:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4LF8Tt5142z1pVyW; Fri, 3 Jun 2022 10:08:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1654276098; bh=fknXJ1UKuzM4LFairusBBdNX6eLnUWTQLKpxBSYCTsg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=IiHUevFZYh86hMq/11mgItVZtw3C6wiZ3XLkRvSOyUs3x9aCkt9Zg4SeqPGG3asv6 8kNGXH+Bj7rbgyi26SEZvx15ImJmahsrTVicy9DzwzSRTiH+SjV/gdyJl+Aw2/iOyO efqrxU/0NZAGYVaLNO9Sp+XXjeaKBWsGFBkVVptM=
X-Quarantine-ID: <7SgieXkZhEE8>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (50-233-136-230-static.hfc.comcastbusiness.net [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)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4LF8Ts5yMLz1pVyb; Fri, 3 Jun 2022 10:08:17 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------hqVIQ9QDoN9PjA9Hm06blqcs"
Message-ID: <9a29ffe1-c78e-77ad-86ce-661265e5d2df@joelhalpern.com>
Date: Fri, 03 Jun 2022 13:08:16 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: Eric Rescorla <ekr@rtfm.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: "gendispatch@ietf.org" <gendispatch@ietf.org>, "tao-discuss@ietf.org" <tao-discuss@ietf.org>
References: <CAC9wnY-03+ToGL4KjjRaXBquxV2DeBaax67bxJB9qZEj=PSELg@mail.gmail.com> <89DAA7D5-3DF6-4B42-A3F0-7698F550C5B0@eggert.org> <36AFC944-59F3-49CC-AFEF-4471476F1913@eggert.org> <CB175E16-812E-4288-886B-B7FC82756720@akamai.com> <5C314F03-0C3D-4E1C-9AFE-BBCE8F775D8F@brianrosen.net> <7712AEA2-DDB3-4915-A060-9F3CACA9435E@akamai.com> <EB02214C-8DCC-41C1-A266-08A042AE6318@brianrosen.net> <48a0df92-497a-6747-a8e6-ba93abc7f3d8@joelhalpern.com> <1A1A07E4-A8A9-4D44-AC61-8CAE9B4D6DAC@akamai.com> <68405df2-2808-8739-9c7f-4fc04744f594@joelhalpern.com> <A68A6825-685F-40D6-8978-E853A62A5631@akamai.com> <e321e11e-a70f-e50c-c014-0891708c867a@joelhalpern.com> <145A06D8-7927-44C1-95B6-625529C91DDD@akamai.com> <CABcZeBMH32C2ogd8+hLt_6PEqVxSJV0tBAVygswLtSKhvpVs+Q@mail.gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CABcZeBMH32C2ogd8+hLt_6PEqVxSJV0tBAVygswLtSKhvpVs+Q@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/nnOfW9CCONfJaJVtZUyVhQQxQr8>
Subject: Re: [tao-discuss] [Gendispatch] Requests for IETF 114
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, 03 Jun 2022 17:08:23 -0000

The below note on the content of the Tao seems very relevant.  I 
particularly think the point of getting someone who is not deeply in the 
community to be the pen-holder is well taken.

Still, because this is the communities face to newcomers I would like it 
to be reviewed and approved by the community.  It seems like the content 
(in whatever pieces are appropriate, could still be in an Informational 
RFC, with the presentation left to professionals.  Maybe there is 
another way to do so.

Your note (and one recent one from Rich) are the first efforts to 
explain why some other process may be appropriate.   I

Yours,

Joel

On 6/3/2022 12:58 PM, Eric Rescorla wrote:
> Taking a step back from the discussion of the Tao, one of the most
> common complaints one hears from newcomers to the IETF is how hard it
> is to come up to speed on some of our--honestly kind of
> confusing--processes and practices.
>
> IMO the resources that we point people to should lean into being
> approachable, and I don't think a long document like the Tao really
> fits that bill. A big part of the problem, IMO, is the urge to be
> complete. For instance, I see that in the section on "RFCs and
> Internet Drafts" the Tao has a whole section in "IANA Considerations".
> This is of course important information at some level, but it's not
> information that a newcomer typically needs, even at the point
> where they are writing their first I-Ds.
>
> So I agree with Rich that we should deprecate the Tao as a whole
> document and instead restructure the material in a way more suited
> to helping people get going quickly rather than the linear fashion
> of the current document; one nice feature of the Web is that it
> supports this.
>
> As to who ought to write it, I would observe that writing this kind of
> tutorial material is different from writing technical specifications.
> While I'm sure some people in our community have those skills, it's
> not clear to me it ought to be community developed and in particular
> I think it should be subject to far less rigorous review than RFCs
> and should instead just be easily changed and refines. I'd certainly
> be open to seeing a treatment from someone who was less deeply embedded
> in our community and thus maybe found it easier to empathize with
> newcomers.
>
> -Ekr
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Jun 3, 2022 at 9:41 AM Salz, Rich 
> <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>
>     >   I have read the Tao.  I have directed multiple newcomers to
>     read the
>         Tao.  Some have said it was useful.  None have complained
>     about it.
>
>     Good to know, thans.
>
>     >  We are debating how the
>         content should be developed / agreed for the community
>
>     Some of us (well at least me, but I know others who agree) are
>     debating whether or not the community should be involved in the
>     content creation.
>
>
>     -- 
>     Gendispatch mailing list
>     Gendispatch@ietf.org
>     https://www.ietf.org/mailman/listinfo/gendispatch
>