Question: can long header packets be routed over a separate Conn? about quic-go HOT 2 CLOSED

Ah, my mistake - the read behavior I'm seeing is specifically:

• transport.init() calls wrapConn(), which wraps our net.PacketConn inside an *oobConn, let's say c, which implements rawConn.ReadPacket()
• transport.listen() then reads by calling c.ReadPacket()
• c.ReadPacket() calls c.batchConn.ReadBatch(...) instead of c.OOBCapablePacketConn.Read[From|MsgUDP]()

I was assuming (from comments in the code) that ReadMsgUDP would be called. Perhaps there's a less obvious code-path (e.g an implementation of net.RawConn.Read()) where this would eventually be the case, but I otherwise don't see a straightforward way to hook into the read flow at present.

from quic-go.

From a quick glance through the paper, I wish I had the authors' optimism that a censor wouldn't block migrated connections (i.e. connections for which it hasn't seen the handshake) once this solution becomes widely enough deployed.

That said, I believe the connection migration API suggested in #3990 would enable the implementation of QUICStep, if ProbePath is called right after completion of the handshake.

from quic-go.