[regext] Re: RESTful EPP draft next session how to move forward
"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 23 July 2024 17:41 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 A634DC1522A0 for <regext@ietfa.amsl.com>; Tue, 23 Jul 2024 10:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.006
X-Spam-Level:
X-Spam-Status: No, score=-7.006 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, HTTPS_HTTP_MISMATCH=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_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 SDwaySvIalUs for <regext@ietfa.amsl.com>; Tue, 23 Jul 2024 10:41:35 -0700 (PDT)
Received: from mail5.verisign.com (mail5.verisign.com [69.58.187.31]) (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 EEC63C15155C for <regext@ietf.org>; Tue, 23 Jul 2024 10:41:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=11222; q=dns/txt; s=VRSN; t=1721756495; h=from:to:cc:date:message-id:references:in-reply-to: mime-version:subject; bh=/vrSuP7UvzCK/dNfA/CHbrwKwAknF2O+ErP8O9f7wyU=; b=ISNg0TMmuAqzeSieD9n6EMw2Z6Ou8VzZDHoZD8RnYxPhE5tR+fPyGPgH f94bYo7gLzkatUReedqgtaLpkyvaLuv2IsCIAi4Sr9Mw5VFfVpA4COfdE xkCX7wYFh6y1TH1pmpdNQYaxdZhmZH/3DlvqDge8dx9Ff43moEw0rB5XZ svQ2nc+zqiHNHoKTuxVBeJGrJaMjmhYTla8vKwrm4RZR/sCWpYLhIT/yt TK3N6EEJ9mWz0XvF13Y99QLWnxM7y2IiKB5crFA3s2L0l5DC8E2o2Oxf5 NNHHQH9AmhInMcwM2Hww9v1klahe8/fDRiF72Rmg4E+woQBdfgB/a28Ft A==;
X-CSE-ConnectionGUID: 4Q4c/qjtSmyjJgzj2WlncA==
X-CSE-MsgGUID: 7lIy2AAHTJWTyt4tEb5mgg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:n5eJeq2FRC/X3qCdIfbD5c5wkn2cJEfYwER7XKvMYLTBsI5bpzBTm GMXCmHQbvaOZGP0eIsgPI629RkEscCAyN9gGQRlqSg9HnlHl5HIVI+TRqvS04F+DeWYFR46s J9OAjXkBJppJpMJjk71atANlVEliOfVAOO6ULOZUsxIbVcMYD87jh5+kPIOjIdtgNyoayuAo tqaT/f3YTdJ4BYqdDpFg06/gEk35qiq52lD5gdWic1j5zcyqVFEVPrzGonsdxMUcqEMdsamS uDKyq2O/2+x138FFtO/n7/nRVYBS7jUMBLmoiI+t3+K20UqSoQai87XBdJEAatlo2zhc+NZk b2hgaeNpTIBZcUgrsxGCkUFTHsuVUFx0OSvzXCX6aR/xmWYKye8m60G4EseZeX08c4vaY1CG GBxxJngoXlvisrvqI9XRNWAiex/FZXge5odpkpl3DP7AuQkG6/HRa7jsIowMDcY3qiiHN70X exAVhxCXEyaJQNEPU0PTpsy2vmynX+5eDpdwL6XjfNvpTGMl0oojeOrbIu9lt+iHK25mm6Dp mXC+2n/CBwRN/SBxCCE6XOjgKnEmiaTtIc6T+TprqYz3QD7Kmo7Vxk3RAGSiNmFqHGCSs4DN 2Eepy8hov1nnKCsZpynN/Gim1aesxERS8Z4EuAm5keK0KW8ywOQD3IYQzgHd8EisM4wRml2j kSIk9WvAzhHvLicU3nb97qIo3W1Iyd9EIMZTSUeS1Ia5dTz+Nt2lQzVCNNiC+u/iZv/Azeph S6Qty54jLIW5SIW65iGEZn8q2rEjvD0osQdv207gkrNAttFWbOY
IronPort-HdrOrdr: A9a23:/RbEiaAv3NNpEavlHema55DYdb4zR+YMi2TDj3oBLSC8cqSj+/ xG785rsiMc6QxhIE3I9urhBEDtexnhHNtOkOws1NSZLXLbUQmTXeJfBOLZqlWKJ8S9zJ8+6U 4KScdD4ajLbGSS+vyV3ODXKbsdKZK8gcaVbK/lvg5QcT0=
X-Talos-CUID: 9a23:TpiQ9Goj7HG7aUG1GmQBzM/mUZwcLnaa1XXMGEqpC0RmWr/PdluW84oxxg==
X-Talos-MUID: 9a23:V23YgAsND4UZLDp+k82n2zVDJZ1ByoSSKn8xgIlap+SOaCl/NGLI
X-IronPort-AV: E=Sophos;i="6.09,231,1716249600"; d="scan'208,217";a="31900155"
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, 23 Jul 2024 13:41: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; Tue, 23 Jul 2024 13:41:32 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Maarten Wullink <maarten.wullink=40sidn.nl@dmarc.ietf.org>
Thread-Topic: [EXTERNAL] Re: RESTful EPP draft next session how to move forward
Thread-Index: AQHa3KPmpfyiK3phZEGJvmpPbBg6+LIEWOGAgAAxvoCAAAs2TA==
Date: Tue, 23 Jul 2024 17:41:32 +0000
Message-ID: <7D4DB42A-C5D9-4EAD-81B7-EFECDE906920@verisign.com>
References: <EB01BA72-6887-4485-9AAE-466FD04930A5@sidn.nl> <cf77245c1cf44460acd25f550b4323e6@verisign.com>,<42B3E6BE-1C29-48F5-B583-3AE05B9A7A95@sidn.nl>
In-Reply-To: <42B3E6BE-1C29-48F5-B583-3AE05B9A7A95@sidn.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7D4DB42AC5D94EAD81B7EFECDE906920verisigncom_"
MIME-Version: 1.0
Message-ID-Hash: NH664O5MMQL3BLO3F5OAPF7BHYRZIMN3
X-Message-ID-Hash: NH664O5MMQL3BLO3F5OAPF7BHYRZIMN3
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 draft next session how to move forward
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Mck8HN91NsjY4Lc_GrwYAOIVTo8>
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>
Thanks, that helps. For some reason the DataTracker returned no results when I searched for “restful EPP”. Scott On Jul 23, 2024, at 10:01 AM, Maarten Wullink <maarten.wullink=40sidn.nl@dmarc.ietf.org> wrote: 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. Hi Scott, Sorry i forgot to include a reference to the draft, you can find it here. https://datatracker.ietf.org/doc/draft-wullink-restful-epp/<https://secure-web.cisco.com/16xqFKzukctZDxpzu89dLLHGVTj_3_M0sI5A-XZ89nexM3cHIB-7u73qVFJ0kaBngzudSqNz4OHMVtzTURuhKJHYCzobagpr8UahThiQJzXePkvRXc1XN79EMqcSJbbH_q-nOGKKb60bFDKB86-nq6ANOle0Ht_AC3GPNRmtvw51Co0DRCBx4zDpV3603ovMWQ1tr8LPoOVbG4BcBRguuLHRraRuO66kHlSLVhxo7cCzvvrPtDU-OlUM0eL1YHohaaAUKK-WHwyCvzGWknJVR1ORrN40M1fr_yxBP47qLypNGORKvmLDCdf3WfLz89wQb/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-wullink-restful-epp%2F> - Maarten Op 23 jul 2024, om 07:03 heeft Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org> het volgende geschreven: -----Original Message----- From: Maarten Wullink <maarten.wullink=40sidn.nl@dmarc.ietf.org> Sent: Monday, July 22, 2024 9:59 PM To: Registration Protocols Extensions <regext@ietf.org> Subject: [EXTERNAL] [regext] RESTful EPP draft next session how to move forward 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. Hi All, During the next REGEXT session on Wednesday we will be asking the WG where to best continue to work on RESTful EPP (REPP). There was broad support for this work during previous sessions and on the mailing list and by other communities such as CENTR (centr.org <http://secure- web.cisco.com/1yR7AbWi_bLjoECIPto4bCW8jg5e4TpW2sOzLzzXVBZiEsJ- NZ8_czhrKU3ysMaudfEkrNP62UW_DmQQ5TCmaF3dNFkcI7JL6e6vnGY8Zjgs 3uXT3_R7nZJMCerzAR8KvZqoVH9K9PSDFsx8FElmyC41vl6hRiI4BwjCsBbxOI5 GSGNRm- 8JFVDPn82HPsKr25vRjdnzXeJlCDuIIyE5wtrJTfhqKiX711nhbtoa1fiS6mxB6TqZ 0bEkDI0GPSRSnNG9Vr2NJ0EuRtSJVQmzkQwvDBUTv- jJRupRMczoPPn4/http%3A%2F%2Fcentr.org%2F>) But, some have also expressed the opinion that REPP is not an extension nor transport protocol, but instead something new. The current draft is not fully compliant with RFC5730 ( e.g. statleless vs stateful) but does have a goal of full compatibility with the existing object mapping and extensions. [SAH] I can't find an IETF draft that describes the topic. I did find this one, though: https://sidn.github.io/ietf-epp-restful-transport/draft-epp-restful-transport.html I'd very much prefer to base our working group discussions on a published IETF draft. Please publish one, or more, as necessary. How to best fit formally fit this work into the IETF process? We see 2 options: 1) WG to adopt this work? - This is the preferred option - Is it an extension (in a wider sense)? - Work on WG re-charter in parallel (if required)? 2) Create a new WG (NEXTGEN-EPP)? - Focus on a next generation RESTful EPP? - Cleaner and no distractions by work on EPP/RDAP extensions? - But will be same people + more red tape [SAH] We really, really need to see a draft (or drafts) to have a meaningful discussion of this topic. Scott
- [regext] Re: RESTful EPP draft next session how t… Rubens Kuhl
- [regext] RESTful EPP draft next session how to mo… Maarten Wullink
- [regext] Re: RESTful EPP draft next session how t… Hollenbeck, Scott
- [regext] Re: RESTful EPP draft next session how t… Maarten Wullink
- [regext] Re: RESTful EPP draft next session how t… Hollenbeck, Scott