Marten Seemann

Sorry for the late response! There's currently nobody working on implementing on RFC 9218, but such work would be highly appreciated! Please comment on this thread if you're interested to...

Hi Thomas, I’m not aware of any “Quic over DPDK” work in Go. How would one use DPDK in Go?

It's not that easy. The MTU on the outer connection must be large enough to hold the datagrams (plus the additional packet header and crypto overhead).

The size of the header unfortunately is not constant, it depends on the value of the packet number and on the connection ID, for example. If you want a guarantee...

@LPardue's suggestion definitely makes sense for the receive side. The complication here is that the send side is not very sophisticated: https://github.com/lucas-clemente/quic-go/blob/496fbe9fda4bb094b1cbdb162a52130b6beda6b1/session.go#L1973-L1981 By using a datagram size that's 60 bytes...

@neilalexander This issue is about the QUIC DATAGRAM frame, not the MTU size. I wouldn't be opposed to adding a config option to increase the QUIC packet size, but let's...

@ohoushar, thank you for the PR! I don't think we need to make any changes to the `quic` package. Can we just set the `AfterFunc` in the `http3` package?

Can you please remove the unneccessary commits? First of all, there's no need to modify the .gitignore. Then, please don't merge master into a feature branch. Please do a rebase...

Can you rebase now that #3233 was merged?

> The motivation for this PR is to start incrementally exposing a minimal API for packages outside of http3 to implement HTTP/3 extensions. That makes sense. It would be great...