Hi Jiankang, On 30-06-2026 8:04 PM, Jiankang Yao wrote:
### Server Requirement for Client Fall Back407 8.1. Clients Fall Back with Management of Multiple Transport 409 If the establishment of an EoQ connection fails, clients MAY attempt 410 to fall back to EPP over TCP as specified in [RFC5734], depending on 411 local deployment and security policy. It is up to clients to 412 determine the mix of transports that best meets their business needs. While it is up to the client to determine if fall back is necessary, what are the requirements on the server? If a client falls back to EoT but the server doesn't have EoT, isn't that an interoperability issue? I think this can be solved with the following addition: Servers MUST offer service over TCP (EoT [RFC5374]) for clients that fall back to TCP.Thanks for your kind suggestion. Section 8.3 has discussed " QUIC Support Announcement and Discovery”. In future, some servers may support EoQ only. How about this one: If EoQ is not offered, servers MUST offer service over TCP (EoT [RFC5734]) for clients that fall back to TCP.
I think you have answered my question that clients know this through out-of-band configuration. I wouldn't want to put a MUST support EoT if EoQ is not offered rule as that may impinge on policy, and the interoperability issue is solved with out-of-band configuration. So I think there is nothing to do here. Thanks for answering my question. -andy, ART AD _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
