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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 01 August 2024 12:17 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 08438C14F6BC for <regext@ietfa.amsl.com>; Thu, 1 Aug 2024 05:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 gkxl0U2oC8sX for <regext@ietfa.amsl.com>; Thu, 1 Aug 2024 05:17:46 -0700 (PDT)
Received: from mail2.verisign.com (mail2.verisign.com [72.13.63.31]) by ietfa.amsl.com (Postfix) with ESMTP id 08C39C14F5FE for <regext@ietf.org>; Thu, 1 Aug 2024 05:17:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=3154; q=dns/txt; s=VRSN; t=1722514666; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=zrCyMCzUGuyW78KY3WIOmYtoYPTyZHyjXT9r7ranYhs=; b=INZC07qUvANS+aIQ4nhfeZUiIj+qUFJPGIstHUkw15Obe1s0Ok6iBu9V T2y6DmSvf1rJplSOO9raIplISI+o/XyPi7DDtJsk5QovI8RTA5nHbTumn KovSMsFBPGLPvtpFeADLTZ0kM+e1LlipWajwTX4ywgZZr8Ps7PbD3PHxH 3f30o2aQyjKSYDcnfDGCdEQxHGNaAoV3izC+ORhz1KlWpRV6l9bTnmQZE OOBgMGAs+onG7pIkT/7wbZzO8KDkvT/sQVLtUzFtVIwUbs5OfKXlAGvzD Z+VppIql06D7evjhm0woiJaDKySUWbExOLG2o38Kea628Vpu9tIFmohYP A==;
X-CSE-ConnectionGUID: Y7TK6IY9TAacWuBn6cLcMA==
X-CSE-MsgGUID: MH8YFx1QScSiiH2mb0sVYg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:Im+FW6KPSMxc0+MGFE+R2ZQlxSXFcZb7ZxGr2PjKsXjdYENShDxTy WUeXDjXP66DYGqmft4nPYqw/EsCucDVn9NhGQporCE8RH908seUXt7xwmUcnc+xBpaaEB84t ZV2hv3odp1coqr0/0/1WlTZhSAhk/zOH/ykVbOs1hlZHWdMUD0mhQ9oh9k3i4tphcnRKw6Ws LsemeWGULOe82AyajN8B56r8ks14Kyi4GpA4jTSWNgQ1LPgvyhNZH4gDfzpR5fIatE8NvK3Q e/F0Ia48gvxlz8xCsmom6rMaUYDRLjfJ2Cm0hK6jID733CuDgRrukoKHKJ0hXV/0l1lrPgoo Dl5jqFcfC9yVkH6sL9ED0QHSXEW0Zpuo9crKVDn2SCa5xOeLyu0m52CBmluVWET0r4f7W2ja ZX0gd3CB/yOr7ve/V61dgVjrvV8EOq1HbJOhlhpxg7EJ/B4SrTIZoyfsLe03B9o7ixPNdzkQ ZMmTxdfNE2GfRZIIE9RAZ54gv2zgD/0dDgwRFC9/PJxujeIilUsi/6xYLI5efTTLSlRtl2Yo WbC8mLzDxoZHMKS0zue832qwOTImEsXXapJSOXoraY30TV/wEQ2KE0ne0vimMKysU+/e4haI RQPxBsh+P1aGEuDC4OVsweDiH2DoRcYWtl4H+A86QrLxqe8yw+fCnksTi5bLsE93OcsSDMnx kOhnt71C3poqrL9dJ6G3r2Oq2qtPyUFdTZHfjEeCw4E+Jzpp8c5lBSWCMh5C6jzhdrwcd3t/ w23QOEFr+17paY2O2+TpDgrXxrESkD1czMI
IronPort-HdrOrdr: A9a23:oR6vBa4RlDoljNQ++gPXwXmBI+orL9Y04lQ7vn2ZFiY5TiXIra qTdaogviMc0AxhPk3I6urwQZVoIEmsvKKdhLN8AV7MZniDhILFFuBfBOjZsnXd8k/Fh4lgPM 5bGsAQZuEYZmIK7voSlTPIdurIt+P3kpxA692/815dCSVRL41w5QZwDQiWVmdsQhNdOJY/HJ 2AouJaujuJYx0sH46GL0hAe9KGi8zAlZrgbxJDLQUg8hOygTSh76O/OwSE3y0ZTyhEzd4ZgC X4ek3Cl+meWsOAu1HhPlzontVrcRzau5t+7fm3+4cow/PX+0WVjcpaKv+/VXsO0ZmSAR4R4a LxSlEbTo9OAjrqDx2IiAqo1A/63Dk07Xj+jVeenHv4uMT8ACk3EsxbmOtiA2/kAmcbzaNBOZ hwrheknosSCQmFkDX25tDOWR0vnk2ooWA6mepWi3BES4MRZLJYsIRapSpuYeE9NTO/7JpiHP hlDcna6voTeVSGb2rBtm0qxNC3RHw8EhqPX0BHsM2I1Dpdmmx/0iIjtbsit2ZF8Ih4R4hP5u zCPKgtnLZSTtUOZaY4H+sFSdvfMB2/ffsNChPjHb3KLtB3B5uWke+J3Fwc3pDVRLUYiIYp3I nbWFlbtWk9P0LiYPf+pqFj41TdQGK+GTXkzcxa65URgMyAeIbW
X-Talos-CUID: 9a23:kfjLLWOCxVawFe5DaXZb1xA1K5EZW3TW82r6JRGzLW1MYejA
X-Talos-MUID: 9a23:WfGnig8FqM2+I29/erLZLQCQf+JIs5WAGBk0qp49usikbyl6YyyjvTviFw==
X-IronPort-AV: E=Sophos;i="6.09,254,1716249600"; d="scan'208";a="34083059"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) 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.37; Thu, 1 Aug 2024 08:17:44 -0400
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.037; Thu, 1 Aug 2024 08:17:44 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "kowalik@denic.de" <kowalik@denic.de>, "andy@hxr.us" <andy@hxr.us>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-07.txt
Thread-Index: AQHa41uLf8WqCWzwaUuFcyOJvdkJT7IRNpeAgAAMAgCAABhKAIAAGxMAgAATUwCAAAhMAIAAvfZg
Date: Thu, 01 Aug 2024 12:17:44 +0000
Message-ID: <cf2be8dcce7f45f195ae476b9581bedc@verisign.com>
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> <93a84f6b-eb4e-4ea4-a15e-b8b1fe727bd4@hxr.us> <ce6842d5-154c-4b61-81c4-ac245c80059c@denic.de>
In-Reply-To: <ce6842d5-154c-4b61-81c4-ac245c80059c@denic.de>
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: BWO5AJIPDZ7BAM6A2XNKHZHENRANKBPX
X-Message-ID-Hash: BWO5AJIPDZ7BAM6A2XNKHZHENRANKBPX
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
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/bNqpUibJuzZMB42APSv_tsnFxNo>
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: kowalik@denic.de <kowalik@denic.de>
> Sent: Wednesday, July 31, 2024 4:46 PM
> To: Andrew Newton (andy) <andy@hxr.us>; regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-
> 07.txt
> 
> Hi Andy,
> 
> On 31.07.24 22:16, Andrew Newton (andy) wrote:
> > 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
> 
> -05 and -06 were fine and I'm supportive of those. If it's SHOULD or MUST or
> we remove normative language entirely would not be substantial change
> IMHO.
> 
> -07 restructured the section 6 so that the 2 issues appeared:
> 
>      1) removed preamble and paragraphs so that current and proposed
> practices were set as equal choice to implementers

[SAH] This was done to address feedback we received from Orie after he read -06. It's based this text found in Section 5 of RC 2026:

"A BCP document is subject to the same basic set of procedures as standards track documents and thus is a vehicle by which the IETF community can define and ratify the community's best current thinking on a statement of principle or on what is believed to be the best way to perform some operations or IETF process function."

Note that it says "what is believed to be". There is no requirement for "best current practices" to be something that's being done at the moment the document is written.

>      2) added normative text which means the changes are only to be
> implemented by servers

[SAH] That's my mistake, and it's an easy fix. Change "AN EPP server MUST" to "EPP clients and servers MUST", or "must", or "can", if people have issues with a normative MUST.

As I said above, Orie requested changes to the text he saw in Section 6 of -06. We think we addressed his feedback with the change noted above, but only he can say for sure. I don't want to revert to -05 or -06 only for him to give us the same "please change this" feedback during his formal AD review.

Scott