Re: [regext] EPP evolution and the REGEXT charter

"Gould, James" <jgould@verisign.com> Fri, 22 March 2024 12:01 UTC

Return-Path: <jgould@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 CCA98C1D4CF1 for <regext@ietfa.amsl.com>; Fri, 22 Mar 2024 05:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_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 pTpOixfJRXge for <regext@ietfa.amsl.com>; Fri, 22 Mar 2024 05:01:41 -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 3599DC110D36 for <regext@ietf.org>; Fri, 22 Mar 2024 05:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=9924; q=dns/txt; s=VRSN; t=1711108901; h=from:to:cc:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=55sWdFmySlpwNJgmMQ3BaoIRrWa1FodwAqdipnJQPAM=; b=Zb/kBxMfta3hRRVZz6zUqxURwoCdyQ7wi0NE/T2AIEreOg352OvILkjn qrSWnisr8M9UFvwNOIHmEQMrIKnn5i0E1UKPv0fzy+mJQwUqsR/h7vAFn UlqBVelVx7RvxIZLwR+jTwUk5QbZ5budZNmGfU9e0ZXgBjW6SwGkRvQEg xkMYfB7mf2OQyItSV40jY7wQ7zONOP55kc6tB4R31hS/VKx1zgZXhmhax wAOt3lG7mx0eodQ8wwNCqnEANVWUtrj1jH3i25FOfxvvva9YQVE/98evG peT9P/09RGr+/1MmN+E45Atz9ACRbG/6rFiyVvMgzkFA4h3cniSvh0qo1 A==;
X-CSE-ConnectionGUID: ci6Of0DzQ62sVP5yP45ItA==
X-CSE-MsgGUID: T2fxpYgMRryv44toN68QkA==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:jsUrJqqAo8gUL+vBOg/NIzr/KFteBmI0ZBIvgKrLsJaIsI4StFCzt garIBnQaPjZMTb1KYp1bYmw9xlSvp/UnN5iHgdu/3o8QS8RoJacVYWSI3mrMnLJJKUvbq7FA +Y2MYCccZ9uHhcwgj/3b9ANeFEljfngqoLUUbOCYmYpA1Y8FE/NsDo788YhmIlknNOlNA2Ev NL2sqX3NUSss9JOGjt8B5mr9lU345wehBtC5gZiPasR5geH/5UoJMl3yZ+ZfiOQrrZ8Q7bSq 9brlNmR4m7f9hExPdKp+p6TnpoiG+O60aCm0xK6aoD66vRwjnVaPpUTbZLwXXxqZwChxLid/ v0W7MDtFl15VkH7sL91vxFwS0mSNIUYoOOXeSDXXca7lyUqeFO0qxli4d1f0ST1NY+bDEkXn cH0JgzhYTiIhryRzuqXWNAy3N8dFJT6BN9Cm21JmGSx4fYOGfgvQo3g3/kB4xEdtpgUW+jVY NABLzNjKgraeBsJMVASYH48tL7wwCCgKHsB9QnT+ftfD2v7lWSd1JDvP93IftCiW8hPn12Zq WSA9GP8av0fHIbOl2barCL37gPJtR+hVpIKJbKdzOR7ngHP2ms1Vk0vVnLu9JFVjWb7AbqzM Xc88ywivIAy5FbtU8KVdxixun+D+BobVdRKHuE9wACM1uzf5RzfB3RsZjxIc9AnrNQeTCYr0 BmPks+BLTlmuaeJRHTb6aqQqTK0OgAOLGMEIykAJSMf7tbusJ0bjx/TQJBkCqHdszHuMTvqx WmVqiUu3+9WltARkaC65hXNhHSmvJ6QCBAv/QORVWWghu9kWLOYi0WTwQCzxZ59wEyxFzFtY FBsdxCi0d0z
IronPort-HdrOrdr: A9a23:YfZ626jN+pG/GnmacnBp0Ndv23BQXgoji2hC6mlwRA09TyXBrb HLoBwavSWZtN6IMEtQ5OxoS5PwJk80kqQFnbX5XI3SJjUO11HJEGgP1+HfKnjbakjDH41mpN hdmspFeb7N5DFB5K6Q3OD7KadD/DDtys+VbJLlrkuFOjsFV0gP1WpE402gYytLrUF9dOME/N D33Ls+m9OPQwVtUviG
X-Talos-CUID: 9a23:BTK9UGpmUUrsmKk3I+YIBsnmUcskLFrTlFvCGhHiElhRFaytFQKx5Ioxxg==
X-Talos-MUID: 9a23:YTdCAArsJJT9JEkJZfQezw04Otdw0quLMlocj8lap86ia3xJOB7I2Q==
X-IronPort-AV: E=Sophos;i="6.07,145,1708387200"; d="scan'208";a="29647683"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) 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; Fri, 22 Mar 2024 08:01:39 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2507.037; Fri, 22 Mar 2024 08:01:39 -0400
From: "Gould, James" <jgould@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>, "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>
CC: "jasdips@arin.net" <jasdips@arin.net>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, "maarten.wullink@sidn.nl" <maarten.wullink@sidn.nl>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] EPP evolution and the REGEXT charter
Thread-Index: AQHae+2+iX4qqqvt8EGK1U54aTpiGbFDwXGAgAAlEAD//8MHgA==
Date: Fri, 22 Mar 2024 12:01:39 +0000
Message-ID: <A7C9335D-F0E1-4F89-8C02-3D67359297EA@verisign.com>
References: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com> <a7b73d2bb3ec49b586230d8709424170@verisign.com> <LV3PR15MB6453A840D9C678809D94BB0EC9312@LV3PR15MB6453.namprd15.prod.outlook.com> <1f54547d-8fb1-4686-8a95-e9dcbe021d55@iit.cnr.it> <CAAQiQReqVY91FF2_r=0KfWKUzc5Nt4nBRvzaZO5ZxjWp4Oux4g@mail.gmail.com>
In-Reply-To: <CAAQiQReqVY91FF2_r=0KfWKUzc5Nt4nBRvzaZO5ZxjWp4Oux4g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.82.24021116
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <427F16306286D64D9BAEBA31047308F2@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Vgk8mIVQH7quhA8wcT8yXzxtSq4>
Subject: Re: [regext] EPP evolution and the REGEXT charter
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2024 12:01:45 -0000

