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)

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 18 February 2025 19:30 UTC

Return-Path: <shollenbeck@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 49832C1CAE75 for <regext@ietfa.amsl.com>; Tue, 18 Feb 2025 11:30:32 -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 tCvTHHqmVI7p for <regext@ietfa.amsl.com>; Tue, 18 Feb 2025 11:30:28 -0800 (PST)
Received: from mail5.verisign.com (mail5.verisign.com [69.58.187.31]) by ietfa.amsl.com (Postfix) with ESMTP id 35C37C1E1862 for <regext@ietf.org>; Tue, 18 Feb 2025 11:30:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2038; q=dns/txt; s=VRSN; t=1739907028; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=kpeHcEx0Tzp/AjPT/gLbv1Z5rhLTcd1B8Lc9FT77x2Q=; b=dSrwT0HK+jgSjSlx7osk2X1e8T7jCnAJNWjHf6fl2oNA2wniTbsAo3si QGUWxeCIMWU6XzPApBbHWW9kfgtiUO952gscnpdY4+i8jxP/hWF1H6u+a fJltRDJ1HJPqUzq7xvM/3+1l9CWaZSjelh+SwcodsEyQDLJQew8VzO9MF wVy1tj8ont2dgbhlRnh7vNitY7hRcDWtEbg2qtFo7h1MNU6K9uMbsxLKr DFkmXxODSqSsJGctTK5Gq7Z3KHIkWhh/+/6vWk9T8R+LZ4z2N6laNuh/e bT+g6cdNeJzE/jJWVSKEeB9midZ+QgEoNZmQDxu7WOwMsuhDQ6NSawmDF g==;
X-CSE-ConnectionGUID: pTrNNA3nRAG+cMnc7WCZqA==
X-CSE-MsgGUID: gI1tXrR0TWi//vIOiamWlg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:VZ8R/q/dZfhPQFk5FsSfDrUD/n+TJUtcMsCJ2f8bNWPcYEJGY0x3m mQeXTuGPf3eYjCkftl1bYrn9EgD7JLUn9NlGwc5rykxFiIbosf7XtnIdU2Y0wF+jCHgZBk+s 5hBMImowOQcFCK0SsKFa+C5xZVE/fjWAOK6UKicZ3wZqTZMEE8JkQhkl/MynrlmiN24BxLlk d7pqqUzAnf8s9JPGjxSsvnrRC9H5qyo5WtC5wxmOJingXeF/5UrJMNHTU2OByagKmVkNrbSb /rOyri/4lTY838FYvu5kqz2e1E9WbXbOw6DkBJ+A8BOVTAb+0Teeo5iXBYtQR8/Zwehxrid+ /0U3XCEcjrFC4WX8Agre0IBT3whZ/0uFIjvehBTueTLp6HPWyW0n6U2VCnaN6VAkgp8KTkmG fD1tFnhx/1M7g676OvTdwViuigsBNHXJqU5kypm9xj2Tv0DR5ucfI74/PYNiV/chugWdRrfT +AjT2NQSjnwO0cJJFwQEop4levumGPkdXtTr1f9SagfujCVlVMqluGwa5yJK7RmRu0M9qqcj nnG+GD9DxcQOdec4SSI6HO3h+DJ2yj8Xer+EZXjq6863QTImAT/DjUZdAKnkeOD0nKBWpUYN W0z+yMrkqw9oRnDot7VGkfQTGS/lhcaV8t4E/0grhyWooLO7gmUFnQsTzNdZpohrsBeeNAx/ lWTmYr2AzF/6OfQUmyHsLKVtna4Pm4fN2lbIzEeVg1D6N7myG0usi/yoh9YOPbdprXI9fvYm lhmcABWa20vsPM2
IronPort-HdrOrdr: A9a23:3blepqq2aeSKBYxONRix4fEaV5r2eYIsimQD101hICG9Ffbo8v xG/c5rtyMc5wxwZJhNo7690cq7Lk80nKQdibX5Vo3SPzUO1lHIEKhSqaXvxDH6EzDz+6p3xc 5bH5RWOZnVAUJhhcj3pCu1A78bquWvweSNif3Fx3lgCTt2bbpthj0VNi+AHlZoSBJ9CZ01KZ qZ6qN8zAadRQ==
X-Talos-CUID: 9a23:6QNj9WAzGe7tpnv6EzFb7mgyM5sjSFTyj3z1JUTnNk1bUZTAHA==
X-Talos-MUID: 9a23:X8YUlgwctsyDiAfR/jSdhonHDvWaqKuPUVw9i69eh/aFcmtuGhCchTGIRoByfw==
X-IronPort-AV: E=Sophos;i="6.13,296,1732579200"; d="scan'208";a="35985136"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) 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:30:27 -0500
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; Tue, 18 Feb 2025 14:30:27 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>
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: AQHbgjeQ0B/bj2D1rUebXe7EzXplo7NNcVWg
Date: Tue, 18 Feb 2025 19:30:26 +0000
Message-ID: <17abe4eb757d4203b67367a66e823866@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:
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: PA2OXP6FEKDO4CHPM56NK7DYUMMJSFOB
X-Message-ID-Hash: PA2OXP6FEKDO4CHPM56NK7DYUMMJSFOB
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
CC: "Gould, James" <jgould@verisign.com>, "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/O25BEHsxXCdLUpBMTbT1_skshLk>
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: Andrew Newton (andy) <andy@hxr.us>
> Sent: Tuesday, February 18, 2025 2:02 PM
> To: Hollenbeck, Scott <shollenbeck@verisign.com>
> Cc: Gould, James <jgould@verisign.com>; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: Charter question (was Re: CALL FOR
> ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-
> http)
>
> 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> 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?

[SAH] Because it's a process-heavy activity that may be unnecessary. If it *is* necessary, fine, let's do it. It would be helpful if our WG chairs would weigh in on the topic.

Scott

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