Hi, I agree with much of the feedback provided by the OP (Mark), standardizing EPP over HTTP will force implementers to effectively hack a stateful protocol onto a stateless transport. EPP relies on persistent sessions for login, command ordering, and session lifecycle. HTTP provides none of these guarantees. Attempting to layer state on top of it will inevitably lead to (brittle) solutions that require additional mechanisms, session management, cookies, routing, etc. In order to emulate what the current EPP TCP transport already provides.
In practice, this is unlikely to result in a clean, maintainable solution. It will almost certainly spawn further WG documents to try to standardize session management, login flows, and command ordering and more potential issues, increasing the complexity and scope of EPP and the workload for this WG. For these reasons, I think the WG should carefully consider whether EPP over HTTP is a good path forward. - Maarten _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
