Script updating gh-pages from 3b2aaf1. [ci skip]

draft-mattsson-tls-super-jumbo-record-limit.html

@@ -9,7 +9,7 @@
 <meta content="Hannes Tschofenig" name="author">
 <meta content="Michael Tüxen" name="author">
 <meta content="
-       TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2 14  + 1 bytes, which includes one byte for the content type, and have a 3-byte overhead due to the fixed fields opaque_type and legacy_record_version. This document defines a TLS extension that allows endpoints to negotiate a larger maximum inner plaintext size, up to 2 32  - 256 bytes, while reducing overhead. 
+       TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2 14  + 1 bytes, which includes one byte for the content type. Records also have a 3-byte overhead due to the fixed opaque_type and legacy_record_version fields. This document defines a TLS extension that allows endpoints to negotiate a larger maximum inner plaintext size, up to 2 32  - 256 bytes, while reducing overhead. 
     " name="description">
 <meta content="xml2rfc 3.23.0" name="generator">
 <meta content="next generation" name="keyword">
@@ -1071,7 +1071,7 @@
 <h1 id="title">Large Record Sizes for TLS and DTLS with Reduced Overhead</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
-<p id="section-abstract-1">TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2<sup>14</sup> + 1 bytes, which includes one byte for the content type, and have a 3-byte overhead due to the fixed fields opaque_type and legacy_record_version. This document defines a TLS extension that allows endpoints to negotiate a larger maximum inner plaintext size, up to 2<sup>32</sup> - 256 bytes, while reducing overhead.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
+<p id="section-abstract-1">TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2<sup>14</sup> + 1 bytes, which includes one byte for the content type. Records also have a 3-byte overhead due to the fixed opaque_type and legacy_record_version fields. This document defines a TLS extension that allows endpoints to negotiate a larger maximum inner plaintext size, up to 2<sup>32</sup> - 256 bytes, while reducing overhead.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
 </section>
 <section class="note rfcEditorRemove" id="section-note.1">
       <h2 id="name-about-this-document">
@@ -1181,7 +1181,7 @@ <h2 id="name-copyright-notice">
       <h2 id="name-introduction">
 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
       </h2>
-<p id="section-1-1">TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2<sup>14</sup> + 1 bytes, which includes one byte for the content type, and have a 3-byte overhead due to the fixed fields opaque_type and legacy_record_version. TLS-based protocols are increasingly used to secure long-lived interfaces in critical infrastructure, such as telecommunication networks. In some infrastructure use cases, the upper layer of DTLS expects a message oriented service and uses message sizes much larger than 2<sup>14</sup>-bytes. In these cases, the 2<sup>14</sup>-byte limit in TLS necessitates an additional protocol layer for fragmentation, resulting in increased CPU and memory consumption and additional complexity. Allowing 2<sup>32</sup>-byte records would eliminate additional fragmentation in almost all use cases. In <span>[<a href="#RFC6083" class="cite xref">RFC6083</a>]</span> (DTLS over SCTP), the 2<sup>14</sup>-byte limit is a severe restriction.<a href="#section-1-1" class="pilcrow">¶</a></p>
+<p id="section-1-1">TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to 2<sup>14</sup> + 1 bytes, which includes one byte for the content type. Records also have a 3-byte overhead due to the fixed opaque_type and legacy_record_version fields. TLS-based protocols are increasingly used to secure long-lived interfaces in critical infrastructure, such as telecommunication networks. In some infrastructure use cases, the upper layer of DTLS expects a message oriented service and uses message sizes much larger than 2<sup>14</sup>-bytes. In these cases, the 2<sup>14</sup>-byte limit in TLS necessitates an additional protocol layer for fragmentation, resulting in increased CPU and memory consumption and additional complexity. Allowing 2<sup>32</sup>-byte records would eliminate additional fragmentation in almost all use cases. In <span>[<a href="#RFC6083" class="cite xref">RFC6083</a>]</span> (DTLS over SCTP), the 2<sup>14</sup>-byte limit is a severe restriction.<a href="#section-1-1" class="pilcrow">¶</a></p>
 <p id="section-1-2">This document defines a "large_record_size_limit" extension that allows endpoints to negotiate a larger maximum inner plaintext (TLSInnerPlaintext) size. This extension is valid in TLS 1.3 and DTLS 1.3. The extension works similarly to the "record_size_limit" extension defined in <span>[<a href="#RFC8449" class="cite xref">RFC8449</a>]</span>. Additionally, this document defines new TLS 1.3 TLSLargeCiphertext and DTLS 1.3 unified_hdr structures to enable inner plaintexts up to 2<sup>32</sup> - 256 bytes with reduced overhead. For example, inner plaintexts up to 2<sup>16</sup> - 256 bytes can be supported with 3 bytes less overhead, which is useful in constrained IoT environments. The "large_record_size_limit" extension is incompatible with middleboxes expecting TLS 1.2 records.<a href="#section-1-2" class="pilcrow">¶</a></p>
 </section>
 </div>

draft-mattsson-tls-super-jumbo-record-limit.txt

@@ -17,11 +17,11 @@ Expires: 9 March 2025                                            Siemens
 Abstract
 
    TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to
-   2^14 + 1 bytes, which includes one byte for the content type, and
-   have a 3-byte overhead due to the fixed fields opaque_type and
-   legacy_record_version.  This document defines a TLS extension that
-   allows endpoints to negotiate a larger maximum inner plaintext size,
-   up to 2^32 - 256 bytes, while reducing overhead.
+   2^14 + 1 bytes, which includes one byte for the content type.
+   Records also have a 3-byte overhead due to the fixed opaque_type and
+   legacy_record_version fields.  This document defines a TLS extension
+   that allows endpoints to negotiate a larger maximum inner plaintext
+   size, up to 2^32 - 256 bytes, while reducing overhead.
 
 About This Document
 
@@ -89,11 +89,11 @@ Table of Contents
 1.  Introduction
 
    TLS 1.3 records limit the inner plaintext (TLSInnerPlaintext) size to
-   2^14 + 1 bytes, which includes one byte for the content type, and
-   have a 3-byte overhead due to the fixed fields opaque_type and
-   legacy_record_version.  TLS-based protocols are increasingly used to
-   secure long-lived interfaces in critical infrastructure, such as
-   telecommunication networks.  In some infrastructure use cases, the
+   2^14 + 1 bytes, which includes one byte for the content type.
+   Records also have a 3-byte overhead due to the fixed opaque_type and
+   legacy_record_version fields.  TLS-based protocols are increasingly
+   used to secure long-lived interfaces in critical infrastructure, such
+   as telecommunication networks.  In some infrastructure use cases, the
    upper layer of DTLS expects a message oriented service and uses
    message sizes much larger than 2^14-bytes.  In these cases, the
    2^14-byte limit in TLS necessitates an additional protocol layer for