You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, apparently TLV stands for Type Length Value, which was not immediately obvious to me. I guess the format is a sequence of one or more {type, length, value} fields - it would be nice to specify this explicitly.
Secondly, it doesn't specify the size of the type and length fields. Since earlier text claims that the minimum tlv_payload length is two bytes, I guess that's one byte for type, one byte for length and zero bytes for value (if length == 0)? If I need to guess, it's an indication the spec lacks some clarity.
The text was updated successfully, but these errors were encountered:
First of all, apparently TLV stands for Type Length Value, which was not immediately obvious to me. I guess the format is a sequence of one or more {type, length, value} fields - it would be nice to specify this explicitly.
Secondly, it doesn't specify the size of the type and length fields. Since earlier text claims that the minimum
tlv_payload
length is two bytes, I guess that's one byte for type, one byte for length and zero bytes for value (if length == 0)? If I need to guess, it's an indication the spec lacks some clarity.The text was updated successfully, but these errors were encountered: