Re: Demultiplexing HTTP and DNS on the same listener [New Version Notification for draft-dkg-dprive-demux-dns-http-02]

I forgot to mention another potential challenge with the demux approach -
h2 is not client send first.. typically both sides send SETTINGS
simultaneously.. and its important to the server not to hold those back
.5RTT as it can contain a bunch of configuration information (buffer
sizing, levels of parallelism, extension negotiation, etc..) that it wants
the client to start honoring asap. (Whether this is actually simultaneous
boils down to which flavor of tls handshake is done.)