forked from IETF-QUIC/Charter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
quic-charter.html
1 lines (1 loc) · 6.63 KB
/
quic-charter.html
1
<html><head><meta content="text/html; charset=UTF-8" http-equiv="content-type"><style type="text/css">ol{margin:0;padding:0}table td,table th{padding:0}.c5{background-color:#ffffff;max-width:468pt;padding:72pt 72pt 72pt 72pt}.c0{background-color:#ffffff;color:#222222}.c1{orphans:2;widows:2}.c3{font-size:17pt;font-weight:bold}.c4{padding-bottom:4pt}.c2{height:11pt}.title{padding-top:0pt;color:#000000;font-size:26pt;padding-bottom:3pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}.subtitle{padding-top:0pt;color:#666666;font-size:15pt;padding-bottom:16pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}li{color:#000000;font-size:11pt;font-family:"Arial"}p{margin:0;color:#000000;font-size:11pt;font-family:"Arial"}h1{padding-top:20pt;color:#000000;font-size:20pt;padding-bottom:6pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}h2{padding-top:18pt;color:#000000;font-size:16pt;padding-bottom:6pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}h3{padding-top:16pt;color:#434343;font-size:14pt;padding-bottom:4pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}h4{padding-top:14pt;color:#666666;font-size:12pt;padding-bottom:4pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}h5{padding-top:12pt;color:#666666;font-size:11pt;padding-bottom:4pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;orphans:2;widows:2;text-align:left}h6{padding-top:12pt;color:#666666;font-size:11pt;padding-bottom:4pt;font-family:"Arial";line-height:1.15;page-break-after:avoid;font-style:italic;orphans:2;widows:2;text-align:left}</style></head><body class="c5"><p class="c1 c4"><span>Name </span><span>Quick UDP-based Internet Connection</span><span> (QUIC)</span></p><p class="c1"><span>Acronym QUIC</span></p><p class="c1"><span>Area TSV</span></p><p class="c1"><span>Personnel</span></p><p class="c1"><span> Chairs TBD</span></p><p class="c1"><span> Area Director: Spencer Dawkins</span></p><p class="c1"><span> Security Area Advisor: TBD</span></p><h2 class="c1 c4" id="h.n55cjst3dlqa"><span class="c3">Charter for Working Group</span></h2><p class="c1"><span>There is emerging implementation and deployment </span><span>experience with</span><span> QUIC, a UDP-based protocol that provides a stream-multiplexing encrypted transport. Based on that implementation and deployment experience, t</span><span>he QUIC working group will provide a standards track specification generalizing the design described in the initial set of draft-tsvwg-quic-protocol</span><span class="c0">, draft-tsvwg-quic-loss-recovery, </span><span>and related documents. </span><span>Key goals for QUIC</span><span> are: minimizing connection establishment and overall transport latency for applications</span><span>, starting with HTTP/2</span><span>; providing multiplexing without head-of-line blocking; enabling deployment over unmodified Internet paths; and enabling multipath and </span><span>forward error correction</span><span> extensions.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>The work of the group will have four main focus areas, corresponding to four core deliverables. The first of these is the core transport work, which will describe the wire format, along with the mechanisms f</span><span>or</span><span> connection establishment, stream multiplexing, data reliability, loss detection and recovery, congestion control, and</span><span> negotiation</span><span>. </span><span>QUIC is expected to support rapid iterability and experimentation, and t</span><span>his work will also describe a versioning process that enables distributed experimentation with QUIC.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>The second of these focus areas is security. This work will describe how the protocol uses the facilities of TLS 1.3 for key negotiation and will also describe how those keys are used to provide confidentiality and integrity protection. </span><span>It will also provide a threat model description specific to </span><span>connection re</span><span>sumption</span><span>, along with a description for denial-of-service mitigations.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>The third focus area will describe mappings between specific applications’ semantics and the transport facilities of QUIC. The first mapping will be a description of HTTP/2 semantics using QUIC, specifically with the goal of minimizing web latency using QUIC. Upon completion of that mapping, additional protocols may be added by updating this charter to include them.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>The fourth focus area will extend core protocol facilities to enable </span><span>multipath and forward error correction</span><span> (FEC). These extensions will be separate from the core protocol and will be described in separate documents. Importantly, the FEC extension will describe QUIC protocol mechanisms required to enable negotiation and use of FEC schemes; specific FEC scheme definitions are out of scope.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span class="c0">Note that consensus is required both for changes to the current protocol mechanisms and retention of current mechanisms</span><span>. In particular, because something is in the initial document set does not imply that there is consensus around the feature or around how it is specified.</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>Milestones</span></p><p class="c1 c2"><span></span></p><p class="c1"><span>Working group adoption of Core Protocol document<br>Working group adoption of Loss detection and Congestion Control document</span></p><p class="c1"><span>Working group adoption of TLS 1.3 mapping document</span></p><p class="c1"><span>Working group adoption of HTTP/2 mapping document</span></p><p class="c1"><span>Working group adoption of Multipath extension document</span></p><p class="c1"><span>Working group adoption of FEC extension document</span></p><p class="c1"><span>Core Protocol document to IESG</span></p><p class="c1"><span>Loss detection and Congestion Control document to IESG</span></p><p class="c1"><span>TLS 1.3 Mapping document to IESG</span></p><p class="c1"><span>HTTP/2 mapping document to IESG</span></p><p class="c1"><span>Multipath extension document to IESG</span></p><p class="c1"><span>FEC extension document to IESG</span></p><p class="c1 c2"><span></span></p></body></html>