Andy,

It's not a question of fairness, but a question of what is defined in EPP RFC 5730 as it comes to extensibility of EPP.  EPP RFC 5730 includes extensibility of transport, as reflected in Section 2.1.  

-- 

JG 



James Gould
Fellow Engineer
jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/> 




On 3/22/24, 7:40 AM, "Andrew Newton (andy)" <andy@hxr.us <mailto:andy@hxr.us>> 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. 


I am against any logic that creates different gating factors for the
different, competing solutions. Any contortion of the concept of an
EPP "extension" that results in the favor of one set of drafts over
the other is obviously unfair.


-andy


On Fri, Mar 22, 2024 at 5:33 AM Mario Loffredo
<mario.loffredo=40iit.cnr.it@dmarc.ietf.org <mailto:40iit.cnr.it@dmarc.ietf.org>> wrote:
>
> Hi Jasdip,
>
>
> IMO, REPP is not an "EPP extension" as defined by RFC5730. It provides neither just a switch of transport (like EoH and EoQ) nor an extension to EPP comands and responses.
>
> Instead, it presents a full revision of EPP that maps some EPP features onto HTTP features.
>
> Moreover, the current proposal is incompatible with some existing or future documents including extensions to EPP query commands (see Jody's question at last meeting about REPP compatibility with the Fee Extension).
>
> On the contrary, in the spirit of achieving a full compliance with RFC5730, .it is going to update its EPP implementation that has been working since 2009.
>
>
> With regard to a possible RegExt rechartering, I also don't think we need it.
>
> RFC5730 already allows for implementing EPP over multiple transports. But it does even more, it makes some examples of possible alternatives to TCP.
>
> Therefore, leaving aside for the moment the debate about considering a new transport as an extension or not, it would be paradoxical if the protocol itself admitted other transports than TCP but it wouldn't be allowed to standardize them just like it has been done for TCP :-(
>
>
> Best,
>
> Mario
>
>
> Il 22/03/2024 01:12, Jasdip Singh ha scritto:
>
> Hi.
>
>
>
> Curious if the newly proposed “RESTful EPP” is considered a new protocol that is different from EPP, or is it an “extension” of EPP? (AFAICT, the former seems outside the current regext charter.)
>
>
>
> Thanks,
>
> Jasdip
>
>
>
> From: regext <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org>> on behalf of Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>>
> Date: Friday, March 22, 2024 at 9:56 AM
> To: jgould=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org> <jgould=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>>, maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org> <maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>>, regext@ietf.org <mailto:regext@ietf.org> <regext@ietf.org <mailto:regext@ietf.org>>
> Subject: Re: [regext] EPP evolution and the REGEXT charter
>
> From: regext <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org>> On Behalf Of Gould, James
> Sent: Thursday, March 21, 2024 7:49 PM
> To: maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>; regext@ietf.org <mailto:regext@ietf.org>
> Subject: [EXTERNAL] Re: [regext] EPP evolution and the REGEXT charter
>
>
>
> 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.
>
> Maarten,
>
>
>
> The charter refers to EPP extensions, which transports is a form of an EPP extension. RFC 5730 defines the extension points for EPP and includes support for extending the transports based on Section 2.1 “Transport Mapping Considerations”. I don’t believe that there is a need to revise the REGEXT charter to support the additional of new EPP transports.
>
> [SAH] Agreed. New transport mappings are just another type of extension as long as they preserve the data model described in RFC 5730.
>
>
>
> Scott
>
>
> _______________________________________________
> regext mailing list
> regext@ietf.org <mailto:regext@ietf.org>
> https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
>
> --
> Dott. Mario Loffredo
> Senior Technologist
> Technological Unit “Digital Innovation”
> Institute of Informatics and Telematics (IIT)
> National Research Council (CNR)
> via G. Moruzzi 1, I-56124 PISA, Italy
> Phone: +39.0503153497
> Web: http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo <http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo>
>
> _______________________________________________
> regext mailing list
> regext@ietf.org <mailto:regext@ietf.org>
> https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>