Script updating gh-pages from a5cd124. [ci skip]

draft-ietf-quic-http.html

@@ -373,7 +373,7 @@
 
   <meta name="dct.creator" content="Bishop, M., Ed." />
   <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-quic-http-latest" />
-  <meta name="dct.issued" scheme="ISO8601" content="2019-05-08" />
+  <meta name="dct.issued" scheme="ISO8601" content="2019-05-10" />
   <meta name="dct.abstract" content="The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment.  This document describes a mapping of HTTP semantics over QUIC.  This document also identifies HTTP/2 features that are subsumed by QUIC, and describes how HTTP/2 extensions can be ported to HTTP/3." />
   <meta name="description" content="The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment.  This document describes a mapping of HTTP semantics over QUIC.  This document also identifies HTTP/2 features that are subsumed by QUIC, and describes how HTTP/2 extensions can be ported to HTTP/3." />
 
@@ -394,10 +394,10 @@
 </tr>
 <tr>
 <td class="left">Intended status: Standards Track</td>
-<td class="right">May 08, 2019</td>
+<td class="right">May 10, 2019</td>
 </tr>
 <tr>
-<td class="left">Expires: November 9, 2019</td>
+<td class="left">Expires: November 11, 2019</td>
 <td class="right"></td>
 </tr>
 
@@ -417,7 +417,7 @@ <h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).  Note that other groups may also distribute working documents as Internet-Drafts.  The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.</p>
 <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time.  It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
-<p>This Internet-Draft will expire on November 9, 2019.</p>
+<p>This Internet-Draft will expire on November 11, 2019.</p>
 <h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
 <p>Copyright (c) 2019 IETF Trust and the persons identified as the document authors.  All rights reserved.</p>
 <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.  Please review these documents carefully, as they describe your rights and restrictions with respect to this document.  Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
@@ -1201,7 +1201,7 @@ <h2 id="rfc.section.5.3">
 <p id="rfc.section.5.3.p.3">Taken together, the dependencies across all prioritized elements in a connection form a dependency tree. An element can depend on another element or on the root of the tree. A reference to an element which is no longer in the tree is treated as a reference to the root of the tree. The structure of the dependency tree changes as PRIORITY frames modify the dependency links between prioritized elements.</p>
 <p id="rfc.section.5.3.p.4">Due to reordering between streams, an element can also be prioritized which is not yet in the tree. Such elements are added to the tree with the requested priority.</p>
 <p id="rfc.section.5.3.p.5">When a prioritized element is first created, it has a default initial weight of 16 and a default dependency. Requests and placeholders are dependent on the root of the priority tree; pushes are dependent on the client request on which the PUSH_PROMISE frame was sent.</p>
-<p id="rfc.section.5.3.p.6">Requests may override the default initial values by including a PRIORTIY frame (see <a href="#frame-priority" class="xref">Section 4.2.3</a>) at the beginning of the stream. These priorities can be updated by sending a PRIORITY frame on the control stream.</p>
+<p id="rfc.section.5.3.p.6">Requests may override the default initial values by including a PRIORITY frame (see <a href="#frame-priority" class="xref">Section 4.2.3</a>) at the beginning of the stream. These priorities can be updated by sending a PRIORITY frame on the control stream.</p>
 <h3 id="rfc.section.5.3.1">
 <a href="#rfc.section.5.3.1">5.3.1.</a> <a href="#placeholders" id="placeholders">Placeholders</a>
 </h3>