IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Fri, 03 June 2022 15:55 UTC

Return-Path: <bob.hinden@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 93580C15BEC8; Fri, 3 Jun 2022 08:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 (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 IKO9b6Ppt7I6; Fri, 3 Jun 2022 08:55:38 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 3A04FC157B50; Fri, 3 Jun 2022 08:54:23 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id x17so10946535wrg.6; Fri, 03 Jun 2022 08:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=G1mQXNQTz2IddMndcgAzugUGSBJt2XRZAG2gyHsXt9o=; b=cI47nfqk4BP8eFFinpbxJsKgW6uYuI/qFNQHLnDGx6umPeDQgL7wBjR6S+L8vniXuY oToEZzejiwd0WP834vOZlxCw0IierdspCgDx/f+9vdgaM0/t4JvsoqSKfxS36DghIYbE 3KKHS58sscNkAJgwibsL9qyclsY2ZIdfpEftASVFMSR56NZoJsriCFyJswoq0gK6AMMv 1OZmcW/hRzBzjBpnsJo6SS5quJebgIIArXc4yABv3M2M3n3HZwz7rxxysSdJJXncalVR aGUr++WrTReFYXiD2Rt0X6syDC5IIcANqrl74jch/0WHuSKv21sQKvuQDGAdHm7KqFcQ SzdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=G1mQXNQTz2IddMndcgAzugUGSBJt2XRZAG2gyHsXt9o=; b=GvXEpw8ogzFPcH56MoPG64MoMmeoGGne9AzSqJyzN4tbMFc90zWosen5zH9L09XZQJ 3aWVvgUnbMDFS6ABAgmYLr8tfPdIYY6JrVTUJXNTImSJmDocs/5cIr/iYHUftWlocszD G20M1xoUQg4LOJI/8Mg4WT5HUcJKuuJGAbPKAKsQX4kX3NnjXetEnZbT5KLKT+DaPlFx v9gIv9P4IFbT/dCTURhIGe1mBGxbVjQKwj3nVeY+OZkDF13M4O2StzZd4LShRP2epV8R I5WkYVGUjl/LmuihNDUuhhfp3BvZ/Yoq2agZnjdPCqZREVl+/CMTcMqSvoBmj4qnVeg+ QM3w==
X-Gm-Message-State: AOAM532z3FAvS6+L+gRAMPmPrcy7qi8wz9X859T4+wmJGFtWbv4XgOiO fB1p9Ytvb5Z4LANnSorQUU+QqqpDIbN17Q==
X-Google-Smtp-Source: ABdhPJz4tftc2ICFuIb52RsqZdJyMkPIVomn76JYpM0CAYWD1AbZ/wDTXBLWNTm/GIeO28ToG9NTHQ==
X-Received: by 2002:adf:fbce:0:b0:20f:ca5b:c4cf with SMTP id d14-20020adffbce000000b0020fca5bc4cfmr8704904wrs.421.1654271661335; Fri, 03 Jun 2022 08:54:21 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:ac3f:e564:10d0:ce15]) by smtp.gmail.com with ESMTPSA id n20-20020a7bc5d4000000b0039aef592ca0sm8805225wmk.35.2022.06.03.08.54.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Jun 2022 08:54:20 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_EC268D3E-7FBA-4711-8D9F-1F15275048D6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <C5B7316E-97BE-4C52-8383-15F3BC3CC7ED@brianrosen.net>
Date: Fri, 03 Jun 2022 08:54:16 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Rich Salz <rsalz@akamai.com>, Lars Eggert <lars@eggert.org>, Kirsty Paine <kirsty.ietf@gmail.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>, "gendispatch-chairs@ietf.org" <gendispatch-chairs@ietf.org>, "tao-discuss@ietf.org" <tao-discuss@ietf.org>
Message-Id: <DBA61D29-F469-4D78-9682-C3BC5C13376E@gmail.com>
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> <3951006C-21D8-4A04-9CC5-2D88B3A94778@akamai.com> <C5B7316E-97BE-4C52-8383-15F3BC3CC7ED@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/9q3-D5C-3ng_xNhZa9cfda63hXI>
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 15:55:40 -0000

Brian,

> On Jun 3, 2022, at 8:50 AM, Brian Rosen <br@brianrosen.net> wrote:
> 
> That’s a rendering decision, not a content decision.
> 
> I’m pretty sure most of us point any newcomers to the Tao.
> 
> I do that because I think it represents the consensus (key word) of who we are and how we work.  I do not trust a website content creator to get that right.  And I’d prefer not to have to trust a self-selected group (a work group) to get that right without review.  It’s a small stretch to say the IESG has to review and approve, but I think that just using the RFC process is the best way forward.
> 
> Once we have the consensus on the words, you can render them in some pleasing way on the website.

I also note that folks who want to work in the IETF need to get used reading RFCs, so this is a a good place to start.

Bob

> 
> Brian
> 
> 
>> On Jun 3, 2022, at 11:43 AM, Salz, Rich <rsalz@akamai.com> wrote:
>> 
>>>> Dunno, ISTM that the simplest, most straightforward solution is just make the TAO an RFC again.
>>> 
>>> I very strongly believe that this misses the point.  "It is not a formal IETF process document but instead an informational overview."
>> 
>>> That seems to be a distinction without a difference, because, I think, it ought to get an IETF-wide review, and, I think, the IESG should review it.
>> 
>> You are comparing "Tao as RFC" with "Tao under the current process (RFC 6722)" and I mostly agree that there is no effective difference between those two.  The proper evolution of 6722 is to just make it a web page, developed by professionals.
>> 
> 
> --
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch

v2.23.0 | Report a Bug | By Email