IETF Logo Mail Archive

[regext] Re: WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)

"Gould, James" <jgould@verisign.com> Thu, 16 October 2025 13:20 UTC

Return-Path: <jgould@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 6410A74EDDDB; Thu, 16 Oct 2025 06:20:56 -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=unavailable 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 iCE9GFIst54z; Thu, 16 Oct 2025 06:20:55 -0700 (PDT)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.30]) by mail2.ietf.org (Postfix) with ESMTP id 50B2E74EDC21; Thu, 16 Oct 2025 06:20:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=4130; q=dns/txt; s=VRSN; t=1760620848; h=from:to:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=cUpEBNxZBPqZ9J8tUgxmyvtqBnnjGXuP1EwFVQEGAJg=; b=L6Dqlj6UzLib963qZmG1mIbR6MN6LvVst66aY8NnrwCNU5cvIVEN7w55 zM05KoGzEO5zuK+AiJxnSbhaYtWTA0GTvcr+8Ah/6388zf+rym7+xAgrw P/qefUUqoPjszMgRBHc505vNDRti67MHZJjJhXaDYXvXRbhpbfkbc7aOo De0elHgPOntzM2tl4oB9A+jV9rHGk5xeKVtb1Vv0j/7xMK1Uc4Cdl4Dhu VgrfU2UevUYJlnqfar1tXSbsiELFZyRbrJACp9ScWkk11aRj5DwM7uOKZ hPGC9U8XI20/dHO4i8CEowyg79rDmlvPp+3PjjFsdfut7SfUcNvyAry+s A==;
X-CSE-ConnectionGUID: 03btNu0TQ7eB+um/cctcZg==
X-CSE-MsgGUID: IKjzDj8vQCadfDpbIA+leg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:lOxKkaxNIYXfvaF3SQd6t+fixyrEfRIJ4+MujC+fZmUNrF6WrkUOm jBOWTyHPfzYazbyfNEnPt7j9E4F65XUzN5rSlNqqi00HyNBpPSeCIXCJC8cHc8wwu7rFxs7s ppEOrEsCOhuExcwcz/0auCJQUFUjP/OHvymTredYEidfCc8IA85kxVvhuUltYBhhNm9Emult Mj7yyHlEAbNNwVcbCRNuspvlDs15K6v4WtB4ARkDRx2lAS2e0c9Xcp3yZ6ZciOQrrl8RoaSW +vFxbelyWLVlz9FIs+liLvybnoRSbfUOwWU4lIOM0R1qkEfzsCa+v9T2Ms0MS+7uR3Q9zxC4 IwlWaiLdOscFvakdNI1CEAETn4kbcWqz5ecSZS3mZT7I0TuLSOwk602ZK08FdVwFu1fWQmi+ RGEQdykg9/qa++emdqGpudQassLdJLhIKUC4k1ZkjzzTusjBpvIX6746ooNtNswrpgm8ff2Q us9RmNQSjnwO0QJJFwQEop4levumGPkdXtTr1f9SagfujCVllAvluGwapyPI7RmRu0M9qqcj mDJ+Hn9DjkEOcae0juK9DSngeqncSbTBNtMS+TiqqACbFu7508RGjEUBUWCivC1hGKmUfN2a EgZ9X97xUQ13AnxJjXnZDWjoHmAuhMaUddbELhmsB+A0KvP4gmfQGMDSxZNbdU8v4k3SCAkk FiTkLvBDDpjoZWVWWjb66z8hT+oMCYJaG4PeSFBVwYK7sn/5YwjklfVQ9liC7Kvn5j4ASnYw j2Wom45nbp7pdQG2Kir4XjGji6i4J/TQWYICh7/W2Oh4VpmYoO1P9Xt8kbBq/NBN8OTSR+Au Hdd3daE9+ZIBpaI/MCQfNgw8HiSz67tGFXhbZRHRvHNKxzFF6afQL1t
IronPort-HdrOrdr: A9a23:TtxqiKDetyKbRajlHel155DYdb4zR+YMi2TDj3oBLCC86qSj5r qTdYcgpHvJYVEqKQwdcLG7SdK9qBznlKKdjbN6AV7mZniFhILKFvAf0WKB+V3d8kTFn4Y36U 4jSdkcNDSaNzRHZLPBjjVQZOxO/DDoys2VbKzlvhBQpElRGsddB00SMHfjLqRZfng/OaYE
X-Talos-CUID: 9a23:BjFC1mxCQUDZOnV54y7rBgVMQco5VGCF8E6PLmX7FGMuQ7aJQm2frfY=
X-Talos-MUID: 9a23:tEn9gQw0RNixmBc8ySi8tpszrZKaqIWNClIhk8UYguKNOSJcIz28pXezT4Byfw==
X-IronPort-AV: E=Sophos;i="6.19,234,1754956800"; d="scan'208";a="41671246"
Received: from MILG1WNEX01.vcorp.ad.vrsn.com (10.246.152.21) by MILG1WNEX01.vcorp.ad.vrsn.com (10.246.152.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.17; Thu, 16 Oct 2025 09:20:35 -0400
Received: from MILG1WNEX01.vcorp.ad.vrsn.com ([10.246.152.21]) by MILG1WNEX01.vcorp.ad.vrsn.com ([10.246.152.21]) with mapi id 15.02.2562.017; Thu, 16 Oct 2025 09:20:35 -0400
From: "Gould, James" <jgould@verisign.com>
To: "shollenbeck=40verisign.com@dmarc.ietf.org" <shollenbeck=40verisign.com@dmarc.ietf.org>, "andy@hxr.us" <andy@hxr.us>, "draft-ietf-regext-ext-registry-epp@ietf.org" <draft-ietf-regext-ext-registry-epp@ietf.org>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] Re: WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)
Thread-Index: AQHcPgXzw5dq9yY6MkacgrG/MhVSLbTE9bwA///Nh4A=
Date: Thu, 16 Oct 2025 13:20:35 +0000
Message-ID: <736921C1-9BB4-46C1-85C3-68AF3AEC335E@verisign.com>
References: <176038761756.679481.14812728809171611120@dt-datatracker-84f8f646b-tg6mn> <554fdd1e-ad5e-45f4-af95-1852c5e4152a@hxr.us> <5e6e56ef8f7c4639a030b21d080bdd94@verisign.com>
In-Reply-To: <5e6e56ef8f7c4639a030b21d080bdd94@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.101.25092124
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C837675341BB9D4E855C6104973D7B26@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: Q6AUQVJGNM6X3HXBZOEUVIYFMJVJHRTH
X-Message-ID-Hash: Q6AUQVJGNM6X3HXBZOEUVIYFMJVJHRTH
X-MailFrom: jgould@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: WG Last Call: draft-ietf-regext-ext-registry-epp-00 (Ends 2025-10-27)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/cYve31GS-i_K73DaqpDeLjbFulo>
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>

