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

"kowalik@denic.de" <kowalik@denic.de> Wed, 07 August 2024 08:15 UTC

Return-Path: <kowalik@denic.de>
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 10747C14CF15 for <regext@ietfa.amsl.com>; Wed, 7 Aug 2024 01:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=denic.de
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 3GufVwGnh6rY for <regext@ietfa.amsl.com>; Wed, 7 Aug 2024 01:15:40 -0700 (PDT)
Received: from mout-b-105.mailbox.org (mout-b-105.mailbox.org [IPv6:2001:67c:2050:102:465::105]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 4D708C14F6AF for <regext@ietf.org>; Wed, 7 Aug 2024 01:15:38 -0700 (PDT)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-105.mailbox.org (Postfix) with ESMTPS id 4Wf2zm5L4bz9v6M; Wed, 7 Aug 2024 10:15:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1723018532; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ztLKIfhJneJrr99t7Y3UcvEu0Kup7bVIvngwz0g4mSA=; b=RvwkDDNjgqh7b2VTqJT5nEXNPsr9aGsJWQToh+yXUXlP1XNPDUlrI41COQtNN30ApAWaWR tK84N6+4VZVJDnV1PGqy7SYx896vgacYShF0s5pLEePBOtQcp1CL7PTVx5a7oTNE63oc/l ogXY/5P1yQK2cTlsDjdmR7Zg3dgwUblY682kFLUihjip711fhl2tOWS2MC315U7JQbraSj GSO3n62MbmmHQ+eOLksMcdHtmdWmgutgmxRwywV2LyYZoZ8p3zB3OPITCAyLo3GJot820e hjY4N9N3I236/e+OesuBnDy5ijtEJyMJeElJzlfuFHvc1AvHZaJ1CLw3QXxaSQ==
Message-ID: <ee7ae7cd-5286-44a1-874e-03195a0bc2cd@denic.de>
Date: Wed, 07 Aug 2024 10:15:28 +0200
MIME-Version: 1.0
From: "kowalik@denic.de" <kowalik@denic.de>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "andy@hxr.us" <andy@hxr.us>, "orie@transmute.industries" <orie@transmute.industries>
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> <cf2be8dcce7f45f195ae476b9581bedc@verisign.com> <CAN8C-_LTmV1AQ+Wtn1ZH8R43=+1680kD0B=Z3rD=3msC9R=YUw@mail.gmail.com> <13c2dc98-e629-4a80-8ad7-782225498aa8@hxr.us> <cbc15f6594be46ae82c4267567a15fad@verisign.com>
Content-Language: en-GB, de-DE
In-Reply-To: <cbc15f6594be46ae82c4267567a15fad@verisign.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms030900020109020307040301"
X-MBO-RS-ID: a7afe8ad4ff12799ef2
X-MBO-RS-META: fwd4o5ij3coxtpenmu1uq9oi3xhdaheq
Message-ID-Hash: CBRS43P3W22VO3YCAZRSP7JUK3VKN2DW
X-Message-ID-Hash: CBRS43P3W22VO3YCAZRSP7JUK3VKN2DW
X-MailFrom: kowalik@denic.de
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" <regext@ietf.org>
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/LDoE2QJ0GrYtHGX_t3WoQhPGGGE>
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>

Hi Scott,

 > > -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:

Apart from the feedback above I don't see my point addressed or a valid 
argument why it should not be of concern.

I take a point of Andy about having something to enforce and it could 
have been achieved without structural change to section 6. The changes 
in -07 address the need in a misleading and confusing way.

Kind Regards,

Pawel

On 06.08.24 17:51, Hollenbeck, Scott wrote:
>
> So can we make that change and consider the draft ready for AD review?
>
> Scott
>
> *From:* Andrew Newton (andy) <andy@hxr.us>
> *Sent:* Tuesday, August 6, 2024 10:50 AM
> *To:* Orie Steele <orie@transmute.industries>; Hollenbeck, Scott 
> <shollenbeck@verisign.com>
> *Cc:* kowalik@denic.de; regext@ietf.org
> *Subject:* [EXTERNAL] Re: [regext] Re: I-D Action: 
> draft-ietf-regext-epp-delete-bcp-07.txt
>
> *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.
>
> My preference is that a BCP have something to enforce, therefore I 
> like your suggested change but do think Scott's change to the server 
> language is needed.
>
> -andy
>
> On 8/1/24 13:09, Orie Steele wrote:
>
>     Hi,
>
>     I'm happy to hear from the group on this.
>
>     If the working group thinks my change request doesn't make sense
>     please let me know.
>
>     Regards,
>
>     OS, ART AD
>
>     On Thu, Aug 1, 2024 at 7:18 AM Hollenbeck, Scott
>     <shollenbeck=40verisign.com@dmarc.ietf.org> wrote:
>
>         > -----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
>         _______________________________________________
>         regext mailing list -- regext@ietf.org
>         To unsubscribe send an email to regext-leave@ietf.org
>
>
>     -- 
>
>     *ORIE STEELE *Chief Technology Officer www.transmute.industries
>     <http://secure-web.cisco.com/1toHV6cMy-GMvu17PDcSOYTNCPJkFJJPwJUmeXceX-H9CqD3HwPy0MXE-zSmUz6b0cZ9GZn8xI--ru7j4kQIZVchD9yoilCFOj9DyI1XUlFrL_haNuqJXWLjZSz8tnHkU_wLydBmWST8fsJUy8FsfY05gekwcJVzaDRyxdbhni8-9br6owRqjymS9YY3jOZAaAN7X-eWlOKmw465gacMR00f68M8PkEHwcMYjQnWOv7cRjE9KlqdGS3W8YjCfbbkpFm-1wMO30pjSQp47FUfk89OC-fqRbgKfvGBobFFmN0w/http%3A%2F%2Fwww.transmute.industries>
>
>     Image removed by sender.
>     <https://secure-web.cisco.com/1ecTkdEr3or7tmTLSl-W2-nXGyuiuDuloq43SyomRPIUsvlOqplNb_Pd_TEPxcX-i0OS1HoEGpoUDmxoaLXQAEzsfa6p-FDdtfKT8R9a1MmLWgrH3Gh_wWUMmU5I2LU16gxp8wSJrpafuVQCwqqQ6h0M-mfw04TvsvmTtNBLKgJUQ4B-dqMr9RpDIJPzp1uM84885sagd0uMRimpEpNbHR_zcRJQs0mxYmrqgs0WkS7Z91h6akf7X8CXOvYKYrcfPq8TyP_3s2wBZNsZg3Gf1cZa4jnqELBiR-e1V42PdShU/https%3A%2F%2Ftransmute.industries>
>