David Schinazi

@martinduke which design team are you referring to?

Yeah that chat we had was completely informal and carries no weight whatsoever :) I like @davidben's proposal of having compatible QUIC version negotiation fit into this somehow, it matches...

I like the direction you're going in @martinthomson - though I think we'll need to add one bit to the QUICv2 draft: QUICv2 implementations MUST support QUICv1 and compatible VN...

> I don't think that a MUST-level requirement is what we need. > > For MUST support QUICv1, an explanation of the consequences of not supporting it would be sufficient....

Hi folks, I work on HTTP/3 and QUIC for Chrome. I'm jumping in to answer questions about QUIC authentication. There hasn't been much discussion of "pluggable authn mechs" in the...

Hi there! Just to respond to the points about MASQUE above, I think that right now MASQUE is focusing on enabling proxying over HTTP - which makes it a good...

Envoy Mobile won't support UMA which is a Chrome-specific format. We'll plan to offer a different stats mechanism

Thanks @alyssawilk ! /assign @alyssawilk

@carloseltuerto is this issue not a duplicate of #1550 ?

I don't think "there is no way around to have them all implemented" is correct, we can return a subset of error codes right?