Scott,

I believe the language needs to be "IETF namespaces SHOULD be reserved for IETF specifications" to cover the use case of the registration of implemented Internet Drafts that have been abandoned by a working group.  This case came into play for the registration of "Verification Code Extension for the Extensible Provisioning Protocol (EPP)" that is associated with the abandoned draft-ietf-regext-verificationcode-06.  The ICANN RST 2.0 requires for the extensions to be registered in the EPP extension registry, which then required the registration of the implemented "Verification Code Extension for the Extensible Provisioning Protocol (EPP)" (draft-ietf-regext-verificationcode-06) that would not be able to register the IETF namespace.  I believe the same use case applies to the abandoned IDN Mapping draft in draft-ietf-eppext-idnmap-02, which has been implemented by many registries and registrars.  Changing of the namespace is not an option based on the implementation impact and interoperability with the registrars.  This is a true corner case, but it needs to be covered with a SHOULD instead of a MUST. 

Thanks,

-- 

JG 



James Gould
Fellow Engineer
jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/> 




On 10/16/25, 8:21 AM, "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>> wrote:


Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. 


> -----Original Message-----
> From: Andy Newton <andy@hxr.us <mailto:andy@hxr.us>>
> Sent: Wednesday, October 15, 2025 3:00 PM
> To: draft-ietf-regext-ext-registry-epp@ietf.org <mailto:draft-ietf-regext-ext-registry-epp@ietf.org>; regext@ietf.org <mailto:regext@ietf.org>
> Subject: [EXTERNAL] Re: [regext] WG Last Call: draft-ietf-regext-ext-registry-
> epp-00 (Ends 2025-10-27)
>
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Hi,
>
> I have the following comments:
>
> 152 for both syntactic and semantic correctness. For example, IETF
> 153 namespaces should be reserved for IETF specifications.
>
> This should be changed to:
>
> IETF namespaces MUST be reserved for IETF specifications.
>
> I think we should also add the following:
>
> Extensions and any normative reference necessary to implement the
> extension
> MUST NOT be denoted with "work in-progress" or any similar description.


[SAH] Those are both good suggestions. Thanks!


Scott
_______________________________________________
regext mailing list -- regext@ietf.org <mailto:regext@ietf.org>
To unsubscribe send an email to regext-leave@ietf.org <mailto:regext-leave@ietf.org>

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