Currently the whitespace tag "consists of the following 16 bytes, followed by one or more sets of 8 bytes indicating the version of OTR Alice is willing to use [...]" with the bytes being hex representations of tabs and spaces in ASCII/UTF-8.
As the protocol description doesn't mention a specific text encoding for the underlying protocol, I think this should be changed to "[...] 16 characters [...]" and so on, for clarity and compatibility. The byte values would be replaced with "tabs" and "spaces" in some form, maybe mentioning the Unicode code points to keep it precise. The current draft is problematic with UTF-16 and other encodings where these characters are larger or otherwise differently encoded, in so far as a "strict" implementation would be either impossible or most likely incompatible with an encoding transition or sanity check somewhere in the network. _______________________________________________ OTR-dev mailing list OTR-dev@lists.cypherpunks.ca http://lists.cypherpunks.ca/mailman/listinfo/otr-dev