Re: WGLC for draft-ietf-quic-reliable-stream-reset

[Lucas Pardue <[e-mail]>]

Closing the loop here. Thanks for all the responses.

There is a minor change to the document title to be finalized [1] but the
chairs don't believe that is a blocker to the important design aspects of
the draft. Once that issue is resolved, working group consensus will be
declared and the document Shepherd will pick things up.

We've noted the comment from David about implementations and will ensure
the Shepherd incorporates that into their writeup. In the meantime, we'd
encourage folks that haven't already to get going on implementing this
extension.

Thanks once again.

QUIC WG chairs.

[1] - https://github.com/quicwg/reliable-stream-reset/pull/67





On Tue, Feb 6, 2024 at 12:24 AM Martin Thomson <[e-mail]> wrote:

> I've reviewed this and I opened an inconsequential issue and added +1 to
> Victors regarding naming (ugh, isn't it always the same old problems...with
> better understanding comes a need to reframe how you communicate that
> understanding).
>
> On Thu, Jan 25, 2024, at 13:44, Lucas Pardue wrote:
> > Hello QUIC WG,
> >
> > This email announces the Working Group Last Call (WGLC) of the Reliable
> > QUIC Stream Resets draft [1] [2].
> >
> > At IETF 118 the sense of the room was this draft was ready. The authors
> > have been working on some final i dotting and t crossing and have
> > recently closed out all open issues on the GitHub repo [3].
> >
> > The WGLC runs for 2 weeks, finishing on February 08 Anywhere on Earth.
> > Please direct feedback as issues on GitHub [3], or in response to this
> > thread on the QUIC mailing list.
> >
> > Thanks,
> > Lucas & Matt
> > QUIC WG Chairs
> >
> > [1] -
> https://datatracker.ietf.org/doc/draft-ietf-quic-reliable-stream-reset/
> > [2] -
> https://datatracker.ietf.org/doc/draft-ietf-quic-reliable-stream-reset/05/
> > [3] - https://github.com/quicwg/reliable-stream-reset
>