Damn it, wrong http On Tue, Apr 27, 2021 at 3:40 PM Martin Duke <[email protected]> wrote:
> In the quicdev slack channel today, we realized that we had a disconnect > on what ALPN to use in the interval between the QUIC RFCs publishing and > the HTTP/3 RFCs being ready (due to a MISREF with http-semantics, etc). > > It's lost in the slack archives now, but I *think* we had concluded that > once the QUIC RFCs ship the endpoints should use 0x00000001/h3, not h3-29 > or h3-32, because the chance of something in http-semantics breaking > interoperability was nil. I personally don't really care how we converge, > as long as we converge. > > To summarize the choices, in the ~months between the RFCs, are endpoints > doing a QUIC version + ALPN of > 1) 0x00000001/h3 or > 2) 0x00000001/h3-xx > > Can we come to an agreement on this point? > > Martin >
