On 2/19/26 11:32 AM, Gould, James wrote: > 3. The goal of draft-ietf-regext-epp-https is to provide a more > Cloud-friendly EPP transport, which means that Domain Name Registries (DNRs) > can be deployed in the public cloud without having to create custom EPP over > TCP (EoT) gateways. Use of the CONNECT HTTP method does not meet this goal. >
I am befuddled by the "cloud-friendly" marketing as well. There are currently several RSPs who operate EPP using cloud providers, and many cloud providers have network load balancers that do TLS termination. From what I can tell, this draft doesn't work well with cloud-based web-application firewalls as each EPP operation uses the same path (or did I miss something), requiring custom parsing of the EPP XML bodies to do any app-layer routing. Can you point to the specific technical challenge this is referencing? Mario's message seemed to indicate that the desired connection model was about using reverse proxies which can be done on-prem or in a cloud. From that, I believe the issue he is solving is the lack of graceful session closure by the server in EPP. I am only guessing, but that seems like it could be solved with a simple EPP extension. -andy, as an observer _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
