Open
Description
We have found a lack that the format of UUIDs is not defined in documentation for Native and *Binary formats.
By default it is expected that it uses normal network byte order but in fact a client has to spilt UUID in network byte order into two Uint64 words and then reverse byte order of each part.
I am not specifically writing "little endian" because the described operation works in both directions.