[TLS] FW: New Version Notification for draft-mattsson-tls-super-jumbo-record-limit-04.txt

[John Mattsson <[e-mail]>]

Hi,

We submitted a new version based on the comments received at IETF 119.
https://mailarchive.ietf.org/arch/msg/tls/SuKV6R_Xc7QlrHstqE-espDOWpE/
https://mailarchive.ietf.org/arch/msg/tls/_YPAmOnqSPpw9wGDNokTpY9CepQ/

The technical conclusions were that larger records than 2^16 should be supported. This means that the records will not look like TLS 1.2 records anyway and that the fixed fields opaque_type and legacy_record_version are not needed.

The new version makes these changes. The extension now works very similar to RFC 8449 but allows endpoints to negotiate a maximum inner plaintext size up to 2^32 - 256 bytes , while reducing overhead.

The current suggestion is to let the size of the length field be uint16, uint24, or uint32 depending on the negotiated maximum inner plaintext. This minimizes overhead and allows inner plaintexts up to 2^16 - 256 bytes can be supported with 3 bytes less overhead than before.

Cheers,
John

------------------------------------------------------

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.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-mattsson-tls-super-jumbo-record-limit/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-mattsson-tls-super-jumbo-record-limit-04.html
A diff from the version 02 is available at:
https://author-tools.ietf.org/iddiff?url1=draft-mattsson-tls-super-jumbo-record-limit-02&url2=draft-mattsson-tls-super-jumbo-record-limit-04&difftype=--html