Hi John,
[*] By the way, why not just use “255” in the text instead of “2^8-1”? Eschew
obfuscation!
Which one of these is clearer seems like a question of taste, I should think.
It's worth noting that because the length prefix is determined by the ceiling,
arguably 2^8-1 is clearer.
I don’t follow your point, but suit yourself.
[Hannes] As mentioned by Ekr it is a matter of taste how to describe the
payloads. We follow the style used in previous TLS specifications.
In any case, for an implementer it is important to know the length of each data
item.
For example, if you have a ceiling of 2^16-1 for a data item you know that two
bytes have to be written (or parsed). Here is a copy-and-paste from the Mbed
TLS code to show an example:
*p++ = (unsigned char)( ( MBEDTLS_TLS_EXT_SERVERNAME >> 8 ) & 0xFF );
*p++ = (unsigned char)( ( MBEDTLS_TLS_EXT_SERVERNAME ) & 0xFF );
Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
