Re: [PATCH net-next v4 01/15] net: define IPPROTO_QUIC and SOL_QUIC constants
Paolo Abeni <[email protected]> Tue, 4 Nov 2025 10:20:19 +0100
| Newsgroups | dev.linux.lists.quic,dev.linux.lists.kernel-tls-handshake,org.kernel.vger.linux-cifs,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On 10/29/25 3:35 PM, Xin Long wrote: > This patch adds IPPROTO_QUIC and SOL_QUIC constants to the networking > subsystem. These definitions are essential for applications to set > socket options and protocol identifiers related to the QUIC protocol. > > QUIC does not possess a protocol number allocated from IANA, and like > IPPROTO_MPTCP, IPPROTO_QUIC is merely a value used when opening a QUIC > socket with: > > socket(AF_INET, SOCK_STREAM, IPPROTO_QUIC); > > Note we did not opt for UDP ULP for QUIC implementation due to several > considerations: > > - QUIC's connection Migration requires at least 2 UDP sockets for one > QUIC connection at the same time, not to mention the multipath > feature in one of its draft RFCs. > > - In-Kernel QUIC, as a Transport Protocol, wants to provide users with > the TCP or SCTP like Socket APIs, like connect()/listen()/accept()... > Note that a single UDP socket might even be used for multiple QUIC > connections. > > The use of IPPROTO_QUIC type sockets over UDP tunnel will effectively > address these challenges and provides a more flexible and scalable > solution. > > Signed-off-by: Xin Long <[email protected]> Acked-by: Paolo Abeni <[email protected]>