IETF Logo Mail Archive

[regext] Re: RESTful EPP Charter side meeting Thursday 13:00

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 25 July 2024 02: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 1C1A0C1D8752 for <regext@ietfa.amsl.com>; Wed, 24 Jul 2024 19:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_BLOCKED=0.001, 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 cFXlbAvqwve6 for <regext@ietfa.amsl.com>; Wed, 24 Jul 2024 19:17:34 -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 0A4D9C1DA1FE for <regext@ietf.org>; Wed, 24 Jul 2024 19:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2386; q=dns/txt; s=VRSN; t=1721873854; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=goO8SMwKGcheN2ESDwCmdu04RDCb6UU/ViFiudTuXXk=; b=JNEjxnaT78aVJ4my4MGjz0GWRDvV4EGxC9TctTlUNe0gRtD/Epa4LtjN qNTFudzKh38SjCruLlCZ3Nb+3n5Gl0uxDTMBXegYvaCOU2PFsfbG97Pt+ KHsxAELhN5zbnuicA/r+eFIvr6AGyHh9JwrxKHPNC+A/9ImZPRn1M+SsB Sg8oQLQaIOQJoznvIhWoXLIyI/PXAtF6AHwX4AkeeMWQXrL7OUw58Ec4h sCXNcnIzwvNQi8D00gxtfq1/sE90wwDAN7ZEggBWO34avHN2N3jJNVFl8 HhkvaOsC1UEqvQPDyyueQHsflJ2QP2zUTITpuesOpLOAZ2+P0NVtmIL0l g==;
X-CSE-ConnectionGUID: pRPUXm0WTr2OCth6YaGCHw==
X-CSE-MsgGUID: mnSnWIpdTYOHcU58yBCnJA==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:4TZpUqgEvto8e763aEpKmxq4X161dBEKZh0ujC45NGQN5FlHY01je htvW2mOO/mMMWbyfN9yPoq3ph4A78SEytA2SgRqpXpmHi0W8JqUDtmndUqhZCn6wu8v7q5Ex 55HNoSfdpBcolv0/ErF3m3J9CEkvU2wbuOhTrOCY2YpGFIMpB4J0XpLg/Q+jpNjne+3CgaMv cKai8DEMTdJ4RYtWo4vw/zF8EIHUMja4mtC4gRhP6wT5zcyqlFOZH4hDfDpR5fHatQMdgKKb 76r5K20+Grf4yAsBruN+p7nclcHS6LlJgOHjHxbQcCK2nCucQRrj87XnNJFAatmo23hc+JZk b2hhrTpIesdBZAgrcxGO/VuO3onYfAZou+vzU+X6qR/x2WeG5fl66s2UBFuZeX08M4vaY1F3 aRwxDzg8nlvLg95qV62YrAEuygtECXkFJslgkxQyGnmMex8ZrvfQ/v77PBz/Chl06iiHd6GD yYYQRBVSk3/RTB/Yg5RFpk5hv/uj3W5bSdDrhSeoq9fD2r7lVQ3iee2doOIIZrWFa25nW7Bz o7C13/5BRUeOdqVxDGG2myhnO7UnCz9HokVEdVU89Yx3QTLnz1JUnX6U3O+p8K/tW+mV+5uD Gwfx3d+vIIZ8m6CG4yVsxqQ5STsUgQnc9VfFsUz7A6AwLDd+ECeHGdsZjxAbfQ8usRvHWd3k FSOmrvBHzFgva2JYXOQ6rnSqim9URX5NkcIfyldUg0I84G65ZotlFTKT80mGqnzhMfzQHfu2 SuM6iM5gt3/kPI26klyxnif6xrEm3QDZlddCtn/No590j5EWQ==
IronPort-HdrOrdr: A9a23:1weoFa6i2XA4Xk9d6QPXwBXXdLJyesId70hD6qkXc20xTiX4rb HNoB1173/JYVoqNk3I+uruBEDoexq1yXcf2/hzAV7NZmjbkVrtAo1k4ZDr3jHsXwbvn9Qw6Y 5QN4xzEsf5A1Q/r8rriTPTL/8QhP2K6rqhi+ub9WpqVg0CUcxdxh10ERmWCXd7QwR6BZ40fa D22vZ6
X-Talos-CUID: 9a23:K+AiFWpd+9GwXY6FvMnwwNDmUdgfSkDtyS/vH1XiLk11SOOkQHC72Lwxxg==
X-Talos-MUID: 9a23:Dx0O1Q3z6gwhQUlNVNc5uBOCYTUj5qKVDn8siZk6iu6kPhEtaya3pzKVa9py
X-IronPort-AV: E=Sophos;i="6.09,234,1716249600"; d="scan'208";a="35101922"
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; Wed, 24 Jul 2024 22:17:32 -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, 24 Jul 2024 22:17:32 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "ggm@algebras.org" <ggm@algebras.org>, "jim@rfc1035.com" <jim@rfc1035.com>
Thread-Topic: [EXTERNAL] [regext] Re: RESTful EPP Charter side meeting Thursday 13:00
Thread-Index: AQHa3hnUpWDrBIcWrkOAuKqi8xfZGLIG4sgAgAABi4CAAAcJAIAABcEA//++/UA=
Date: Thu, 25 Jul 2024 02:17:32 +0000
Message-ID: <4bc66e03d6654dd6bf903eaa59a460d3@verisign.com>
References: <603C6F0D-CED2-4624-8F2E-6A9F4BEB6083@sidn.nl> <CAN8C-_KWKxJ47CkL31UNPCgs0wqi6zce=j4aFPvDY4e4cnXn7g@mail.gmail.com> <CAKr6gn1FDy7NX37-G1xoFJJjw1GDmPFkhnZow-2PpWastEMyKg@mail.gmail.com> <BB28FA75-B408-40AF-A68B-1192C84DC98E@rfc1035.com> <CAKr6gn2bdRNJ3wTqSbQ3OqwHEF557WfOzHDhFSM+w0qNzGaFhA@mail.gmail.com>
In-Reply-To: <CAKr6gn2bdRNJ3wTqSbQ3OqwHEF557WfOzHDhFSM+w0qNzGaFhA@mail.gmail.com>
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: WZXJ3ENTEIJK6P2NTPAEOP4ZTQF5WRDQ
X-Message-ID-Hash: WZXJ3ENTEIJK6P2NTPAEOP4ZTQF5WRDQ
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
CC: "regext@ietf.org" <regext@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: RESTful EPP Charter side meeting Thursday 13:00
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/NX9IzWZeAsrpVesl7-IYpyI-fRM>
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: George Michaelson <ggm@algebras.org>
> Sent: Wednesday, July 24, 2024 9:51 PM
> To: Jim Reid <jim@rfc1035.com>
> Cc: Registration Protocols Extensions <regext@ietf.org>
> Subject: [EXTERNAL] [regext] Re: RESTful EPP Charter side meeting Thursday
> 13:00
> 
> 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.
> 
> Yea, I think we probably agree but my comment was to new WG charter not
> REGEXT re-charter. If we put EPP-on-REST to a new WG, the WG should do the
> formalism of REST and JSON (!) for it, and then walk away. Future revisions to
> functional elements? Good question.
> 
> I presume if the REST model worked, ICANN would also incur some ..
> belief it was moving contracted obligations to support it? We're not e.g. doing
> work to a dream are we? Is there a belief we can specify a protocol which
> ICANN will at some level "commit" to adopting?
> requiring? Mandating? Not things in our purview of course, but I want to
> believe the prime body here is not going to say "cute: not interested"

[SAH] This is a real risk. Hundreds of existing operators have made significant investments in developing and operating ugly old EPP, with no reason to replace those implementations just because some new transport, or data encoding scheme, or other shiny object comes along. This is an important reason to ensure that, if we decide to do anything, we MUST produce something that allows potential new operators to do their thing without mandatory impact on legacy operators. If we ever document requirements, that should be requirement number 1.

Scott

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