First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] PPID in sctplib dataArriveNotif


Chronological Thread 
  • From: Michael Tuexen <Michael.Tuexen AT micmac.franken.de>
  • To: Jukka Lehtniemi <jukka.lehtniemi AT hut.fi>
  • Cc: discussion AT sctp.de
  • Subject: Re: [SCTP-Discussion] PPID in sctplib dataArriveNotif
  • Date: Sat Mar 26 23:02:57 2005
  • List-id: SCTP Discussions <discussion.sctp.de>
The PPID is not touched by the sctplib as indicated by

o payload protocol-id - A 32 bit unsigned integer that is to be
passed to the peer indicating the type of payload protocol data
being transmitted. This value is passed as opaque data by SCTP.

of section 10 of RFC 2960, which was used as a guideline for the sctplib
API.

So your term 'network bytes order' does not really make sense. It is the
the order sent by the sender.

If the sender wants to encode an upper layer with a 32 byte interger
like the IANA registered PPIDs the user has to call htonl() at the
sender side and ntohl() at the receiver side.

I hope this makes it clear.

Best regards
Michael

On Mar 24, 2005, at 7:40 Uhr, Jukka Lehtniemi wrote:

Hello,

It seems payload protocol identifier parameter in dataArriveNotif ULP-callback is in network byte order. I think it should be in host byte order because it's API-level interface or at least this feature should be documented if network byte order is used.

--
Jukka Lehtniemi "Tämä on se portti, jolla miehet
+358 40 5705 041 piestään." -A.W.Yrjänä
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion




Archive powered by MHonArc 2.6.19+.

Top of page