Commit aece877f authored by Ian Goldberg's avatar Ian Goldberg

Clarify fragmentation format in Protocol-v3.html

Clarify that instance tags and fragment numbers in the OTR fragment
format are allowed to have leading 0s.

Thanks to Ola Bini <obini@thoughtworks.com> for the report.

Fixes #107
Signed-off-by: 's avatarIan Goldberg <iang@cs.uwaterloo.ca>
Signed-off-by: 's avatarDavid Goulet <dgoulet@ev0ke.net>
parent aa6b7053
......@@ -1280,7 +1280,8 @@ fragmentation on outgoing messages is optional.</p>
<li>Note that k and n are unsigned short ints (2 bytes), and each has
a maximum value of 65535. Also, each piece[k] must be
non-empty.</li>
non-empty. The instance tags (if applicable) and the k and n
values may have leading zeroes.</li>
</ul>
<p>Note that fragments are not themselves messages that can be
fragmented: you can't fragment a fragment.</p></dd>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment