Thanks David and Martin, your comments are now reflected in the editor's
copy. I'll cut a new draft when WGLC is over.

On Tue, May 17, 2022 at 2:31 PM David Schinazi <[email protected]>
wrote:

> I've also reviewed the document and think it is mostly ready to go. I've
> opened a few issues and PRs but they're all minor.
>
> I'll note that it makes me sad that we've designed QUICv2 in such a way
> that it can't serve its anti-ossification purpose by itself, but hopefully
> we'll figure that out later.
>
> David
>
> On Mon, May 16, 2022 at 6:37 PM Martin Thomson <[email protected]> wrote:
>
>> This is ready to go.
>>
>> I've opened a few pull requests for some extraordinary nit-picky things,
>> but I'm happy to let those go if there is any push-back.  I've implemented
>> this and the spec does a good job of mapping out the interoperability
>> requirements, including a bunch of the fiddly stuff that is not immediately
>> obvious from the outset.  It's good work.
>>
>> On Tue, May 17, 2022, at 10:08, Lucas Pardue wrote:
>> > Hello QUIC WG,
>> >
>> > This email announces the WGLC of the QUIC version 2 draft[1]. This
>> > document is tightly scoped to changing trivial details of the wire
>> > protocol to combat ossification. Having another formal QUIC version
>> > also complements the QUIC version negotiation work. There are multiple
>> > interoperating implementations of QUIC version 2.
>> >
>> > This last call will run for 2 weeks, finishing on May 30 2022 Anywhere
>> > on Earth. Please direct responses as issues on GitHub[2], or in
>> > response to this thread.
>> >
>> > Thanks,
>> > Lucas & Matt
>> > QUIC WG Chairs
>> >
>> > [1] - https://www.ietf.org/archive/id/draft-ietf-quic-v2-03.html
>> > [2] - https://github.com/quicwg/quic-v2/issues
>>
>>

Reply via email to