Thomas Narten wrote:
This is in a lab, before deployment, before many other vendors start
writing their own code to make use of this message.
Let's be real. Anyone doing an implementation from scratch from the
specs would (with high probality) do its first test against a
well-known, readily available implementation. E.g., linux, *BSD, or
any of the available products.
They'd run the TAHI/IPv6ready Logo tests, fail miserably, and fix their
implementation.
I've been to many, many bake-offs from Connectathon to ETSI for IPv6 and
Mobile IPv6, and haven't seen any endian issues at them, so I really
don't think this is an issue either. I wouldn't be opposed to a
one-sentence RFC saying "network byte order/big endian is assumed in all
RFCs unless otherwise noted" if it will stop this thread :)
-Brian
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
