Re: [regext] EPP evolution and the REGEXT charter

[Maarten Wullink <[e-mail]>]

REPP is not meant to be a replacement for RFC5730. Version 01 uses a custom schema based on the RFC5730 schema, because that looked to be a cleaner way to do it. 
But we could change it so REPP uses the RFC5730 schema as in Version 00. In that case we can describe which XML elements and types are not reused by REPP.

I don’t see REPP therefore as a new protocol. it reuses almost all EPP datastructures and protocol commands. Commands are mapped to URLs and all extensions should still work  

I believe the closest match for REPP is a transport mapping. A transport mapping doest have to use a obvious transport protocol such as tcp/quic it can also be an L7 layer protocol. Section 2.1 for instance gives the SMTP protocol as an example for a possible transport mapping. 

The name “Transport mapping” might be misleading in RFC5730. 

Maarten 
> 
> [You don't often get email from [e-mail]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Andy,
> 
> I'm not comparing EoH with REPP in any way since they're not competitive.  I view the EoH and EoQ drafts as a fully complaint transports with the extensibility defined in EPP RFC 5730, and therefore they're covered by the existing REGEXT charter.  REPP is a competitive draft to EPP itself since it replaces EPP RFC 5730.  REPP may reuse some aspects of EPP, but it is a replacement protocol.  Can you find language in the REGEXT charter that supports working on a replacement protocol to EPP?
> 
> Thanks,
> 
> --
> 
> JG
> 
> 
> 
> James Gould
> Fellow Engineer
> [e-mail] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail]>
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> Verisign.com <http://verisigninc.com/>
> 
> 
> 
> 
> On 3/22/24, 9:28 AM, "Andrew Newton (andy)" <[e-mail] <mailto:[e-mail]>> 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.
> 
> 
> James,
> 
> 
> If you wish to persist this line of reasoning whereby your drafts are
> in charter but REPP is not due to an unorthodox definition of what is
> and what is not an EPP extension, be aware that there is plenty of
> text in the current RFCs that define more strictly the nature of an
> EPP extension.
> 
> 
> I also take a more inclusive view that REPP could be covered under the
> latter section of the regext charter, specifically in that it defines
> XML and/or JSON files, exchanged over HTTP, between registration
> entities that need insertion in or extraction from EPP or RDAP.
> 
> 
> -andy
> 
> 
>> On Fri, Mar 22, 2024 at 8:01 AM Gould, James <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> 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
>> [e-mail] <mailto:[e-mail]> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[e-mail] <mailto:[e-mail]>>
>> 
>> 703-948-3271
>> 12061 Bluemont Way
>> Reston, VA 20190
>> 
>> Verisign.com <http://secure-web.cisco.com/1EhcGow1atX1jq2duBAhzSxt2PHDpLVZkGSj3d6FbCQz_EkI6jfEcLHAGIwfS9-36yDWM-kXX7w3IufIkmPPMH99L9ueNM8-wGSS60JT8YxeehBi4dgNuz1ZfCCxvkv6kzU7cqkY_eKPV-J8BJX--Ov8gYOEvL0COzw9U3jOx3pxZtgH2kQEUq2DFfHjuVDiZTGNhWsZXpkWv2WwZWon9yRy5WlpfP4xICVgMy3MJ8YXQVaTNwWtruiLj_gjlj7RvnnoZ8vCS7yLz79uktZKVUbgMbCNBhPcnrDDgZq-qhDQ/http%3A%2F%2Fverisigninc.com%2F> <http://secure-web.cisco.com/1EhcGow1atX1jq2duBAhzSxt2PHDpLVZkGSj3d6FbCQz_EkI6jfEcLHAGIwfS9-36yDWM-kXX7w3IufIkmPPMH99L9ueNM8-wGSS60JT8YxeehBi4dgNuz1ZfCCxvkv6kzU7cqkY_eKPV-J8BJX--Ov8gYOEvL0COzw9U3jOx3pxZtgH2kQEUq2DFfHjuVDiZTGNhWsZXpkWv2WwZWon9yRy5WlpfP4xICVgMy3MJ8YXQVaTNwWtruiLj_gjlj7RvnnoZ8vCS7yLz79uktZKVUbgMbCNBhPcnrDDgZq-qhDQ/http%3A%2F%2Fverisigninc.com%2F&gt;>
>> 
>> 
>> 
>> 
>> On 3/22/24, 7:40 AM, "Andrew Newton (andy)" <[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>> 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=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>> 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 <[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>> on behalf of Hollenbeck, Scott <shollenbeck=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>>
>>> Date: Friday, March 22, 2024 at 9:56 AM
>>> To: jgould=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>> <jgould=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>>, maarten.wullink=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>> <maarten.wullink=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>>, [e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>> <[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>>
>>> Subject: Re: [regext] EPP evolution and the REGEXT charter
>>> 
>>> From: regext <[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>> On Behalf Of Gould, James
>>> Sent: Thursday, March 21, 2024 7:49 PM
>>> To: maarten.wullink=[e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>; [e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>
>>> 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
>>> [e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>
>>> 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> <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&gt;>
>>> 
>>> --
>>> 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: [phone]
>>> 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> <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&gt;>
>>> 
>>> _______________________________________________
>>> regext mailing list
>>> [e-mail] <mailto:[e-mail]> <mailto:[e-mail] <mailto:[e-mail]>>
>>> 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> <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&gt;>
>> 
>> 
>> 
> 
> 
>