关于QUIC协议（RFC-9000）中mTLS支持可行性的技术问询

Hey there! Great question about QUIC and mTLS—let me break this down clearly for you.

First things first: mutual TLS (mTLS) and client-side authentication are fully supported in QUIC, as defined by RFC 9000 and the accompanying TLS 1.3 integration standards (since QUIC relies on TLS 1.3 as its default security layer).

The reason you might have missed this in your RFC 9000 deep dive is that most of the TLS-specific authentication mechanics (including mTLS) are delegated to the TLS 1.3 spec instead of being repeated in QUIC's core document. QUIC just specifies how the TLS handshake is transported over its own connection layer, but the rules for mutual authentication follow standard TLS 1.3 workflows.

To answer your core question directly: Yes, you absolutely can implement mTLS or client-secured authentication with QUIC. The process mirrors what you’d do with HTTPS over TCP:

• During the QUIC handshake, the server can request a client certificate just like in TLS 1.3 over TCP
• The client presents its certificate chain, the server validates it, and both parties establish a mutually authenticated connection

And regarding that 2018 comment you mentioned—yes, that support is definitely live now. All major QUIC implementations (including quic-go, which you referenced, plus others like nginx's QUIC module, Chromium's QUIC stack, etc.) have had fully functional mTLS capabilities for years now.

A quick practical tip: Since QUIC uses TLS 1.3, make sure your client and server are configured with TLS 1.3-compatible certificate authorities and certificate formats—this is standard for modern mTLS setups, so it shouldn’t be a major hurdle.

备注：内容来源于stack exchange，提问作者aureylz