[regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-07.txt

"Andrew Newton (andy)" <andy@hxr.us> Wed, 31 July 2024 20:16 UTC

Return-Path: <andy@hxr.us>
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 76979C15108C for <regext@ietfa.amsl.com>; Wed, 31 Jul 2024 13:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.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 Cwy5wGRCwfOD for <regext@ietfa.amsl.com>; Wed, 31 Jul 2024 13:16:10 -0700 (PDT)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EF8CC151084 for <regext@ietf.org>; Wed, 31 Jul 2024 13:16:10 -0700 (PDT)
Received: by mail-ua1-x92a.google.com with SMTP id a1e0cc1a2514c-8333a5dc765so1811226241.0 for <regext@ietf.org>; Wed, 31 Jul 2024 13:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1722456969; x=1723061769; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=ziHXrtIj/BSwNkJ8+lJJ0ukChg5XgH3jai70k8WPq84=; b=R44C7t3+ZHtppKvaIWxgRjk/bNURrNO2emigi9oKGHPaewXw1kXlHPOp7XT6pkg6Yo R35j84tf1oV3O6X8uqIBTAYxzPIccKnFiGBaj7svqYQxmg8SdNCpndhodg/e4wzgnzkr AghG3A0SVP9JPF6myd2DZ/P6CSZLg8SsOn/jurbtBJOKtSnh6tOl7daCqlN36wvjMO1a DRNV+uL+Ume7Q7LbnBlT+7thAYxpV9QWiRWuyNDSrYeVMca+DP1htN9e3UCsKQv1nZNt aJnX+as4SCtpTZ6GJ3QltWv+IAH0wjAGDNNUpN3LyGZvONb9OVHAIWvNGn8f80kZHh4l C8eQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722456969; x=1723061769; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ziHXrtIj/BSwNkJ8+lJJ0ukChg5XgH3jai70k8WPq84=; b=WFKa5JntHMkoo1BO+Seq4xjoqHaHYLxyHzLA41wVENV3O4SD6Pr/jd+yQpSAkH0J8c dr/HPB7/cFlD/dseaurgFJGSQqUlmbzQPksHX0HOP3wjgK9zmnIBfRl1s7n7WVzC5qmy j1R6TWrz835O5BlPauqI5p9k3c4PyJG10F+KSu1V8c6i+ajX0iaQuAFAqoamEvzk+8Q7 AXvpkWqGTlPkjUlXue+vC9vkdT80F0tM94D9K5fRugVo/wkzehoGZA29FPmMt4ftszbo 1hO3h7lxdhhLAm4c45v6oYOLeaWb7zS/RBt0kChEZycZlRkhLo+hPtmuJoUyfLypVAGF ToHg==
X-Forwarded-Encrypted: i=1; AJvYcCUd+IezGAeiFv6j+FRt7Jv8pnBUTR/oPbVhDq69GpmiWDJTdhuOhmtGokICTLGUgS0cBf1EF0cpyCtYxWCZ+tY=
X-Gm-Message-State: AOJu0YwU9iN5fB4FbNzdGTJsEVFcz4QaPoq+ZepkqcyFeVMI/FtqzMWo tPIZ0dQa9hq6F3cyXBwQ6OZSvPs60bbrCwH3/OD8KR3U9knBgFDLbTVvvVnrmknPQDGVPG8vpxF B
X-Google-Smtp-Source: AGHT+IGQk35SkX1wL1Q8jigH36YMUSAoLKuQH+G/d5V5jRrsEblIM9YwfCA2w79hza4ppOgl5366iw==
X-Received: by 2002:a05:6102:292c:b0:48f:e683:7b46 with SMTP id ada2fe7eead31-494506ccb9dmr681274137.3.1722456969044; Wed, 31 Jul 2024 13:16:09 -0700 (PDT)
Received: from [10.2.8.160] (pool-72-83-25-32.washdc.fios.verizon.net. [72.83.25.32]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6bb3fb05265sm77406216d6.135.2024.07.31.13.16.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 31 Jul 2024 13:16:08 -0700 (PDT)
Message-ID: <93a84f6b-eb4e-4ea4-a15e-b8b1fe727bd4@hxr.us>
Date: Wed, 31 Jul 2024 16:16:06 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: kowalik@denic.de, "regext@ietf.org" <regext@ietf.org>
References: <172243217153.2152631.577325171851793888@dt-datatracker-659f84ff76-9wqgv> <f041e47b-0429-4439-9f61-d9efb3288f0b@denic.de> <8f747241-2c2a-4df2-b338-42bbdfdadf09@hxr.us> <9e2810a9-9f40-4c8b-8981-291b2094581d@denic.de> <7ab277ac-8dc2-49a0-b5fe-ac469296cb47@hxr.us> <56d2fd23-4a4a-4fc2-b18b-7bffaff49801@denic.de>
Content-Language: en-US
From: "Andrew Newton (andy)" <andy@hxr.us>
In-Reply-To: <56d2fd23-4a4a-4fc2-b18b-7bffaff49801@denic.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: XVKWPO5HY7OPFXFD57ORKV4L5WT5FUZ6
X-Message-ID-Hash: XVKWPO5HY7OPFXFD57ORKV4L5WT5FUZ6
X-MailFrom: andy@hxr.us
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.9rc4
Precedence: list
Subject: [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-07.txt
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/LbiIsComm4XIAEOHPmnZYyQP0OU>
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>

On 7/31/24 15:06, kowalik@denic.de wrote:
>
> Just on this one topic.
>
> On 31.07.24 19:30, Andrew Newton (andy) wrote:
>>>> Would you be satisfied if the first recommendation was labeled with 
>>>> "This practice has been observed in use." and the other two 
>>>> recommendations are labeled with "This practice has not been 
>>>> observed in use."?
>>>
>>> This is already stated with each single practice and it would be 
>>> logically inconsistent the way Section 6 is written now ("MUST 
>>> implement one of the following practices...").
>>>
>>> For me the BCP shall tell like "SHOULD implement practice 1 if 
>>> existing and operationally proved practices are preferred or MAY 
>>> consider experimenting with practice 2 or 3 in the future".
>>>
>> I don't understand this. A SHOULD and MAY means a practitioner can 
>> say they adhere to the BCP without doing anything. Also "the future" 
>> is subjective. 
>
> Yes, "the future" is subjective. That's right. However touches on one 
> important point.
>
> If the goal is to eliminate those bad existing practices in a 
> foreseeable near future, then practice 1 is the only that is 
> practicable and can be implemented by only one party - the clients. 
> This is by the way also an inconsistency in the current text - it 
> tells now that EPP MUST servers implement practices, which is not 
> right for this one. At least the description does not mention any of 
> server changes needed. For others both servers and clients must 
> implement collectively.
>
> Practice 2 has a lot of moving parts that needs to change both by 
> servers and the clients, so nothing one party can implement on the 
> spot to improve the situation in any way. It maybe recommended as a 
> target picture, but will take loads of time to implement. Is it then 
> an equal recommendation referring to the goal?
>
> Practice 3 also require both servers and clients to change, but likely 
> is easier to implement. Easier does not mean easy, as clients tend to 
> be reluctant to solutions that work only with selection of registries, 
> so servers would have to move first and allow for sacrificial.invalid 
> or alike. I'm not an expert in ICANN policies, but maybe it's even 
> needed to change those. Also quite broad tests are likely required if 
> with all those conditions mentioned in 5.1.4.3 are indeed fulfilled in 
> the wild.
>
> So I don't feel right to put an equal mark within Best Current 
> Practice document for those three. Whatever "current" means.
>
> Kind Regards,
>
> Pawel Kowalik
>

Pawel,

The issues you have raised about changes necessary for either or both 
the EPP client and EPP server appear to me to go beyond normative 
language. Given this type of language  is not in any version of the 
draft, does this mean you are not supportive of this document regardless 
of the -05 or -07 version?

-andy