________________________________ From: Gould, James <jgould=40verisign.com@dmarc.ietf.org> > EoH uses HTTP GET to the HTTP server to establish the EPP session that returns the EPP greeting packet. EoH then goes into a command and response loop and leverages HTTP POST from the client to send the EPP command packet and to receive the EPP response packet. As I mentioned, this design seems unlikely to work well in common "cloud" CDN models, because the requests that make up one "loop" will likely be load-balanced across several EPP session servers. > The goal with EoH is to enable the 20+ year old EPP application protocol to ride on HTTP to provide for a more Cloud-friendly option for registries. It would help to have a clearer sense of what "cloud-friendly" means here. In my view, the proposed design is not "cloud-friendly", because it is likely to be broken if deployed in the most natural way using an HTTP gateway. > HTTP has been used as an EPP transport by many EPP registries, and we want to standardize it in draft-ietf-regext-epp-https. Does this draft document an existing deployed protocol, or is it proposing a new one? If the protocol is already deployed and not subject to significant revision, then the proposed status should be "Informational". If the IETF has change control, then I suspect EPP-over-WebSocket would be an easier way to pass EPP through HTTP cloud infrastructure. --Ben Schwartz
Received on Wednesday, 4 February 2026 21:18:01 UTC