IETF Logo Mail Archive

[regext] Re: Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)

"Gould, James" <jgould@verisign.com> Tue, 18 February 2025 19:21 UTC

Return-Path: <jgould@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C792C1840CD for <regext@ietfa.amsl.com>; Tue, 18 Feb 2025 11:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 omQcP472jJri for <regext@ietfa.amsl.com>; Tue, 18 Feb 2025 11:20:59 -0800 (PST)
Received: from mail5.verisign.com (mail5.verisign.com [69.58.187.31]) by ietfa.amsl.com (Postfix) with ESMTP id DD585C1ECA86 for <regext@ietf.org>; Tue, 18 Feb 2025 11:20:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2414; q=dns/txt; s=VRSN; t=1739906459; h=from:to:cc:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=gwhkt7//6ioAfMY8Gv6gOk1C6Z6RZ+tLWseR6aoH8Wk=; b=URhS4SZLMjNhiHZwGzyNtxELh0fapD6myT6f4W6+BXHDybRHyG73TF8y KtaQ4RgJLqazWx1QBTkkyWkavuqakI2ci6Y0IluINyXjr2MEJ/SUWJ41N e2Tsn3sGbdmuLBozDe+NgdHp3eO7WYAQFV1ljVUGE+429d2xWSOFookOt Ey2qvdw6QklEDbmb1QHMJ0mk5jMHR9uLO32uSgO+HmPQzIqmgkYsXejh2 A26H9A1la7GWWKXFXF6lsFNtvstIjwO5ausCW2Ccjj+58/gXcxFUvahm+ ITOgU5Ti0LyQyvLS4n4n5l1mrpVD7NgUxHoPWLfiAZD5JhHfveaWqXg3I g==;
X-CSE-ConnectionGUID: 8OCgFYwESj+wQDgYO49vJw==
X-CSE-MsgGUID: UB3E/P1oQQqlUnjvaZIPeg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:sqmI5qgg/Kyu86PWfQn1fOdTX161ExEKZh0ujC45NGQN5FlHY01je htvWGzVbviNYzD8LtFxaYqy9x5QvZGDm4dlSlZo+SlkEysW8JqUDtmndUqhZCn6wu8v7q5Ex 55HNoSfdpBcolv0/ErF3m3J9CEkvU2wbuOiTraCYmYpGFMMpB4J0XpLg/Q+jpNjne+3CgaMv cKai8DEMTdJ4RYtWo4vw/zF8UgHUMja4mtC4wRkPKAT4TcyqlFOZH4hDfDpR5fHatQMdgKKb 76r5K20+Grf4yAsBruN+p7nclcHS6LlJgOHjHxbQcCK2nCucQRrj87XnNJFAatmo23hc+JZk b2hhrTpIesdBZAgrcxGO/VuO3onYfAZou+vzU+X6qR/x2WeG5fl66s2UBFuZeX08M4vaY1F3 aRwxDzg8nlvLg95qV62YrAEuygtECXkFNM4kX5O/C70NvRlXqnvTJTtuY5G/ihl06iiHd6GD yYYQRBVSk3/RTB/Yg5RFpk5hv/uj3W5bSdDrhSeoq9fD2r7lVQ3iee2doOIIZrWFa25nW7Bz o7C12b2BQweOPSBxCCE6XOjgKnEmiaTtIc6T+DppqMy2gT7Kmo7NTdNeByD+P6As1e6ZtRdN UUm2xIjov1nnKCsZpynN/Gim1aNuBINc9pACasn82ml0Kfb7haFLmkJUjAHb8Yp3PLaXhQgz FnQgNXkFWQ29aaLUzSY96zRpzT0MzITdCkcfzQCCwAC5rEPvb0Os/4Gdf47eIbdszE/MWiYL +yixMTmu4gusA==
IronPort-HdrOrdr: A9a23:/zlAUaqddGJegTm3mUx3BMAaV5r7eYIsimQD101hICG9Kvbo8/ xHnJwguSMdEF4qKQwdcKO7Sc69qBTnhOJICOgqTM2ftWbd2FdAQLsJ0WKm+UyEJ8SczJ8j6U 4DSdkcNDSYNzET5voSojPIcerIq+PpzEncv4bjJgBWIz2CBZsM0+4zMHf8LqQ/fng+OXJyfq DsnvaviQDQAkgqUg==
X-Talos-CUID: 9a23:RbJkNWvT4KoctE007/aI8ptR6It1VVbS4kbPDnS6SnlQZLKkbgPB5oF7xp8=
X-Talos-MUID: 9a23:vztXxAs8bIB5ByTef82nuRs5GYBQuqOXMVkJrJMEpcC2FBR9NGLI
X-IronPort-AV: E=Sophos;i="6.13,296,1732579200"; d="scan'208";a="35985021"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) 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; Tue, 18 Feb 2025 14:20:56 -0500
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2507.044; Tue, 18 Feb 2025 14:20:56 -0500
From: "Gould, James" <jgould@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: [EXTERNAL] Re: [regext] Re: Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)
Thread-Index: AQHbgjeQmdPiaqoE4kiKGcWu6tLkirNNcAgA
Date: Tue, 18 Feb 2025 19:20:56 +0000
Message-ID: <C4B535FD-1EEC-4CF2-A33C-C16AE6CDE764@verisign.com>
References: <A4407EAD-3F1B-452C-9F5B-764C80763AC1@elistx.com> <CAAQiQRdwaibyd7cOXGqGigzoOyXPxz34xNMMbiJ6qom0bCQyjQ@mail.gmail.com> <92872b26ce2b44159f296b138b11ca9c@verisign.com> <CAAQiQRfDEp1TP0wPwY8pXy_9R2_-Horo-opTf1svJCzs+DZc5g@mail.gmail.com> <318DA0CE-A720-442C-A4F2-D394CE6E317C@verisign.com> <84ae80afd9bb4f27ba54f98d5a4948fb@verisign.com> <CAAQiQRdHN2f7sHMEkH1hGV3jmrCMgxmWA9RZc_sBV6uSFwtqhw@mail.gmail.com>
In-Reply-To: <CAAQiQRdHN2f7sHMEkH1hGV3jmrCMgxmWA9RZc_sBV6uSFwtqhw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.94.25020927
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <37E1E78D03AF0641BBE67057EE795D59@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: AJHQ2GRVBT3BHCZSZ2RWIVKGEYARFFJY
X-Message-ID-Hash: AJHQ2GRVBT3BHCZSZ2RWIVKGEYARFFJY
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
CC: "regext@ietf.org" <regext@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Re: Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/LH5z50_9NFRuFFMi7ypblHY-jxU>
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>

Andy,

Very clearly RFC 7451 references both RFC 5730 and RFC 3735 (guidelines), which means that transport extensions should be registered in the EPP extension registry.  By adding the transport extensions to the EPP extension registry, they meet the letter of the REGEXT charter, so there is no need to re-charter.  Since this is the first instance of adding a new EPP transport, we can add the missing EPP extension registry registrations to address the gap.     

Does that make sense?

-- 

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 2/18/25, 2:01 PM, "Andrew Newton (andy)" <andy@hxr.us <mailto:andy@hxr.us>> 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. 


On Thu, Feb 13, 2025 at 9:58 AM Hollenbeck, Scott
<shollenbeck@verisign.com <mailto:shollenbeck@verisign.com>> wrote:
>
>
> [SAH] I don't see anything in RFC 7451 that would preclude registration of a new transport mapping in the IANA EPP extension registry. Jim's proposal is worth considering.


"Extensions should be evaluated for architectural soundness using the
guidelines described in RFC 3735..." Very clearly 7451 is about
extensions described in RFC 3735. 7451 does say IETF standards don't
require DE review, but that doesn't get around the purpose for this
registry or that the IETF should be misusing its own protocol
registries just to avoid following the process.


Why the strong pushback on a recharter?


-andy

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