Pawel, I will mirror what I stated at the IETF 119 session, that there are economies of scale to have both EoH and EoQ progress at the same time. Based on my implementation experience with EoQ, it has security and functional advantages over EoT. Specifically, the encryption is setup ahead of time with the QUIC connection and a set of streams (EoQ connections) can be setup without the overhead of setting up the encryption via a TLS handshake, so a set of EoQ connections can be established quicker. EoQ can provide security and performance enhancements over EoT and is lower level than EoH for those registries that have the need for higher performance. All the transports (EoT, EoH, and EoQ) are pluggable, so they can be chosen based on the needs of the EPP registry and the registrars. The Verisign EPP SDK 1.17.0.2, published at https://www.verisign.com/en_US/channel-resources/domain-registry-products/epp-sdks, has an implementation of the transports if you would like to try them out.
Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 2/4/25, 3:59 AM, "kowa...@denic.de <mailto:kowa...@denic.de>" <kowa...@denic.de <mailto:kowa...@denic.de>> wrote: A clear +1 for adoption of DoH. For DoQ I share the opinions expressed in the room in IETF 119 session, that benefits from adding this transport are not clear, so I don't think we should spend cycles on this draft until this is better answered. Adding this new transport on a Standard track would mean that EPP will have two standard transports without telling why someone should decide for one instead of the other. Kind Regards, Pawel On 03.02.25 15:05, James Galvin wrote: > Continuing our potential adoption of new documents, as previously discussed > the next two documents will be taken together. The suggestion is to advance > them together, although if these are adopted the working group can choose to > advance them separately. > > This is a formal adoption request for both: > > Extensible Provisioning Protocol (EPP) Transport over QUIC > https://secure-web.cisco.com/1Xiu9Ut3Lc60FihL07sVWOQI7pG5FddLiSR0CcNGE_gi-OmKzt1eqTEywWofggN1Nbx84oVb1iMmqgKkM-GFGEqVk3i2xSP4Ot4GgNQP3tTbcVgWXPbZ0tCXNBGKBXMs0dYDUFEu0F2r7B2ydVWcdykyzinT1MFjwOT0guURBN-_vWIci3NGR0WpLgU229lojUED9pX1O00ilHGthWYiNBQIUvLKVXn459sByhVFA3H98CAy-7RFhvo46j6iIkGyQ1ObMk3k0Oy5jhbdAVMApT7CV7a39_OoZbSaSOSjJhrw/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-yao-regext-epp-quic%2F > > <https://secure-web.cisco.com/1Xiu9Ut3Lc60FihL07sVWOQI7pG5FddLiSR0CcNGE_gi-OmKzt1eqTEywWofggN1Nbx84oVb1iMmqgKkM-GFGEqVk3i2xSP4Ot4GgNQP3tTbcVgWXPbZ0tCXNBGKBXMs0dYDUFEu0F2r7B2ydVWcdykyzinT1MFjwOT0guURBN-_vWIci3NGR0WpLgU229lojUED9pX1O00ilHGthWYiNBQIUvLKVXn459sByhVFA3H98CAy-7RFhvo46j6iIkGyQ1ObMk3k0Oy5jhbdAVMApT7CV7a39_OoZbSaSOSjJhrw/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-yao-regext-epp-quic%2F> > > Extensible Provisioning Protocol (EPP) Transport over HTTPS > https://secure-web.cisco.com/1s2TIU_87gESzlNw5wocWXCPk9WE6EVTAGnVUkNen62cR8w7YKToQ1DGCLSmDJI5IcwvTHFSGIg5Qa1w0nmWKExT10TkDB3SXbEW215DFenQihE320DIqhjMWOC8g-60hJd8oWAVlAT3PjgeZwVGuCciDZiGKSNWlR0CDtwild-1c5HGQUXMs_qHSB-WuAxvUSQPNTtffh2XlOT_Yiqebo8kSJKdj-11qerKQkPLSEPqbyzLa9efes8ugJbcbx2lD5G0cLJa3e_YQa7tfisKrFaHrNSBJG6JO1bTIICamRzg/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-loffredo-regext-epp-over-http%2F > > <https://secure-web.cisco.com/1s2TIU_87gESzlNw5wocWXCPk9WE6EVTAGnVUkNen62cR8w7YKToQ1DGCLSmDJI5IcwvTHFSGIg5Qa1w0nmWKExT10TkDB3SXbEW215DFenQihE320DIqhjMWOC8g-60hJd8oWAVlAT3PjgeZwVGuCciDZiGKSNWlR0CDtwild-1c5HGQUXMs_qHSB-WuAxvUSQPNTtffh2XlOT_Yiqebo8kSJKdj-11qerKQkPLSEPqbyzLa9efes8ugJbcbx2lD5G0cLJa3e_YQa7tfisKrFaHrNSBJG6JO1bTIICamRzg/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-loffredo-regext-epp-over-http%2F> > > Please review these drafts to see if you think they are suitable for adoption > by REGEXT and reply to this message on the list, clearly stating your view. > Optionally indicate if you are willing to contribute text, review text, or be > a document shepherd. > > This Call For Adoption will close on Sunday, 16 February 2025. > > If there are no objections, the chairs will consider these documents adopted. > > Thanks, > > Your REGEXT co-chairs Antoin and Jim > > _______________________________________________ > regext mailing list -- regext@ietf.org <mailto:regext@ietf.org> > To unsubscribe send an email to regext-le...@ietf.org > <mailto:regext-le...@ietf.org> _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
