Re: [Gendispatch] First comments on draft-rsalz-2028bis-00.txt

Eliot Lear <lear@lear.ch> Fri, 10 September 2021 11:35 UTC

Return-Path: <lear@lear.ch>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 059443A090D for <gendispatch@ietfa.amsl.com>; Fri, 10 Sep 2021 04:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level:
X-Spam-Status: No, score=-2.091 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, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OV8s1gMwY43e for <gendispatch@ietfa.amsl.com>; Fri, 10 Sep 2021 04:35:06 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 082B93A0914 for <gendispatch@ietf.org>; Fri, 10 Sep 2021 04:35:04 -0700 (PDT)
Received: from [IPv6:2001:420:c0c0:1011::6] ([IPv6:2001:420:c0c0:1011:0:0:0:6]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 18ABZ0DI042104 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 10 Sep 2021 13:35:00 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1631273701; bh=KQL4jC6znVSgiwXji5ZyA6tDSJy8AItAEEvzITkHc8s=; h=To:Cc:References:From:Subject:Date:In-Reply-To:From; b=czCvWlGu/6OENiqic0KrtUU4XiypMF/z4y0iehcvpLBhYUGdMA6SAshxqICbUTrrY 54NiDth8MkK/0stG/aUCaB0c0Ut51gyqXbIU7D91y4036N1C3BMF2QRNnxZyFoc/ah H6mz/vwDcOZyHZC+0R8HhjPHDpVm/Ohbzyq5YmwE=
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "gendispatch@ietf.org" <gendispatch@ietf.org>
References: <163069758370.6471.14990302329155864755@ietfa.amsl.com> <A21C8B4C-C2E1-4C4D-AB6F-C3C2FF5BF23A@akamai.com> <9b9c0e2d-c997-431c-6cc0-326b85992c72@lear.ch> <84a84b50-e8ce-da68-9115-83b392043683@gmail.com> <18205B44-72C5-4A59-93F4-A39FEA3384A1@akamai.com> <CALaySJLTUHj6ZJ8Yn_99nQLN3g8h00R7w6+4NoEa3-SAf6KQgQ@mail.gmail.com> <CAChr6SwfSnNsiDssk7Z9j_wP4aHHv7UC60QRHrGKEC2L3S36KQ@mail.gmail.com> <a22d97e8-512b-8749-5727-eb93bc481f06@gmail.com>
From: Eliot Lear <lear@lear.ch>
Message-ID: <c1a32701-166d-4d68-e1bf-dd2c9afc3a6c@lear.ch>
Date: Fri, 10 Sep 2021 13:34:57 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <a22d97e8-512b-8749-5727-eb93bc481f06@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="cLbRDBtZcuJIE79MmI7uCeidFGZ0xPzaG"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/HipSGk8G3UMbIdejXcCUHh53mjA>
Subject: Re: [Gendispatch] First comments on draft-rsalz-2028bis-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2021 11:35:12 -0000

As I wrote earlier, I support this draft going forward, and I think the 
best way is AD-sponsored.

The one aspect of this that I mentioned to Rich and Lars was that I 
think we should look at whether this document should be looked at 
normatively or whether it is meant as an informational document.  That 
is– should the process of updating this document update documents other 
than obsoleting 2028?  I would very much like the answer to that 
question to be NO.

We have to be sure that we're not doing that by accident, and one way to 
do that is to make this document Informational.  Another way to do that 
is to say that explicitly we are not updating any other documents, and 
when in doubt, go to those other documents. A third way of doing that is 
to go read that long list of documents to make sure we are not creating 
ambiguities.

Eliot

On 08.09.21 22:59, Brian E Carpenter wrote:
> On 09-Sep-21 08:42, Rob Sayre wrote:
> ...
>> By writing it all down, Rich seems to have shown that some of these relationships are absurdly complex. I'm not saying that was the intent. Sometimes these things only become evident after you try to document them.
> They are complex as a result of history, but trying to straighten out a plate of spaghetti is generally held to be impossible. We have a plate of our own spaghetti to sort out first: https://www.ietf.org/standards/process/informal/
>
>     Brian
>