Scott, What I’m thinking is that an EPP transport discovery draft would define the framework (SRV or SVCB records) and use EoT as the example that could then be used for the client to discover more about the EoT connection policies. We would need to look at what connection policies worthy of publishing for discovery by clients, which could be applicable to all or some of the EPP transports.
-- JG [cid87442*[email protected]] James Gould Fellow Engineer [email protected]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: "Hollenbeck, Scott" <[email protected]> Date: Thursday, June 13, 2024 at 4:13 PM To: James Gould <[email protected]>, "[email protected]" <[email protected]> Subject: [EXTERNAL] RE: Re: RE: 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. That’s worth discussing. We could also assume that we won’t need to do that for EoT since it can be considered the default transport. EoH and EoQ could both say something like “Look for a record for this new transport, and if you don’t find one, assume EoT”. That may be easier and it’s one less document to write. Scott From: Gould, James <[email protected]> Sent: Thursday, June 13, 2024 4:05 PM To: Hollenbeck, Scott <[email protected]>; [email protected] Subject: [EXTERNAL] Re: RE: 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. Scott, Thanks, do you believe we should define a separate EPP transport discovery draft with the use of SRV or SVCB records that would pre-define support for EoT, since it’s an existing RFC, and provide guidance for content that needs to be included in new transports draft like EoH and EoQ? We could then centralize the definition of EPP transport discovery and ensure that all the EPP transports defined now and, in the future, can be supported. -- JG [cid:[email protected]] James Gould Fellow Engineer [email protected]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://secure-web.cisco.com/1L886VSCYbumNNjWuLMPFdB3FTl2l9T0HoQG6SMXOwaYa54epf7HfxoNTATCDzT_S7-iOkoTr3Yn_EuIL3syOhRsMfg_4tcRkY4qykxPSp0pDHxgrVNlYc90BmAC8tCENBlRE_qlZ3lth9Jw3X-wK59BEczfdBjbMkGuVNNkAs7a1YL5JfrioI86Zi4Cc-ipLevB4dEKLgRy6FS9v62DeC7EpbLru0nblc6V5CHzO9uf_-lVUT6A4k9W2Qp0UWGZhaQqXZUqch7rP088jz8nzRRdOqg0zEOUkrIi7G2QSBSQ/http%3A%2F%2Fverisigninc.com%2F> From: "Hollenbeck, Scott" <[email protected]<mailto:[email protected]>> Date: Thursday, June 13, 2024 at 3:38 PM To: James Gould <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [EXTERNAL] RE: 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. 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 <[email protected]<mailto:[email protected]>> Sent: Tuesday, June 11, 2024 9:16 AM To: [email protected]<mailto:[email protected]> 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 [cid87442*[email protected]] James Gould Fellow Engineer [email protected]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://secure-web.cisco.com/1QEXtxym1nDZjDz4mzyDZR8rCrjdERcoaGPSgdAk8MRnaekZDEEA5Ck72z-vMie2TUr8e7wmNMG-aLdCjwx2BWRooFxgLIF5jlj7AfDhCx9F9gEB7YeIzPy_BWBnOW2qDv_sf4kyhZZGztXzFSIAz_KSxzLYGqp3pd1l5_4TV2kXP4z2Yn7rGlRhtzQiPCGEBpyqbQv4zUtux7b1bkWBWUz0r928eL1Neh78G0QjBPGqlXLCEvz4wPcfSFJ3FphbujDi1QxJGUzdLKuEaGcX9ckMAHCIPUSt72oujxHGH-l8/http%3A%2F%2Fverisigninc.com%2F>
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
