Hi, The draft "Large Record Sizes for TLS and DTLS with Reduced Overhead" is now in adoption call by the TLS WG. I suspect that many IoT people might not be aware of this draft as it has only been discussed in TLS WG and the initial discussion was not about reducing overhead.
In addition to enabling larger records, the current solution reduces the overhead of normally sized TLS 1.3 records with 3 bytes, which might be useful for IoT applications, e.g., when transporting CoAP or MQTT. https://datatracker.ietf.org/doc/draft-mattsson-tls-super-jumbo-record-limit/ https://mailarchive.ietf.org/arch/msg/tls/SzefwteGYwh1uIORWzgRqWli0RM/ The overhead (excluding ICV/tag) in bytes for TLS 1.2, TLS 1.3, and TLS 1.3 with the new extention looks as follows: ------------------------------------ TLS 1.2 13 TLS 1.3 6 TLS 1.3 Reduced 3 ------------------------------------ If you think that it a good idea, it would be good if you tell the TLS WG that you support adoption. Cheers, John
_______________________________________________ Ace mailing list -- ace@ietf.org To unsubscribe send an email to ace-le...@ietf.org