IETF Logo Mail Archive

Re: [xml2rfc] future work: a <bcp26> element, by analogy with <bcp14>

John R Levine <johnl@taugh.com> Sat, 14 May 2022 15:55 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A50AC14F6F9 for <xml2rfc@ietfa.amsl.com>; Sat, 14 May 2022 08:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=QCTxK6j4; dkim=pass (2048-bit key) header.d=taugh.com header.b=fVOREPZC
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 qnOWhgwM6WzC for <xml2rfc@ietfa.amsl.com>; Sat, 14 May 2022 08:55:24 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7A6FCC14F6EB for <xml2rfc@ietf.org>; Sat, 14 May 2022 08:55:24 -0700 (PDT)
Received: (qmail 24313 invoked from network); 14 May 2022 15:55:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=5ef6.627fd0e9.k2205; bh=znEJUBGGGIFvrIcKKeTXa9/N0CUKqW0kN83vokijGzY=; b=QCTxK6j4vzlg8EWgbkZVBfh0bOQoAu7LfMDxFVp/YPsC83yOPh0hFYeqt5tjxVsmGbk8Y1SrmVfEcC/BmJhGUziNq7bo28D4JlM4vm6ICMxqxeKKkipMeTXQ4OoaEmV1TJSyqhyphKjpHW9lOguleFCtmx1WJg+iDcDvCB8wmwqcjAn8c7AmqjHM12Qb3qwy9w0ZJVEIp9VQtP/aicDiHDa0ekXkulU5MqehlFFt34NBYS3JuE18BzjIOpNFixsVZHhoAVzLEuKjQtr0csZarLzB+5sG3SJMHu91jVBuW/UmjuP4lx6es5k9NPHuZWQsD+8Tffor4mNAa2eeHkWyiw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=5ef6.627fd0e9.k2205; bh=znEJUBGGGIFvrIcKKeTXa9/N0CUKqW0kN83vokijGzY=; b=fVOREPZCd1w3yKsA/YtR2YIfOEg1+UJnsP5sYjxaRpgBEY/3vvRWk1rF6rDX5htW3dZyb5fSV+gmnjqL78AYvovHKchpeBnT0iED7sBFjTVFxqnNIe2Sv95KdpOwv9EkSeb9Yal4Eq90UdzxXV7BFW8zNlx7nuKuQ4MHgSS/14uZ39tPKzFkJvpndsFaYBA0bMcQhYJQaVBCTb/Mul7Th/QLhzrGbb99nJeMuxZI1ddroYdNWDzocUz6geo0FzDwx9CoOosNCKsJamGbLyl3k8L194uLNfTNWsG1EnUq6LoWrIzgSnufre61IKNExBjLimcF+j443/nifsGKCAA7og==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 May 2022 15:55:20 -0000
Received: by ary.qy (Postfix, from userid 501) id 291174032747; Sat, 14 May 2022 11:55:18 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id D0AAB4032729; Sat, 14 May 2022 11:55:18 -0400 (EDT)
Date: Sat, 14 May 2022 11:55:18 -0400
Message-ID: <55b35059-9b87-3e1e-5b58-0457e2143107@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <87r14wfaqh.fsf@fifthhorseman.net>
References: <20220513233149.B96E4402B887@ary.qy> <87r14wfaqh.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/OIB0Kt2aIJWTQN6_OZhrTiyF4tY>
Subject: Re: [xml2rfc] future work: a <bcp26> element, by analogy with <bcp14>
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2022 15:55:29 -0000

>> I sure hope not.
>
> I agree it's awkward, but I know of several registries (e.g. TLS
> ciphersuites) where the goal is to let people register a new codepoint
> fairly freely ("let 65,536 flowers bloom") but it would be a disaster if
> someone were to casually amend the details associated with, say,
> TLS_DHE_RSA_WITH_AES_128_GCM_SHA256.

But that's not how it works.  For FCFS, see RFC 8126, section 4.4, 
particularly the third paragraph. For Specification Required, see 4.6, 
where it says changes have to be approved by the designated expert.  As I 
may have said once or twice, this isn't supposed to replace the people 
maintaining the protocol registry, but to make their job easier.

>>> How do we handle tweaking the entrypoints for ranges with specific commentary?
>>
>> With adjacent text.  I have no illusion that IANA will be maintained
>> automatically, but we can make the common cases easier.
>
> I see.  Do you (or anyone else on this list) know how IANA maintains the
> registries themselves?  are the *.xml and *.xsl files published in
> rsync.iana.org::assignments the source (in the sense of "preferred form
> of modification"), or are they generated files, produced from some other
> datastore?

I believe that they're generated from an internal database at PTI. 
Nobody's proposing to change that.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email