IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 18 June 2024 15:46 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 2F034C1CAE9D for <regext@ietfa.amsl.com>; Tue, 18 Jun 2024 08:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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 V3GmGhk4TdrX for <regext@ietfa.amsl.com>; Tue, 18 Jun 2024 08:46:26 -0700 (PDT)
Received: from mail3.verisign.com (mail3.verisign.com [72.13.63.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF4E1C1CAE9B for <regext@ietf.org>; Tue, 18 Jun 2024 08:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=3974; q=dns/txt; s=VRSN; t=1718725585; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=0IY57AbMgNU8zjfxHFD7Z5pQIXMKYe1OvATq+EsF0ew=; b=OpczNG1tmnQlYHBlSBX5zJz247PZQZDE445j1QoIavQLgDMD6T3NaEyo vzEehpMo0GYT2hgPMP7DlBubyzh9VTzkgvHMRrrB5tmXkF48oj8T13S+c YAF68hNwpzMfx1slXlzedqNK06QUXA2x+uRE5wA8gJDQHZsBpnWeQDvXc IIAlRz7B/mP86lNJW+YMY+LhT58gENPt0nVqEQFw8KFZ1GE7OLB31GYbZ 2AGHB/2rLsPhdKT1xfmpekIDV3aO6G3SXUfUY94vjyjF81qKHBzsHl1hq Vq52oY2nNR2rHl+Ca4Hwodjnjx+PlnCihj1GaNsFr4IyCYbpTX/RNIcKq g==;
X-CSE-ConnectionGUID: fK8grzr2TL6IjXBre/C/rQ==
X-CSE-MsgGUID: 4Cx3GAMiQmOajc4DMBMtFg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:8xFUuKkDQzkOP6QMA2VIKlPo5gyEJ0RdPkR7XQ2eYbSJt1+Wr1Gzt xJNWGCCPfuCajCjKI8lPY2+oUID7cLSm9RiTVc6qXwwHy4T+ZvOCOrCIxarNUt+DCFhoGFPt JxCN4aafKjYaleG+39B55C49SEUOZmgH+e6VaidfHgsGGeIcQ954Tp7gek1n4V0ttawBgKJq LvartbWULOf82cc3lk8teTb+HuDgNyo4GlE5gJnNagQ1LPjvyJ94Kw3dPnZw0TQH9E88t6SH 47r0Ly/92XFyBYhYvvNuqr7aEADXonJNgGIjHdMM4D66vSVjnVvukqTHKN0hXZ/011lrfgoo Dl+ncXYpTMSA0H5sL91vy9wSHgiYPIcqNcrFlDk2SCb5xWun3LEna0yXBluVWES0r4f7Wpmr ZT0JN2RB/wqai3fLL+TE4FRasofwMbDMqBPtWty12vlKagHQ6DpWaiNzphC5WJl7ixONa62i 8sxQwBJNSvmTi0XYBEJA5UkhKGhij/haSZe7lmSoMLb4UCKlEooj+OraYeOPIDbLSlWth/wS mbu5GT+BhUXMtaSwjmt7H+2h/TOkiW9U4UXfFG93qU22wzCmjZJYPEQfQeQsaKWo2u/Ytd4I k4fpgYLh40u2kP+G7ERWDX9+hZopCU0WN1PGuk76ymBx6zV6ECVCwAsVDNOZcw6nM47WTJs0 UWG9+4FHhRlqrvMVnSQ5u/O6CisI24QLHRHbyhCRxEDup/9upo1yBnIS76PDZKIszE8Ihmoq xjikcT0r+97YRIjv0ljwW36vg==
IronPort-HdrOrdr: A9a23:OkuJAatrtF00FcC0QapNZIrv7skDq9V00zEX/kB9WHVpm6uj5q WTdZUgpH3JYVkqOE3I9ervBEDiexzhHPdOiOEs1NyZLWrbUQWTTb1K3M/NzzrtACXi+uMY/r cIScRDIey1KVRhl8717E2bH8ZI+rO62ZHtoevF1X9iQUVRdqd6425CZzqzCEFsWwVcP5Y/Ga ed4sYvnVGdRUg=
X-Talos-CUID: 9a23:FBH5PGtPZzcukj/cJLfiQikD6IsrUS3S1mXKeXOcV0dreJePRBi7v7ldxp8=
X-Talos-MUID: 9a23:QLFuQgrHewJQVm6KSp8ez21JJJxHyoGvMUUqmJcN5+WhHwlsFTjI2Q==
X-IronPort-AV: E=Sophos;i="6.08,247,1712620800"; d="scan'208";a="34399422"
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; Tue, 18 Jun 2024 11:46:24 -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; Tue, 18 Jun 2024 11:46:24 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "kowalik@denic.de" <kowalik@denic.de>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
Thread-Index: AQHawZXpm6o1NQMoqkK/1yyAL2ged7HNqaQQ
Date: Tue, 18 Jun 2024 15:46:24 +0000
Message-ID: <8b50206930d040cca57dfeef1d0b5144@verisign.com>
References: <591E988C-2F3E-45CA-9E43-874C50CD0F5B@elistx.com> <a3b3ef1e-0fb5-44d5-bae0-1209acabfc02@denic.de>
In-Reply-To: <a3b3ef1e-0fb5-44d5-bae0-1209acabfc02@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: 6ZFAVJB54DTCLHCMOWMEBLQVXDSROGC3
X-Message-ID-Hash: 6ZFAVJB54DTCLHCMOWMEBLQVXDSROGC3
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: WGLC: draft-ietf-regext-epp-delete-bcp-03
List-Id: Registration Protocols Extensions <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/e2cSqZHLA8LL2qcf3kSWDJigiDQ>
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>

Pawel, the document already describes known practices, their issues, and those that are proposed, along with analysis of how they're thought to be better. What's missing?

Scott

> -----Original Message-----
> From: kowalik@denic.de <kowalik@denic.de>
> Sent: Tuesday, June 18, 2024 11:36 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
>
> Hi,
>
> In the course of the actual discussion on the clarity of documents we produce,
> especially related to implementation maturity of the solutions I would need to
> repeat the remark I brought up during the call for adoption [1].
>
> I think the document, being a BCP, should be very specific about which
> methods have already been field proven and which are kind of experimental
> with unknown implementation or operational impact.
>
> [1]
> https://secure-web.cisco.com/1WmRFtKB8RXzAHuXHoN-OpHA3vOlG-
> G0Gpki1ow4L_ezX0s3WaHnOjI1vjfr3mJJj49Wx2QArJxHz_7WstL3WUkGvQXd
> O_QI2Mxh_wKKA9UvoWj_UJUlybSsh9WVIQK4h2Hcc-
> LRehJ7_1E2xmP1iH5FpdEdMxrN2CGNIlFnFVDNyoiPSKZ_xANApbBjCnW1gXU
> pEpbFO4TVSXTFbYeTzWmJT3PHkqzw4dmncdVrCbGbV8b99WCfG2c-
> ahrgqfi1TBuravVfcBrC61Q9oNp2QGP5FzDQ9hbP2gAR93uA0CSo/https%3A
> %2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fregext%2FlDkYhEak6_JehglG
> -YuqxBpwgrw%2F
>
> Kind Regards,
>
> Pawel
>
> On 03.06.24 16:56, James Galvin wrote:
> > The document editors have indicated that the following document is ready
> for submission to the IESG to be considered for publication as a Best Current
> Practice:
> >
> > Best Practices for Deletion of Domain and Host Objects in the
> > Extensible Provisioning Protocol (EPP)
> > https://secure-
> web.cisco.com/1kPqjqwCJfsCxQHvBeBU74pCSqzTWdJQ6jZ6RQm7-
> >
> 2mcVf8pmghWjgEJRqVdkFppbs7M_HiHAE7CVQJzMEmDrBQgrLJGI5WUGwC
> 1rsVWeoAzVgC
> >
> MgBrz_tOOZZ_yWsmaNrvKsCiYCAcKk34iXfGeMuD9YljauXP4IJOs_ATrkUln1aa
> Ezd61l
> >
> pawefS7VAbs77M4BMKMb1NWfX_heCB1wqcD1HYXnSkD203cWebWfQKgj
> 5C8DWHYMuKHwud
> >
> dFtPJJaxGWQA_qb0xjiiL9S3sLb2CbefBMEsC2aAwis4YLx2E/https%3A%2F%2F
> datatr
> > acker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-delete-bcp%2F03%2F
> >
> > 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, 17 June 2024.
> >
> > If there are no objections the document will be submitted to the IESG.
> >
> > The Document Shepherd for this document is Andy Newton.
> >
> > Thanks,
> >
> > Antoin and Jim
> > REGEXT WG Co-Chairs
> >
> > _______________________________________________
> > regext mailing list -- regext@ietf.org To unsubscribe send an email to
> > regext-leave@ietf.org

v2.39.1 | Report a Bug | By Email | System Status