Guys, i’ve yet to read up on the latest version of the document (and I will do so). However, as a quick comment:
1. Establish TCP connection 2. Establish TLS session via TLS-handshake 3. Establish HTTP session via setup of the HTTP session cookie (e.g., JSESSIONID) 4. Return EPP Greeting in framed HTTP response with the session cookie (e.g., JSESSIONID) 5. Support HTTP requests in the form of framed EPP commands that are returned in HTTP responses in the form of framed EPP responses. [AM] Please please let’s not assume that HTTP is TCP. The protocol (imho MUST) also work over HTTP/3, which uses QUIC, which in turn uses UDP. However, the approach of using a session ID for identifying the equivalent of a TCP connection in “plain” EPP is still valid, and I support that design choice. More feedback to come once I manage to squeeze in time to read through the draft more carefully. Best, Alex
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
