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

draft-ietf-httpbis-rfc6265bis.html

@@ -2013,7 +2013,7 @@ <h5 id="name-the-secure-attribute">
 (where "secure" is defined by the user agent). When a cookie has the Secure
 attribute, the user agent will include the cookie in an HTTP request only if
 the request is transmitted over a secure channel (typically HTTP over Transport
-Layer Security (TLS) <span>[<a href="#RFC9110" class="cite xref">HTTP</a>]</span>).<a href="#section-4.1.2.5-1" class="pilcrow">¶</a></p>
+Layer Security (TLS <span>[<a href="#RFC8446" class="cite xref">TLS13</a>]</span>) <span>[<a href="#RFC9110" class="cite xref">HTTP</a>]</span>).<a href="#section-4.1.2.5-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="attribute-httponly">
@@ -3549,7 +3549,7 @@ <h4 id="name-retrieval-algorithm">
 <p id="section-5.8.3-2.1.2.3.2">
 NOTE: The notion of a "secure" connection is not defined by this document.
 Typically, user agents consider a connection secure if the connection makes
-use of transport-layer security, such as SSL or TLS, or if the host is
+use of transport-layer security, such as SSL or TLS <span>[<a href="#RFC8446" class="cite xref">TLS13</a>]</span>, or if the host is
 trusted. For example, most user agents consider "https" to be a scheme that
 denotes a secure protocol and "localhost" to be trusted host.<a href="#section-5.8.3-2.1.2.3.2" class="pilcrow">¶</a></p>
 </li>
@@ -3859,7 +3859,7 @@ <h3 id="name-ambient-authority">
         <h3 id="name-clear-text">
 <a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-clear-text" class="section-name selfRef">Clear Text</a>
         </h3>
-<p id="section-8.3-1">Unless sent over a secure channel (such as TLS), the information in the Cookie
+<p id="section-8.3-1">Unless sent over a secure channel (such as TLS <span>[<a href="#RFC8446" class="cite xref">TLS13</a>]</span>), the information in the Cookie
 and Set-Cookie header fields is transmitted in the clear.<a href="#section-8.3-1" class="pilcrow">¶</a></p>
 <ol start="1" type="1" class="normal type-1" id="section-8.3-2">
 <li id="section-8.3-2.1">
@@ -4444,9 +4444,13 @@ <h3 id="name-informative-references">
 <span class="refAuthor">Bishop, M., Ed.</span>, <span class="refTitle">"HTTP/3"</span>, <span class="seriesInfo">RFC 9114</span>, <span class="seriesInfo">DOI 10.17487/RFC9114</span>, <time datetime="2022-06" class="refDate">June 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc9114">https://www.rfc-editor.org/rfc/rfc9114</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="SERVICE-WORKERS">[SERVICE-WORKERS]</dt>
-      <dd>
+        <dd>
 <span class="refAuthor">Archibald, J.</span> and <span class="refAuthor">M. Kruisselbrink</span>, <span class="refTitle">"Service Workers"</span>, <span>n.d.</span>, <span>&lt;<a href="https://www.w3.org/TR/service-workers/">https://www.w3.org/TR/service-workers/</a>&gt;</span>. </dd>
 <dd class="break"></dd>
+<dt id="RFC8446">[TLS13]</dt>
+      <dd>
+<span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/rfc/rfc8446">https://www.rfc-editor.org/rfc/rfc8446</a>&gt;</span>. </dd>
+<dd class="break"></dd>
 </dl>
 </section>
 </div>

draft-ietf-httpbis-rfc6265bis.txt

@@ -710,8 +710,8 @@ Table of Contents
    channels (where "secure" is defined by the user agent).  When a
    cookie has the Secure attribute, the user agent will include the
    cookie in an HTTP request only if the request is transmitted over a
-   secure channel (typically HTTP over Transport Layer Security (TLS)
-   [HTTP]).
+   secure channel (typically HTTP over Transport Layer Security (TLS
+   [TLS13]) [HTTP]).
 
 4.1.2.6.  The HttpOnly Attribute
 
