Record Header

Legacy Version

The next record-header field is a small legacy version value.

highlighted = computed this step

The next field is legacy version

The legacy version field is 0x0303 in this pinned record.

legacy version=0x0303\text{legacy version}=0x0303
Legacy versionThe record header fields are decoded from the pinned TLS toy bytes.Legacy version40 bits / 5 bytes0x1603030004byte 0byte 1byte 2byte 300010110000000110000001100000000byte 400000100content-type22legacy-version0x0303record-length4(cont.)

It is two bytes

The version field takes 2 bytes between content type and length.

version bytes=2\text{version bytes}=2
Legacy versionThe record header fields are decoded from the pinned TLS toy bytes.Legacy version40 bits / 5 bytes0x1603030004byte 0byte 1byte 2byte 300010110000000110000001100000000byte 400000100content-type22legacy-version0x0303record-length4(cont.)

It is not the length

The version field is separate from the length field that follows it.

legacy version=0x0303\text{legacy version}=0x0303
Legacy versionThe record header fields are decoded from the pinned TLS toy bytes.Legacy version40 bits / 5 bytes0x1603030004byte 0byte 1byte 2byte 300010110000000110000001100000000byte 400000100content-type22legacy-version0x0303record-length4(cont.)

Summary

The fixed record header keeps content type, legacy version, and length as separate fields.

legacy version=0x0303\text{legacy version}=0x0303
Legacy versionThe record header fields are decoded from the pinned TLS toy bytes.Legacy version40 bits / 5 bytes0x1603030004byte 0byte 1byte 2byte 300010110000000110000001100000000byte 400000100content-type22legacy-version0x0303record-length4(cont.)