I have reviewed this document and believe it is ready to move forward. On Tue, Jan 30, 2024 at 7:14 PM David Schinazi <[email protected]> wrote:
> Hi, > > I've reviewed draft-ietf-quic-reliable-stream-reset-05 and, from a spec > perspective, I believe this is ready to move forward. However, I'm not sure > we have sufficient implementation and deployment experience. That probably > shouldn't block IESG review, but I'd suggest waiting until we have a bit > more experience before sending this from the IESG to the RFC editor's queue. > > David > > On Wed, Jan 24, 2024 at 6:45 PM Lucas Pardue <[email protected]> > 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 >> -- >> Webtransport mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/webtransport >> >
