Jim, I’ve looked at both drafts. I think they’re both well written examples of how to specify an EPP transport. The one thing I’d suggest adding to both is a section on service discovery since the specification of new transports means that a client can no longer assume that TCP is the only available transport protocol and we need to describe how these new transports can be found. I recommend that you add text that describes how to use the DNS for service discovery by publishing an appropriate SRV or SVCB record.
Scott From: Gould, James <jgould=40verisign....@dmarc.ietf.org> Sent: Tuesday, June 11, 2024 9:16 AM To: regext@ietf.org Subject: [EXTERNAL] [regext] Request for draft-loffredo-regext-epp-over-http (EoH) and draft-yao-regext-epp-quic (EoQ) Review Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, The draft-loffredo-regext-epp-over-http (EoH) and draft-yao-regext-epp-quic (EoQ) drafts were introduced at the IETF-119 REGEXT meeting. Please review the drafts and provide your feedback on the mailing list or privately. Thanks, -- JG James Gould Fellow Engineer <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 <http://secure-web.cisco.com/1QEXtxym1nDZjDz4mzyDZR8rCrjdERcoaGPSgdAk8MRnaekZDEEA5Ck72z-vMie2TUr8e7wmNMG-aLdCjwx2BWRooFxgLIF5jlj7AfDhCx9F9gEB7YeIzPy_BWBnOW2qDv_sf4kyhZZGztXzFSIAz_KSxzLYGqp3pd1l5_4TV2kXP4z2Yn7rGlRhtzQiPCGEBpyqbQv4zUtux7b1bkWBWUz0r928eL1Neh78G0QjBPGqlXLCEvz4wPcfSFJ3FphbujDi1QxJGUzdLKuEaGcX9ckMAHCIPUSt72oujxHGH-l8/http%3A%2F%2Fverisigninc.com%2F> Verisign.com
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
