IETF Logo Mail Archive

[regext] Re: simplifying the extensions rules

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 02 April 2025 15:57 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: regext@mail2.ietf.org
Delivered-To: regext@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2499D168064D for <regext@mail2.ietf.org>; Wed, 2 Apr 2025 08:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Pfbkg2ZSNkR for <regext@mail2.ietf.org>; Wed, 2 Apr 2025 08:57:35 -0700 (PDT)
Received: from mail2.verisign.com (mail2.verisign.com [72.13.63.31]) by mail2.ietf.org (Postfix) with ESMTP id A03EF168063D for <regext@ietf.org>; Wed, 2 Apr 2025 08:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=1204; q=dns/txt; s=VRSN; t=1743609455; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=mU1l+ItU6Ly/Mqfotl05GIQ2bzehjLYaKVxLgXcz3rA=; b=EnPbhIIEzCVtlzUpD/uJspAgL3DAkWr4vJM45siGpwHe1IEbRMqaV65i 9siJ/On+TWf+g8LGsD/l5c6+ajLaJvqwi+pHQMc2yjCd/K9ixqGgHPu6r xmfBIUQyNYRb0tdU4/AMcb4MOAx8jNFKNUfxuN/01GzlZwCGv64N8fu6K Ds6ML5Fz1gKA4NlbUIzuTw+48FVT0tASVXCV9Cu/GbXg1H155v9BLUgN7 6VNOJxpZ6pzpcbXQiVtGWmDs0eQUVncZLEVlqszpK4od608gDoRr9VfdZ FlkYjh8Fh3DsMkLn72u0w1xjq+C73vyKcS5b2uW7mnEp7n/B32XPE/fk8 Q==;
X-CSE-ConnectionGUID: WTVK8oNAR3uK+wb2dpeiiQ==
X-CSE-MsgGUID: FBk7gYQxSh2JgBeIrUcgjQ==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:Vuvrkand03qFw1atoWFi6Fbo5gyJJ0RdPkR7XQ2eYbSJt1+Wr1Gzt xIbDGmHO6uLYmegLdtzYI7j9EoH75SHx9FjHQJq+XtjEy4T+ZvOCOrCIxarNUt+DCFhoGFPt JxCN4aafKjYaleG+39B55C49SEUOZmgH+S6UKicfHgsGWeIcQ954Tp7gek1n4V0ttawBgKJq LvartbWULOf82cc3lk8teTa9XuDgNyo4GlF5gBmP6gQ1LPjvyJ94Kw3dPnZw0TQH9E88t6SH 47r0Ly/92XFyBYhYvvNuqr7aEADXonJNgGIjHdMM4D66vSVjnVvukqTHKN0hXZ/011lrfgoo Dl+ncXYpTMSA0H5sL91vy9wSHgiYPIcqNcrFlDk2SCb5xWun3LEna0yXBluVWES0r4f7Wpmr ZT0JN2RB/wqai3fLL+TE4FRasofwMbDA78hmSFn6xjjVusFAo/JGanS6N5Z5WJl7ixONa62i 8sxQwBJNSvmTi0XYxEJA5UkhKGhij/haSZe7lmSoMLb4UCKlEooj+OraYeOPIDaLSlWth/wS mbu5GT+BhUXMtaSwjmt7H+2h/TOkiW9U4UXfFG93qU62gfOnDxLYPEQfXWRoqa2u3euYNIFC UM+9ws0kKM99nX+G7ERWDX9+hZopCU0WN1PGuk76ymBx6zV6ECVCwAsRzhNefQmpNVwWCdC/ kWEkN75GRRuvaGbD3WH+d+pQSiaMzITdHAEaD9cFE4e/cOlpYAoyxjICNx5FvfzkMfuH3f7x DXiQDUCuoj/RPUjj82TlW0rSRr1znQVZmbZPjnqY18=
IronPort-HdrOrdr: A9a23:6SttH6/j7PIyKvhJONFuk+AFI+orL9Y04lQ7vn2ZLiYlF/Bw9v re/sjzuiWVtN98Yh8dcLO7V5VoKEm0naKdirNhXotKMjOGhEKYaK9v6of4yyDtFmnU5odmuZ tIQuxbBMfrBVZ3yeT38GCDeeoI8Z2i/LqzjenTi01xSxpnApsM0y5iBh2FHlZNSA5KOJo8GP OnjfZ6mw==
X-Talos-CUID: 9a23:gYyhLmie+46OzfZ8i+0YoGQpUDJuTUHj7yfXBWaCUntKC6KfE1OI9aJlqp87
X-Talos-MUID: 9a23:Q5EuTw5mVGsEbOqw4DJgETHhxoxGyafxB3E0ga4G4euLHyFRIQqWgzaOF9o=
X-IronPort-AV: E=Sophos;i="6.15,182,1739836800"; d="scan'208";a="38225280"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.44; Wed, 2 Apr 2025 11:57:35 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) by BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) with mapi id 15.01.2507.044; Wed, 2 Apr 2025 11:57:35 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "kowalik@denic.de" <kowalik@denic.de>, "andy@hxr.us" <andy@hxr.us>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] Re: simplifying the extensions rules
Thread-Index: AQHbo9vrZynyDXVH4kGh4Oxv36WRDrOQxbaA///CCtA=
Date: Wed, 02 Apr 2025 15:57:34 +0000
Message-ID: <c1695bf39fef44c7aa6aa5101a15575d@verisign.com>
References: <173878722078.433175.16116394455327843548@dt-datatracker-6f7f8bdd64-25rl2> <CAAQiQRfxSB_Yek4hoz9ysrOS3Gggb8XEv2omcxbq0o8fHxsJqA@mail.gmail.com> <71596ec2-d518-4228-8ee5-728a43e7c064@hxr.us> <20c0e2a2-2827-4dbc-b8be-95c1275819ff@denic.de> <67aff05e-c703-4292-99bc-a1c26981d0fa@hxr.us> <11c5e931-3800-4f5a-bd51-c04fabdccfdc@denic.de>
In-Reply-To: <11c5e931-3800-4f5a-bd51-c04fabdccfdc@denic.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: OURPNQWUXKGB4T4RBIUAUYWGF5ZOLFQR
X-Message-ID-Hash: OURPNQWUXKGB4T4RBIUAUYWGF5ZOLFQR
X-MailFrom: shollenbeck@verisign.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Re: simplifying the extensions rules
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/g40BwlTaCXr496lOXhXn42uz6h0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

> -----Original Message-----
> From: Pawel Kowalik <kowalik@denic.de>
> Sent: Wednesday, April 2, 2025 11:38 AM
> To: Andrew Newton (andy) <andy@hxr.us>; regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: simplifying the extensions rules
>

[SAH] [snip]

> Also talking about 22 issues seems an amplification to me, as one may think all
> those were related to bare identifiers. If I recall well, being an author of most of
> those reported issues, that maybe 2 or 3 of them were anyhow related. Worth
> noting that the most complex rules are defined to exclude conflicts of identifier
> prefixes (Section 2.2, paragraph 3, Issue #49). In my eyes still underspecified.
> Bare identifiers are very simple in handling in comparison - either they are
> registered or not... just saying.

[SAH] Mostly, but there are still character case considerations.

Scott

v2.30.2 | Report a Bug | By Email | System Status