attachment
<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Lucas Pardue</b> <span dir="auto"><<a href="mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7@gmail.com</a>></span><br>Date: Tue, Jun 9, 2020 at 10:09 PM<br>Subject: [TLS] Fwd: Working Group Last Call: QUIC protocol drafts<br>To: HTTP Working Group <<a href="mailto:ietf-http-wg@w3.org">ietf-http-wg@w3.org</a>>, <<a href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>>, <<a href="mailto:tls@ietf.org">tls@ietf.org</a>><br>Cc: Lars Eggert <<a href="mailto:lars@eggert.org">lars@eggert.org</a>><br></div><br><br><div dir="ltr"><div>Hello folks,</div><div><br></div><div>Please see the forwarded Working Group Last Call announcement for the QUIC protocol drafts.. <br></div><div><br></div><div>The QUIC WG will only consider feedback directed towards it so please do not respond to this thread. Instead, review comments need to be opened on the GitHub repo or sent to the QUIC mailing list as described in the guidance below.<br></div><div><br></div><div>Cheers,</div><div>Lars, Lucas and Mark<br></div><div>QUIC WG Chairs<br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Lucas Pardue</b> <span dir="auto"><<a href="mailto:lucaspardue.24.7@gmail.com" target="_blank">lucaspardue.24.7@gmail.com</a>></span><br>Date: Wed, Jun 10, 2020 at 2:36 AM<br>Subject: Working Group Last Call: QUIC protocol drafts<br>To: QUIC WG <<a href="mailto:quic@ietf.org" target="_blank">quic@ietf.org</a>><br></div><br><br><div dir="ltr">Hello,<br><br>After more than three and a half years and substantial discussion, all 845 of the design issues raised against the QUIC protocol drafts have gained consensus or have a proposed resolution. In that time the protocol has been considerably transformed; it has become more secure, much more widely implemented, and has been shown to be interoperable. Both the Chairs and the Editors feel that it is ready to proceed in standardisation.<br><br>Therefore, this email announces a Working Group Last Call (WGLC) for the following QUIC documents:<br><br>* QUIC Transport<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-transport-29" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-transport-29</a><br><br>* QUIC Loss Detection and Congestion Control<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-recovery-29" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-recovery-29</a><br><br>* Using TLS to Secure QUIC<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-tls-29" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-tls-29</a><br><br>* Version-Independent Properties of QUIC<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-invariants-09" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-invariants-09</a><br><br>* HTTP/3<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-http-29" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-http-29</a><br><br>* QPACK Header Compression for HTTP/3<br> <a href="https://tools.ietf.org/html/draft-ietf-quic-qpack-16" target="_blank">https://tools.ietf.org/html/draft-ietf-quic-qpack-16</a><br><br>The WGLC will run for four weeks, ending on 8 July 2020.<br><br>As a reminder, we have been operating under the Late-Stage Process; see <a href="https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process" target="_blank">https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process</a><span></span><span></span>. In theory, this means that the contents of the drafts above already have consensus. However, the Chairs would like to actively reaffirm that consensus and start the process of wider review through a formal WGLC.<br><br>Please review the documents above and open issues for your review comments in our repository at <a href="https://github.com/quicwg/base-drafts" target="_blank">https://github.com/quicwg/base-drafts</a>. You may also send comments to <a href="mailto:quic@ietf.org" target="_blank">quic@ietf.org</a>.<br><br>Issues raised during WGLC will be handled in accordance with the Late-Stage Process defined in the Contribution Guidelines (see link above). Please note that design issues that revisit a topic where there's already declared consensus (see <a href="https://github.com/quicwg/base-drafts/issues?q=is%3Aclosed+label%3Ahas-consensus" target="_blank">https://github.com/quicwg/base-drafts/issues?q=is%3Aclosed+label%3Ahas-consensus</a>) need to provide compelling reasons to warrant reopening the discussion.<br><br>As part of this WGLC, we seek consensus on the remaining open design issue #3661 “Include epoch in the AAD or the nonce?” (<a href="https://github.com/quicwg/base-drafts/issues/3661" target="_blank">https://github.com/quicwg/base-drafts/issues/3661</a>). The proposed resolution for this issue is to close with no action, which means that the drafts above already reflect this emerging consensus.<br><br>Subject to the feedback received during this WGLC, a subsequent smaller WGLC may be run in the near future to confirm any changes to the drafts made between now and then.<br><br>The Applicability and Manageability drafts have some dependencies on the core drafts, so we'll run separate WGLCs for them.<br><br>Cheers,<br><br>Lars, Lucas and Mark<br>QUIC WG Chairs<br></div>
</div></div></div>
_______________________________________________<br>
TLS mailing list<br>
<a href="mailto:TLS@ietf.org" target="_blank">TLS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
</div></div>