Re: SCTP API section 5.2.2

From: David Lehmann <lehmann@ulticom.com>
Date: Tue Mar 01 2005 - 08:51:45 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Michael Tuexen wrote:
>> In section 5.2.2, the I-D states:
>> sinfo_ppid: 32 bits (unsigned integer)
>>
>> This value in sendmsg() is an opaque unsigned value that is passed to
>> the remote end in each user message. In recvmsg() this value is the
>> same information that was passed by the upper layer in the peer
>> application. Please note that byte order issues are NOT accounted
>> for and this information is passed opaquely by the SCTP stack from
>> one end to the other.
> ...
> The SCTP user must provide it in network byte order and receiver
> must expect it in network byte order.

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."

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."

-- 
David Lehmann
Ulticom, Inc.
http://www.ulticom.com

Received on Tue Mar 1 09:15:58 2005