[regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03

James Galvin <galvin@elistx.com> Wed, 10 July 2024 20:35 UTC

Return-Path: <galvin@elistx.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 C0A61C15199D for <regext@ietfa.amsl.com>; Wed, 10 Jul 2024 13:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=elistx-com.20230601.gappssmtp.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 oGOgSD4Xe4DM for <regext@ietfa.amsl.com>; Wed, 10 Jul 2024 13:35:51 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECC4CC14F6E2 for <regext@ietf.org>; Wed, 10 Jul 2024 13:35:51 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id 46e09a7af769-7037c464792so64195a34.2 for <regext@ietf.org>; Wed, 10 Jul 2024 13:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx-com.20230601.gappssmtp.com; s=20230601; t=1720643751; x=1721248551; darn=ietf.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=wNR42d2NsSVy27hbXx/pJtE1wUjqcOakK0SdZAJ0S78=; b=fo9LTx6jkzX1rv13Aw+c92Eq+3o4F4FGKvSCDgpTFAEGQCvjFtKXdFIZXMgyx6OWOy xU/Zk/fVRexlsWrDhEfxHTr1FGec366iALE183FXg3ukIufTUL3MIyBUmN+sfV+IiC8K bHLF3N1IPFKLQaip2CKNEu0S4fDdZK7p7IZJXWFZ6XV+Arrkhl84S3QlOIbnrXDoKnlA aTkPmW7U4wl+IArgtscZI/zuH5SOkGU4HrgkAGYgsKokrERnQ0rz/Ls7HSsh89LnhSC6 fmAt2znyCSllz6YdKsrGVxIu2pCAyYe40FNI0RANczC72Fp5QV6pauoHiyap5v2j7/WK WCSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720643751; x=1721248551; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wNR42d2NsSVy27hbXx/pJtE1wUjqcOakK0SdZAJ0S78=; b=AG4Fnpcda4cg4A1yYmHADuLXmbmsNK+sAlxFJSN0PbTwnJTHfhNANyjlHIhhYIT95q Qj/8/eLDWUNXNcZVhQv9rVFiIHcN5MQkwjfYmaV8SScwJbsDpKUKHFaE61b7bA3HAMTb jEWgKikdPKhkBbVOWvWQZr8UyMnawR+aWd9FBlVvz/ihXBKSzmyWNB7oO1AunMRKmRu3 FnNDRMP/DndLXSnYnHG7j7FDQVM0yOi/5YSKFkrtima5VDGDW8FoG7konKFkQBcOxLgK L2Pkive73qUVPofj3jC/A5+XwNVCYgNWFDgYTvYOP414WvQzB2+Um1P3W4gyiRroDex7 MCkA==
X-Gm-Message-State: AOJu0YzLmp0XJLvyenXkK5I7VmD0MHTnJH/mERgP6J8KrfGOB/SU1F9t T40X36+U5kCPRFVE0/6fpS5wQQO7D3v9vCSoLOFoDH0CIVkN/5ASt8NE4i06dk52X/Dz2C8u+Hq 6
X-Google-Smtp-Source: AGHT+IHoI8biJIEq+XqcfGot15IxLDjFQOzyX0pAg9fgbN0euxGXMwPuBoOS/PcnvZW/0rmXmFo/Cg==
X-Received: by 2002:a05:6830:3a8c:b0:703:60f4:30d0 with SMTP id 46e09a7af769-70375a06a21mr7632953a34.8.1720643751086; Wed, 10 Jul 2024 13:35:51 -0700 (PDT)
Received: from [10.0.0.20] ([2601:147:4500:cf70:503:7978:bd50:bc2b]) by smtp.googlemail.com with ESMTPSA id 6a1803df08f44-6b61b9d5f7esm19800746d6.38.2024.07.10.13.35.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jul 2024 13:35:50 -0700 (PDT)
From: James Galvin <galvin@elistx.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Wed, 10 Jul 2024 16:35:50 -0400
X-Mailer: MailMate (1.14r5937)
Message-ID: <33C6C448-65EE-42B0-8132-CB66356991AB@elistx.com>
In-Reply-To: <ab9f8dc56d6d4a72b703f1022f4956e6@verisign.com>
References: <591E988C-2F3E-45CA-9E43-874C50CD0F5B@elistx.com> <561D7723-C1A0-4DD0-BD96-1302251576BD@elistx.com> <ab9f8dc56d6d4a72b703f1022f4956e6@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: 3JMWT2KSLY46DLTOFAEKFQMPE4ZQWQKX
X-Message-ID-Hash: 3JMWT2KSLY46DLTOFAEKFQMPE4ZQWQKX
X-MailFrom: galvin@elistx.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/hdzsBssbPEm2J1fXOzXGUgxRZnI>
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>

As co-Chair, I was giving this document and discussion a quick review before closing the WGLC and handing over to the Document Shepherd and I noticed what I believe is an editorial point.


Speaking as a working group participant, SAC125 offers a complementary analysis about sacrificial nameservers as currently appears in Section 5.  How do you feel about adding a single sentence to the introduction to Section 5, something like the following:


For a broader consideration of the practice and its potential impact on both registries and registrars, “SAC125: SSAC Report on Registrar Nameserver Management” offers some complementary insight (https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-125-09-05-2024-en.pdf)


If you agree and agree it’s just an editorial nit, I’m comfortable letting it get sorted with the Document Shepherd after the WGLC closes and before submission to the IESG.

Of course, if anyone else has an opinion or comment please do jump in.

Thanks,

Jim


On 2 Jul 2024, at 15:29, Hollenbeck, Scott wrote:

>> -----Original Message-----
>> From: James Galvin <galvin@elistx.com>
>> Sent: Monday, June 24, 2024 9:27 AM
>> To: REGEXT Working Group <regext@ietf.org>
>> Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
>>
>> 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.
>>
>> The Chairs have decided to extend this WGLC last call for two weeks, one more
>> week from the date of this message.  There has only been on indication of
>> support and two different threads discussing some minor changes.  We would
>> like these discussion to resolve and for there to be more indications of support
>> for this document.
>>
>> Please indicate your support or no objection for the publication of this
>> document by replying to this message on list (a simple “+1” is sufficient).
>>
>> If any working group member has questions regarding the publication of this
>> document please respond on the list with your concerns by close of business
>> everywhere, Monday, 1 July 2024.
>
> [SAH] Good to go now?
>
> Scott