Jeroen Massar wrote: > Nope. As far as I know of, in the case of all IETF protocols, > "Network > Byte Order" is always used, and this means Big Endian. Thus > when Little > Endian is supposed to be used, it will always have to be specified, > otherwise it is per default Big Endian.
Thanks for the replies, Jeoren and Fred. But this non-specification leaves me with a problem. Rightly or wrongly, in the past when some folk tried to create TCP or UDP messages with little endian ordering in the payload, I could steer them on the path of righteousness with a simple mention of RFC 791. Evidently, many find that Appendix B to be "draconian," but it would still usually end all discussion. Now there seems to be no guidance, even less "draconian" than RFC 791, for headers or data. I guess we'll just have to go with "Internet convention" arguments. Bert -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
