Hi Ilari, yes, I am exactly talking about these bytes that are useless to send around in some deployment environments.
I would expect to at least provide the option of not sending the data in some cases would be useful. Ciao Hannes On 03/06/2017 04:55 PM, Ilari Liusvaara wrote: > On Mon, Mar 06, 2017 at 10:11:58AM +0100, Hannes Tschofenig wrote: >> Hi all, >> >> at the Seoul IETF meeting it was mentioned that the record layer format >> may be simplified (by removing unused fields) if deployment tests real >> no problems. >> >> Sorry if I missed information about the outcome of these deployment >> tests but the current spec version still has the old record layer format. > > Yeah, I haven't seen those results either. > >> As I mentioned in previous meetings I believe that such a record layer >> simplification would be quite useful for environments where link layer >> technologies provide very small MTU sizes. > > AFAIK, one can save 3 bytes from the header for encrypted records > in TLS 1.3. Won't go well with SRTP mux tho. > > (2 octet encoding for such record headers: > > +-+---------------+ > |1|Length(15 bits)| > +-+---------------+ > > These won't overlap with other TLS 1.3 records, as all others > always have MSB of first octet clear). > > > > -Ilari >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
