IETF Logo Mail Archive

Re: [Tools-discuss] I-D names ending in -[0-9][0-9]

Robert Sparks <rjsparks@nostrum.com> Mon, 24 January 2022 15:36 UTC

Return-Path: <rjsparks@nostrum.com>
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 259A93A0EFD for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jan 2022 07:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.793
X-Spam-Level:
X-Spam-Status: No, score=-7.793 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.714, RCVD_IN_DNSWL_HI=-5, T_SPF_HELO_PERMERROR=0.01, T_SPF_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=nostrum.com
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 fu4NQsjuXDAS for <tools-discuss@ietfa.amsl.com>; Mon, 24 Jan 2022 07:36:18 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D005C3A0EFC for <tools-discuss@ietf.org>; Mon, 24 Jan 2022 07:36:18 -0800 (PST)
Received: from [192.168.1.113] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 20OFaCuv078151 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 24 Jan 2022 09:36:13 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1643038573; bh=psarz3YVnWUB4uoUdcg3vziMZJduAS5XHz2lDw+AbJM=; h=Date:Subject:To:References:From:In-Reply-To; b=FHvF239JhAd3tHpNQnKoUqMjbqA9EXJ4Er4+XSOkVBAXNOj8M/lLNOA2xYgLOPUYj FDlGA5acTAsSzHBqlStW1QigsrDGXN6WNxPmEWWTF2aCqxBqlWRjqvS/nksjwUmFRF lUyRWcMZR7FAb6IpUY3infwb7QWURRieZcdLbAtc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.113]
Message-ID: <5acf18e8-2e3b-8d0c-e5a3-2148196ddaf2@nostrum.com>
Date: Mon, 24 Jan 2022 09:36:07 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Julian Reschke <julian.reschke@gmx.de>, tools-discuss@ietf.org
References: <D02B9D39-457E-4CBA-8196-19B6BFA34925@tzi.org> <47E18CD5-2FCB-4218-B0F9-C3BA23672282@tzi.org> <050afa9b-9d59-b56a-9d0d-0ae5cc614fad@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <050afa9b-9d59-b56a-9d0d-0ae5cc614fad@gmx.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/nEh9IZmr49bb0_IikyjS8uRZlfI>
Subject: Re: [Tools-discuss] I-D names ending in -[0-9][0-9]
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Jan 2022 15:36:23 -0000

On 1/24/22 8:22 AM, Julian Reschke wrote:
> Am 24.01.2022 um 14:38 schrieb Carsten Bormann:
>> On 2022-01-24, at 08:09, Carsten Bormann <cabo@tzi.org> wrote:
>>>
>>> (Maybe we should have disallowed draft names ending in -[0-9][0-9] 
>>> ?  But that’s too late now.)
>>
>> And while we are at that, we could disallow submitting v3 drafts with 
>> different names in /rfc/@docName and /rfc/front/seriesInfo/@value — 
>> I’ve seen different parts of the toolchain pick up different values 
>> from those two places, which can get very confusing.  (Some 255 I-Ds 
>> have inconsistencies here, including at least one I co-authored :-), 
>> so this is not a theoretical concern.)
>
> Even better would be to eliminate the option to put the same thing into
> two places...

Are you re-raising this as a grammar change we should consider?

The original 799x proposal turned out to be quite problematic - 
especially when a document might have more than one bit of series info 
(something published as a BCP (and necessarily as an RFC), for example. 
There were other rough spots called out starting at 
https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13#section-3.1.18.

IIRC, list discussion around this and similar changes pointed out the 
issue with changing what people expect, both as authors and as tool 
maintainers.

If we did want to change the vocabulary, perhaps we give up on the reuse 
of seriesInfo in front, and build a structure that unambiguously 
declares the name, and a list of other names the document might go by.

Whatever we do, finding the name shouldn't become more difficult than 
the current, where it's possible to pull the name of the document out 
with a fairly simple regex.

>
> Best regards, Julian
>
> (and yes:
> https://github.com/reschke/xml2rfc/blob/ff4ff07ad7e3871ec6e68fe0c709c76778c7f8a9/rfc2629.xslt#L3182-L3186) 
>
>
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: 
> datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): 
> https://www.ietf.org/mailman/listinfo/tools-discuss

v2.23.0 | Report a Bug | By Email