Standardized format seed
Opened this issue · 0 comments
GoogleCodeExporter commented
In all of the cases, there is no standard written to follow for hashing (that
is clear to me anyways)
Example for mac address:
I can hash the actual bytes, hex codes in ascii Upper, or ascii lower, hex
codes in ascii with "-" or ":" separators; it all depends on how I receive the
mac address.
If there were a prescribed standard, it would prevent different implementations
from generating different hashes for the same ID.
"Mac address must be the raw bytes" or "Mac address must be the lower case
ascii hex codes without a separator". That keeps people like me from messing
it up.
The same goes for the other identifiers, although there is a standard API call,
it would be nice to have a standard format to ensure we are making a standard
ODIN hash.
Original issue reported on code.google.com by syna...@gmail.com on 2 Apr 2012 at 2:46