Re: [tao-discuss] [Gendispatch] Requests for IETF 114
Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 06 June 2022 21:09 UTC
Return-Path: <brian.e.carpenter@gmail.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 5B162C14CF03; Mon, 6 Jun 2022 14:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.984
X-Spam-Level:
X-Spam-Status: No, score=-2.984 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NICE_REPLY_A=-1.876, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 cElZxfQUrEQ3; Mon, 6 Jun 2022 14:09:33 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 9E751C14F72E; Mon, 6 Jun 2022 14:09:33 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id p8so13701637pfh.8; Mon, 06 Jun 2022 14:09:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=jcVgov4k/9SvrtAHnUwcJIsOlGAlYDxoT25F9XexO/I=; b=PVfaVdplBkosbmTNUSqUc11EHPvaLPeqnqupN79KrP5WNLjhct5KfsBQhLD1r4Gmwr U4waigosekG8CVzAeSYo+lGDNsyg2Oma17nT7JhLAA36DBrGbZVScGB23o4/lUKqNQ+6 7YOQazLBGKHZeuxSi7UxHOsx1VoLjmlObZB+l/zc2TDXwQiJ8F74B0d1Qg40ZCOlkSTx ThwDM8Ms0NeMgOYIKFDnJ3rHnKbPkRvAcSIIAxOfy+CvbGq27mY9t/F92M8PLv3YDd4/ 7TUlNvu1E6vK1fg/lCfrK1q8+gnZcEy3JlepLuu25jHc1rIzgXElMCBhtDHXkYDIyt+B bEmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=jcVgov4k/9SvrtAHnUwcJIsOlGAlYDxoT25F9XexO/I=; b=ooWQ8SRF0BXsL+hlB76HuJYCUjgoWw6vWIg073Pp/IpC+gtXaTGZAdZxJ9681N0+FO HxAKy25Mxn3jP2YwHLmDJN+YppRudy7bJklz1a+Sy3UuFBSrG4ztWC0eymbWzRCl+VR6 Gn5WtXLa6p9kbmLkUeoGNJ+MVTEdoZrVVnMmxC6fQA+jikG1TLUwPq/ZOQD9kPGLUB2r WIiS5i6VtlGTCce/h6ZROR2Yxv9ckuZXFFIimTvOYsfu0ePnr0td4WPXHPNqLKUDcjBG vIhPyLfppG0kbGYWNNESauUL5MGGGqO7HG62F6fJgmh/L3SBJ2+sFoBsHK+UnAKDAKdx 2imw==
X-Gm-Message-State: AOAM5323vMWWO8p3D3XnzCnO4fJ+RZpmU70DD2LeZmWvzE6WtQidVNAO HEqOP8y0Arc8iMudEXyLEhjUp6MapTKJOg==
X-Google-Smtp-Source: ABdhPJzZWzagTF2qz1dknc/koq1gK576LRz3Bz5ObBuudgMqhdlDIs2BpvRkXF7C+HPnK3EOBvRa7g==
X-Received: by 2002:a63:ea09:0:b0:3fd:3c6a:47c2 with SMTP id c9-20020a63ea09000000b003fd3c6a47c2mr14668477pgi.242.1654549772528; Mon, 06 Jun 2022 14:09:32 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id g12-20020a17090a708c00b001cd4989ff42sm10467645pjk.9.2022.06.06.14.09.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Jun 2022 14:09:31 -0700 (PDT)
To: Warren Kumari <warren@kumari.net>, Rob Sayre <sayrer@gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, GENDISPATCH List <gendispatch@ietf.org>, tao-discuss@ietf.org
References: <CAC9wnY-03+ToGL4KjjRaXBquxV2DeBaax67bxJB9qZEj=PSELg@mail.gmail.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> <9a29ffe1-c78e-77ad-86ce-661265e5d2df@joelhalpern.com> <A9BAD84B-9228-494B-A988-8665768061B0@akamai.com> <340d6b2a-6cd2-ccdd-6d0b-a2a9ac44e7d8@gmail.com> <CABcZeBN_ATZbA+txPFH3F6OyTpn1WEZ3kC1hBvcvHoShFNibSw@mail.gmail.com> <CAChr6Sw8aMA68Pp5UJ2VDtFzsZ+WDJ2yOXFNgi=1qrEL4FtFMQ@mail.gmail.com> <CAHw9_iKOAkj1TAZ0fvDKi_x1gNs7jPBgt--_ZR99NLc-tUXOUw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <90f43001-461a-5eff-ccb5-59ac70ec71df@gmail.com>
Date: Tue, 07 Jun 2022 09:09:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CAHw9_iKOAkj1TAZ0fvDKi_x1gNs7jPBgt--_ZR99NLc-tUXOUw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/AUmAoF-AkCMezbmVh53n5bNCp8U>
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: Mon, 06 Jun 2022 21:09:37 -0000
Warren, On 07-Jun-22 03:28, Warren Kumari wrote: > > > > > On Mon, Jun 06, 2022 at 1:24 AM, Rob Sayre <sayrer@gmail.com <mailto:sayrer@gmail.com>> wrote: > > On Fri, Jun 3, 2022 at 4:06 PM Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>> wrote: > > > I do agree that the material needs to be accurate, but I also think that if we treat this like a Web page that can be changed rather than an RFC, the stakes are a lot lower. If we find something wrong, we just change it. > > > Lars raised the point that RFC 6722 makes revisions of the document require IESG approval. The result is a poorly supported bureaucratic process. > > The text of the document is mostly good advice, but the name is a bit tacky. I'd suggest writing an RFC that obsoletes all revisions and RFC 6722, and points at a general IETF web page that can be revised as freely as ekr suggests. > > > > I actually believe that the Tao should be an RFC, and progressed and reviewed just like any other RFC. I'll happily agree that updating an RFC is a massive faff, and takes much too long to make simple updates, but I think that *that* is a problem that we should solve. > > For the general "how to participate" and "general IETF web page that can be revised as freely as ekr suggests", we already have these — they are the "general IETF web page that can be revised as freely as ekr suggests" :-) > > We have: > https://www.ietf.org/about/participate/get-started/ <https://www.ietf.org/about/participate/get-started/> As it happens, I drafted the original version of that page in 2013, and I believe this text has survived pretty much unchanged: "The Tao of the IETF is a must read document. If you read nothing else, read this." The basic question here, where there appears to be genuine disagreement, is whether we want that statement to remain true. Personally, I think it's good to have a single document for this material, and that it should be printable. Whether it is an RFC or not is a side issue. Brian > and "a series of video testimonials from other attendees talking about their first meeting." and "IETF Newcomers Introduction Videos" and "The IETF Newcomers' Tutorial" and "How to Read an RFC" (an"blog post by Mark Nottingham provides a practical approach to reading RFCs, the document format in which specifications developed in the IETF are published.") and a huge pile of presentations and resources at https://datatracker.ietf.org/group/edu/materials/ <https://datatracker.ietf.org/group/edu/materials/> and the EMODIR (https://datatracker.ietf.org/group/emodir/about/ <https://datatracker.ietf.org/group/emodir/about/>) resources and the IETF104 newcomers sessions (https://www.ietf.org/live/previous/live104/ietf104-newcomers-tutorial/ <https://www.ietf.org/live/previous/live104/ietf104-newcomers-tutorial/>) and (one of my favorite) Scott Bradner's "bite-sized IETF introductory videos" (https://www.youtube.com/playlist?list=PLC86T-6ZTP5hXPJ-n4mwJbZ0BHaNlhTMA > <https://www.youtube.com/playlist?list=PLC86T-6ZTP5hXPJ-n4mwJbZ0BHaNlhTMA>), and … [0] > > My point is that we *already* have the IETF webpages, and that those can be updated whenever and however we like — but, to me, the Tao is "special", and that this is a good thing. > > I think that the content of the Tao should reflect the consensus of the community, and should reflect (and guide) our ethos. We already have the web site, and it can be updated easily and at the whim of whoever is in charge of those bits, and reflects the consensus of whoever/whichever group decides to so — but it doesn't get the normal IETF consensus review, and doesn't necessarily reflect the IETF community. > > I think that we should have a "higher level" document — and that that is the Tao. > So, my proposal is that the Tao becomes an RFC again and be progressed just like any other, and that the "general IETF web page that can be revised as freely as ekr suggests" already exists. > > > W > [0]: Note: I'm certainly not saying that our newcomers material is perfect or complete - the people participating in Edu / Emo / newcomers / guides, etc are "doing God's work"[0], please help them with this. > > [1]: In the English idiomatic "Work that is very important and necessary, especially that which receives little or no recognition or pay." meaning — no religious meaning implied… > > > thanks, > Rob > > _______________________________________________ > tao-discuss mailing list > tao-discuss@ietf.org <mailto:tao-discuss@ietf.org> > https://www.ietf.org/mailman/listinfo/tao-discuss <https://www.ietf.org/mailman/listinfo/tao-discuss> > > > > > _______________________________________________ > tao-discuss mailing list > tao-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tao-discuss >
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Bob Hinden
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Lars Eggert
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Lars Eggert
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian Rosen
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian Rosen
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian Rosen
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Bob Hinden
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Eric Rescorla
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Joel Halpern
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Eric Rescorla
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Rob Sayre
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Warren Kumari
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Warren Kumari
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Rob Sayre
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Jay Daley
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Niels ten Oever
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Warren Kumari
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Rob Sayre
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Mark Nottingham
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Tony Rutkowski
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Brian E Carpenter
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Salz, Rich
- Re: [tao-discuss] [Gendispatch] Requests for IETF… Lloyd W