[regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-07.txt
"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 31 July 2024 17:38 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 5CFF3C1E7220 for <regext@ietfa.amsl.com>; Wed, 31 Jul 2024 10:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.407
X-Spam-Level:
X-Spam-Status: No, score=-4.407 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_MED=-2.3, 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=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 44c-flWCiKVq for <regext@ietfa.amsl.com>; Wed, 31 Jul 2024 10:38:53 -0700 (PDT)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) by ietfa.amsl.com (Postfix) with ESMTP id A2E17C1519BB for <regext@ietf.org>; Wed, 31 Jul 2024 10:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=4140; q=dns/txt; s=VRSN; t=1722447532; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=Is49PLOBkCEq/+FxNxDdydkRpdXeNocQwaM3wCn5uD0=; b=mJ3hOfeOB1H2ESUElfaboSUa2HhKiQKS74kQd8MXy5JyMM1qjbokZpZC MiV7CMIhasO8D7Ij31WlQFS8Yt9g6Z7uhVuTT9A8PSmjC3C3DGs8FNQLM 8o0zPv0PxdVAwnWm20oABQS8LuZvJNAF01vffDC/IsOTWOuYqGclVeqeC QS97YuFhGKiXeygpvXamD6VxKpul9c70vZiUTrUnVESRTG3c4EGM3Reyq ZtIjqVEWAwM5VWm/D6WZfIATwQMhFWLZ5jHS2/iRQ2pLjjBPTHNyA1r7n aH8gg8BfAJyN3I3gOpe07iW2OdRYMLzBhJGOduKBsKQDRkFI/8x3ZfiKi w==;
X-CSE-ConnectionGUID: D/NSny9PQ8iISh39IZf81g==
X-CSE-MsgGUID: Uv9vVf1qQGekLDPaZ55AOg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:HUGl3awSDKxy36Fryrp6t+c/xyrEfRIJ4+MujC+fZmUNrF6WrkUDn DcWD2+CMv2IZDDyeI0gO4rloU4OsceGzdQwSwZt+y00HyNBpPSeCIXCJC8cHc8wwu7rFxs7s ppEOrEsCOhuExcwcz/0auCJQUFUjPzOG/ylTraZZ0idfCc8IA85kxVvhuUltYBhhNm9Emult Mj7yyHlEAbNNwVcbCRMuspvlDs15K6u4GxD5wRiDRx2lAS2e0c9Xcp3yZ6ZciOQrrl8RoaSW +vFxbelyWLVlz9FIs+liLvybnoRSbfUOwWU4lIOM0R1qkEfzsCa+v9T2Ms0MS+7uR3Q9zxC4 IwlWaiLdOscFvakdNI1CEAETn4kbcWqz5ecSZS3mZT7I0TuLSOwk602ZK08FdVwFu1fWQmi+ RGEQdykg9/qa++emdqGpudQassLAI7NB4UO60lZnTD4NvZ9ELHxTfWT6ooNtNswrpgm8ff2T fA/MAVJQSSYOVtRMVANENQ3kKG2nGL5NTZfrTp5p4Juuy6Kk1c3ieW2doaEEjCJbZw9ckKwv WLB+2D0BBsXP9+31zef82mtiemJliT+MG4XPOboqKE12wfDroAVICAIBEWFr6Cgs2GzWPZzE 0Ump3cHiqdnoSRHSfG4BXVUukWstxgQSvJQA/d89Rrl4qnT/A+dB2ssQjNHaddguMJebSYn2 VKZg/voCCBh9rqPRhqgGqy8pym0YDcTIH9aP2ofUxFD5tj45Ys0yBjVSI8lDrSuiJv+HjSYL y22kRXSTo471aYjv5hXN3ie695wjvAlljII2zg=
IronPort-HdrOrdr: A9a23:LEuopqv3/8pUY3Qhhb5akNXy7skDq9V00zEX/kB9WHVpm6uj5q WTdZUgpH3JYVkqOE3I9ervBEDiexzhHPdOiOEs1NyZLWrbUQWTTb1K3M/NzzrtACXi+uMY/r cIScRDIey1KVRhl8717E2bH8ZI+rO62ZHtoevF1X9iQUVRdqd6425CZzqzCEFsWwVcP5Y/Ga ed4sYvnVGdRUg=
X-Talos-CUID: 9a23:s/A/TGEa8Jr7aCZ/qmJLs2gvHNF0SkSNzVbrIxTpKFRnGOSaHAo=
X-Talos-MUID: 9a23:Yo+a3g6bB4IybyA65VksCV3cxoxV/fWwNk5UiKwptsqgGRR5CWrApRO4F9o=
X-IronPort-AV: E=Sophos;i="6.09,251,1716249600"; d="scan'208";a="38677328"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.37; Wed, 31 Jul 2024 13:38:51 -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; Wed, 31 Jul 2024 13:38:51 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>, "kowalik@denic.de" <kowalik@denic.de>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-07.txt
Thread-Index: AQHa41uLf8WqCWzwaUuFcyOJvdkJT7IRNpeAgAAMAgCAABhKAP//visA
Date: Wed, 31 Jul 2024 17:38:51 +0000
Message-ID: <7d1cf1506ff24f30b6695ce8166523c2@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>
In-Reply-To: <7ab277ac-8dc2-49a0-b5fe-ac469296cb47@hxr.us>
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: KVXYRL6JV4YJWAVU7CXRUSJ2TXBBL3M3
X-Message-ID-Hash: KVXYRL6JV4YJWAVU7CXRUSJ2TXBBL3M3
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/rgn5-2bgpx0v209jydwt1WOeDDE>
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: Andrew Newton (andy) <andy@hxr.us> > Sent: Wednesday, July 31, 2024 1:30 PM > To: kowalik@denic.de; regext@ietf.org > Subject: [EXTERNAL] [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. > > Inline... > > On 7/31/24 12:03, kowalik@denic.de wrote: > > Comments inline > > > > On 31.07.24 17:20, Andrew Newton (andy) wrote: > >> [...] > >> > >> These changes are a result of the shepherd review in checking > >> normative references and normative language (see my other email, > >> which was likely sent when you sent this :) ). > > > > Yes, E-mails crossed. > > > > I am still not sure how useful it is to have normative language as > > such in BCP, especially if it's only used in the section 6, which > > refers to other sections like 5.1.4.3 which in turn does not contain > > any normative language at all. Whether it's a MUST or SHOULD is likely > > a secondary concern and here at least I would like to learn the logic > > behind the change. > > > > I think that is a fair point. Normative language pointing to procedural steps > that do not have normative language can be ambiguous. > > > >> > >> 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. > > > Repeating in this section, that people using practices highlighted as > > "This practice MUST NOT be used" shall stop and use any of above > > instead may be also an idea. > > > In other words, explicitly rule out practices instead of explicitly > allowing them. If this document is to do that, some of the document > practices would need to be updated, such as 5.1.3.2 ("renaming to > as112.arpa"), which has no prohibitive text even though the document say > the practice is detrimental. At the very least, 5.1.3.2 is a SHOULD NOT > practice if it has detriment. > > What do others think? [SAH] That I don't want to make that change. Section 5 describes the known practices, including known risks and limitations. Section 6 is intended to describe practices that we believe are best. I want to stick to that approach. Scott
- [regext] I-D Action: draft-ietf-regext-epp-delete… internet-drafts
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Hollenbeck, Scott
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Hollenbeck, Scott
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Orie Steele
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Hollenbeck, Scott
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik@denic.de
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Hollenbeck, Scott
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… kowalik@denic.de
- [regext] Re: I-D Action: draft-ietf-regext-epp-de… Andrew Newton (andy)