Re: SCTP API section 5.2.2

From: Kacheong Poon <kacheong.poon@sun.com>
Date: Tue Mar 01 2005 - 14:27:11 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) David Lehmann wrote:

> That was a lot of words just to state that it is in network byte
> order. For a couple fields, the draft does explicitly says that
> the values are in "network byte order."

Actually, even though the sinfo_ppid is "supposed" to be
a 32 bit integer, it is really opaque to the SCTP stack and
socket layer. So the app may as well put 4 8 bit bytes
there. Specifying any byte order in the text is probably
not correct. This also applies to the sinfo_context.

> IMHO, the draft should be explicit for all fields. Maybe for each
> structure, the draft should state something like:
> "All members of struct sctp_xxxx are in network byte order,
> except for member3 and member6, which are in host byte order."
>

-- 
						K. Poon.
						kacheong.poon@sun.com

Received on Tue Mar 1 14:38:10 2005