Marten Seemann

> That is a spec draft number and will probably go away soon, is my guess; @marten-seemann would know for sure. But I would suspect he'll eventually drop draft versions...

> @mholt My worry about disabling draft versions is compatibility with some clients that are not up-to-date; even if the non-draft HTTP/3 RFC was released months ago, I find this...

> @marten-seemann How would you feel about having quic-go set the Alt-Svc header using port information from the Host header as a hint? You can see how we do it...

> This should make it work in most cases with port forwarding automatically, no config required. We just can't assume that the socket address is the same one the client...

This issue might be worth revisiting with Go's "new" (Go 1.13) error wrapping.

@phuslu No need to close this issue.

Here's how the standard library TLS implementation handles rotation of session ticket keys: https://github.com/golang/go/blob/8696ae82c94f0a7707cbbbdf2cec44e93edf5b23/src/crypto/tls/ticket.go#L119-L185 Every key has a `ticketKeyName`, which is prepended to the ticket, and used to identify the...

I don't have the time to debug your code, but you'll need to call `Close` (or reset the stream) from both sides.

That makes sense, opening a stream doesn’t send anything on the wire. Only when you write to the stream will your peer learn that you’ve opened a stream.

Yes, you have to read the EOF, or alternatively reset the stream. If you don’t read the EOF, quic-go still has to keep the stream around, as might read from...