[regext] Re: Roman Danyliw's Discuss on draft-ietf-regext-ext-registry-epp-07: (with DISCUSS and COMMENT)

Scott Hollenbeck <sah@sahollenbeck.com> Sun, 02 August 2026 14:38 UTC

Return-Path: <sah@sahollenbeck.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 A541812254D23; Sun, 2 Aug 2026 07:38:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785681523; bh=f0yQ/j/uimELFHyLMlojEgaaia2H1GYERmK4mktyhmM=; h=From:To:Cc:References:In-Reply-To:Subject:Date; b=iO9owmrLwjN2WHFEZShLJfXkBJeNCgsOUBSjaU9eDD6XnD0aA9Hq4yecGa5SX8G81 NByaNoBiDJOhE6a7cCAesdvDVMU41dXTJAKKXvWWQG5mq2JwBAYi+BSfgdTZHZ613V WgcEZfq2sJUDBeAXGO2tvtQaY/q6DpvECDDC42WE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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=sahollenbeck.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 H-eFg9FJNO3C; Sun, 2 Aug 2026 07:38:43 -0700 (PDT)
Received: from procuratus.net (procuratus.net [96.231.245.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1E29512254D1E; Sun, 2 Aug 2026 07:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sahollenbeck.com; s=default; t=1785681513; bh=f0yQ/j/uimELFHyLMlojEgaaia2H1GYERmK4mktyhmM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:From; b=EBtpR/LNcwCQcSkKKkJxDbB8uN9B/hM+KoAyswStGhJG25m+CWU0d8r+MfhrX1WUV sQK+0o9Z8qshJLiLG7T7yuIjGa3yt33hphTJlIvbh2rS2+xfDcMpIfaGsEPcOJb0gj nUHqX0nVc7TabGmQo8xnpKBmvEc0UApnmdLW11i0Kove1exWF9e8OO1L8aTSSLGxUB vNXZGXn8rGtaQ74r4PDGLWNCSftwnJLZdAK6bh3AY30MHHDUuyr+pXt0F8uz1s1TzD JN6xKbeTzydzG5MSAGUhldwGdlyjieg59zDnqFj3aHi8kfKfCS0VXIXKJpz+nusqKq f9F8Hz8dUPnRg==
Received: from Mustang (procuratus.net [96.231.245.35]) by procuratus.net (Postfix) with ESMTPSA id 0B3CC8007F2; Sun, 2 Aug 2026 10:38:33 -0400 (EDT)
From: Scott Hollenbeck <sah@sahollenbeck.com>
To: 'Roman Danyliw' <rdd@cert.org>, 'The IESG' <iesg@ietf.org>
References: <178042664370.2305356.9224013877981664351@dt-datatracker-5b4c8598b5-4ztf9>
In-Reply-To: <178042664370.2305356.9224013877981664351@dt-datatracker-5b4c8598b5-4ztf9>
Date: Sun, 02 Aug 2026 10:38:31 -0400
Organization: SAHollenbeck LLC
Message-ID: <000001dd228c$975ea130$c61be390$@sahollenbeck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDTOuDkEJbDkvwFA6bT1f4hekv+nLien2FQ
Content-Language: en-us
Message-ID-Hash: CAKGCI7TVHZVM66PYYVD2VA3W47SKTIZ
X-Message-ID-Hash: CAKGCI7TVHZVM66PYYVD2VA3W47SKTIZ
X-MailFrom: sah@sahollenbeck.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: draft-ietf-regext-ext-registry-epp@ietf.org, gavin.brown@fastmail.uk, regext-chairs@ietf.org, regext@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Re: Roman Danyliw's Discuss on draft-ietf-regext-ext-registry-epp-07: (with DISCUSS and COMMENT)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/BPNt6aUFWIup3Y_y-lmH5HHuHPU>
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>

Roman, your discuss for this draft is still open. I addressed the points described below. What remains to be done? I have one additional comment that I'll add below.

Scott

> -----Original Message-----
> From: Roman Danyliw via Datatracker <noreply@ietf.org>
> Sent: Tuesday, June 2, 2026 2:57 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-regext-ext-registry-epp@ietf.org; gavin.brown@fastmail.uk;
> regext-chairs@ietf.org; regext@ietf.org
> Subject: [regext] Roman Danyliw's Discuss on draft-ietf-regext-ext-registry-
> epp-07: (with DISCUSS and COMMENT)
> 
> Roman Danyliw has entered the following ballot position for
> draft-ietf-regext-ext-registry-epp-07: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-
> ballot-positions/
> for more information about how to handle DISCUSS and COMMENT
> positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-regext-ext-registry-epp/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> ** Section 2.1.1
>    The IESG should appoint a primary designated expert and a small
>    number of individuals (perhaps 3 - 5) to serve as backup designated
>    experts as described in Section 5.2 of [RFC8126].  The primary
>    designated expert is responsible for conducting all reviews requested
>    by IANA.  The secondary designated experts are responsible for
>    conducting reviews as a consensus-based group if the primary
>    designated expert is unavailable.  In cases where a registration
>    decision could be perceived as creating a conflict of interest for a
>    particular Designated Expert, that Expert SHOULD defer to the
>    judgment of the other Experts.  The designated experts MUST use the
>    existing regext mailing list (regext@ietf.org) or its successor for
>    public discussion of registration requests.
> 
> This language above is a slight reinterpretation of Section 5.2, RFC8126.  Is
> that really necessary as the following are underspecified:
> 
> -- What is a “consensus-based group” (e.g., rough consensus, majority,
> unanimity)
> 
> -- When should a DE NOT recuse if there is a COI?
> 
> -- Is there a requirement being set on the IESG that it has to approved more
> than one DE here (as the language reads, the “IESG should …”)?

[SAH] I've added text to address these questions, but if you still believe that the text is a slight reinterpretation of Section 5.2, RFC8126, would it help to change the first paragraph in Section 2.1.1 to explain that the intention is to describe how 8126 is applied? Perhaps something like this:

OLD:
A high-level description of the role of the designated expert is described in Section 5.2 of RFC 8126 [RFC8126].  Specific guidelines for the appointment of designated experts and the evaluation of EPP extensions are provided here.

NEW:
Section 5.2 of RFC 8126 [RFC8126] describes the role of designated experts. This section describes how the practices described in RFC 8126 are applied for evaluation of EPP extension registration requests.

If this isn't sufficient, I could really use specific guidance to better understand what you're looking for.

Scott