Http/3 is great. No need for third party cookies or local storage for user tracking when the server can supply the client connection ID at the protocol level.

Http/3 is great. No need for third party cookies or local storage for user tracking when the server can supply the client connection ID at the protocol level. From https://quic.xargs.org/#server-handshake-packet/annotated https://quic.xargs.org/#server-handshake-packet/annotated "The destination connection ID is given. This field allows packets for a connection to be recognized by recipients even if the sender's network address or NAT translation has changed, making it more resilient than the underlying network connection. "