Hi, From: Gould, James <[email protected]> Date: Tuesday, March 10, 2026 at 4:35 PM To: [email protected] <[email protected]>, [email protected] <[email protected]> Subject: [regext] Re: draft-ietf-regext-epp-https-02 early Httpdir review
... I would be cautious about using DNS as an example for "modernizing" EPP. DNS is fundamentally a stateless protocol and therefore maps much more naturally onto HTTP-based transports. JG-DoH was brought up since it matches the intent in defining an HTTP transport for an existing application protocol. DoH requires the server to support both the GET and POST HTTP methods for passing the encoded DNS query packets and returning the DNS query responses. HTTP is used as a pure transport with DoH and with EoH. MW: yes, but the upper layer protocol (DNS) is a fundamentally different protocol, and due to its stateless nature more suitable for running over HTTP, you cannot use DoH as argument for EoH. JG2-DoH was simply brought up to point to another example of an existing application protocol that has defined an HTTP transport, which is not REST and is out-of-scope for BCP 56. [JS] That would be unfair to DoH. :) AFAICT, DoH took every care to be BCP 56 compliant. Jasdip
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