@@ -1938,9 +1938,10 @@ Table of Contents
           NOTE: The notion of a "secure" connection is not defined by
           this document.  Typically, user agents consider a connection
           secure if the connection makes use of transport-layer
-          security, such as SSL or TLS, or if the host is trusted.  For
-          example, most user agents consider "https" to be a scheme that
-          denotes a secure protocol and "localhost" to be trusted host.
+          security, such as SSL or TLS [TLS13], or if the host is
+          trusted.  For example, most user agents consider "https" to be
+          a scheme that denotes a secure protocol and "localhost" to be
+          trusted host.
 
        *  If the cookie's http-only-flag is true, then exclude the
           cookie if the retrieval's type is "non-HTTP".
@@ -2215,8 +2216,9 @@ Table of Contents
 
 8.3.  Clear Text
 
-   Unless sent over a secure channel (such as TLS), the information in
-   the Cookie and Set-Cookie header fields is transmitted in the clear.
+   Unless sent over a secure channel (such as TLS [TLS13]), the
+   information in the Cookie and Set-Cookie header fields is transmitted
+   in the clear.
 
    1.  All sensitive information conveyed in these header fields is
        exposed to an eavesdropper.
@@ -2724,6 +2726,10 @@ Table of Contents
               Archibald, J. and M. Kruisselbrink, "Service Workers",
               n.d., <https://www.w3.org/TR/service-workers/>.
 
+   [TLS13]    Rescorla, E., "The Transport Layer Security (TLS) Protocol
+              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
+              <https://www.rfc-editor.org/rfc/rfc8446>.
+
 Appendix A.  Changes from RFC 6265
 
    *  Adds the same-site concept and the SameSite attribute.

index.md

@@ -30,7 +30,7 @@ View [saved issues](issues.html), or the latest GitHub [issues](https://github.c
 | [The Concealed HTTP Authentication Scheme](mikewest-patch-1/draft-ietf-httpbis-unprompted-auth.html "The Concealed HTTP Authentication Scheme (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-unprompted-auth.txt "The Concealed HTTP Authentication Scheme (Text)") | same as main |
 | [Compression Dictionary Transport](mikewest-patch-1/draft-ietf-httpbis-compression-dictionary.html "Compression Dictionary Transport (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-compression-dictionary.txt "Compression Dictionary Transport (Text)") | same as main |
 | [The HTTP QUERY Method](mikewest-patch-1/draft-ietf-httpbis-safe-method-w-body.html "The HTTP QUERY Method (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-safe-method-w-body.txt "The HTTP QUERY Method (Text)") | same as main |
-| [Cookies: HTTP State Management Mechanism](mikewest-patch-1/draft-ietf-httpbis-rfc6265bis.html "Cookies: HTTP State Management Mechanism (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-rfc6265bis.txt "Cookies: HTTP State Management Mechanism (Text)") | same as main |
+| [Cookies: HTTP State Management Mechanism](mikewest-patch-1/draft-ietf-httpbis-rfc6265bis.html "Cookies: HTTP State Management Mechanism (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-rfc6265bis.txt "Cookies: HTTP State Management Mechanism (Text)") | [diff with main](https://author-tools.ietf.org/api/iddiff?url_1=https://httpwg.github.io/http-extensions/draft-ietf-httpbis-rfc6265bis.txt&url_2=https://httpwg.github.io/http-extensions/mikewest-patch-1/draft-ietf-httpbis-rfc6265bis.txt) |
 | [HTTP Server Secondary Cert Auth](mikewest-patch-1/draft-ietf-httpbis-secondary-server-certs.html "Secondary Certificate Authentication of HTTP Servers (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-secondary-server-certs.txt "Secondary Certificate Authentication of HTTP Servers (Text)") | same as main |
 | [Resumable Uploads](mikewest-patch-1/draft-ietf-httpbis-resumable-upload.html "Resumable Uploads for HTTP (HTML)") | [plain text](mikewest-patch-1/draft-ietf-httpbis-resumable-upload.txt "Resumable Uploads for HTTP (Text)") | same as main |