Re: [Tools-discuss] draft-ietf-acme-dns-account-01-00

Carsten Bormann <cabo@tzi.org> Tue, 14 February 2023 16:57 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40D7C1CAB52 for <tools-discuss@ietfa.amsl.com>; Tue, 14 Feb 2023 08:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.486
X-Spam-Level:
X-Spam-Status: No, score=-1.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 P1oEcxDR1GqN for <tools-discuss@ietfa.amsl.com>; Tue, 14 Feb 2023 08:57:01 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 58404C16B5C8 for <tools-discuss@ietf.org>; Tue, 14 Feb 2023 08:57:00 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4PGS6f3h3xzDCbP; Tue, 14 Feb 2023 17:56:58 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f0eacbcd-065d-d0c7-7835-0ee8b958b85a@nostrum.com>
Date: Tue, 14 Feb 2023 17:56:58 +0100
Cc: tools-discuss@ietf.org
X-Mao-Original-Outgoing-Id: 698086618.083915-0c3a4484446496bc63557020c0979820
Content-Transfer-Encoding: quoted-printable
Message-Id: <C42F5998-2C59-4476-B934-6E9CBB1433BF@tzi.org>
References: <7343BA3F-E97F-498C-A56C-C2A6EBDEFC5A@tzi.org> <f0eacbcd-065d-d0c7-7835-0ee8b958b85a@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/tsiH9ztM50hdj9HaMYxQYewxCEs>
Subject: Re: [Tools-discuss] draft-ietf-acme-dns-account-01-00
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2023 16:57:06 -0000

Hi Robert,

On 2023-02-14, at 15:08, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> I'd love to do that. We could solve the disambiguation problem with a finite set of hashes going forward.

I’m not sure we are talking about the same problem, or maybe we are and I don’t comprehend the full gamut of issues here.

> But we can't do it for all document types (which is really what we should strive for). We'd have to completely overhaul the way we name charter documents, including replacing RFC6292 that defined that we use sequences that look like 00-00, 00-01, ..., 00-nn, 01, 01-00, 01-01, ... , 02, 02-00, ...

I was thinking that an 80 % solution might be simply disallowing submission of I-Ds with docnames of the form .*-[0-9][0-9]-[0-9][0-9]

I don’t understand the naming behind draft-ietf-acme-dns-account-01-00, but there are many reasons to have a two-digit number at the end of the constant part of a name, such as in draft-ietf-idr-deprecate-8-9-10-00 (which is about deprecating options 8, 9, and 10), or, historically, in draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-07.txt (the underlying standard IEEE 802.16 can be abbreviated as 802-dot-16 — note there already is a circumvention in that name for the dot) etc. — this just needs to be brutally suppressed at submission time.

Grüße, Carsten


> 
> RjS
> 
> On 2/14/23 4:24 AM, Carsten Bormann wrote:
>> Can we now reject draft submissions with docnames that confuse datatracker like that?
>> 
>> *** reference.I-D.ietf-acme-dns-account-01.xml: *** Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-ietf-acme-dns-account-01.xml
>> 
>> Grüße, Carsten
>> 
>> ___________________________________________________________
>> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss