Chronological Thread 

< Chronological >      < Thread >

---

Hi all,

We are implementing SCTP in the kernel . We are following the UDP style of
working as per the sockets draft draft-ietf-tsvwg-sctpsocket-00.txt where in
we are supposed to open the endpoint with the following call

sd = socket(AF_INET, SOCK_SEQPACKET, IPPROTO_SCTP);

But for the second parameter SOCK_SEQPACKET ,we have no equivalent Transport
Protocol which we can use in the netconfig file to configure the sctp
driver.

For example we configure TCP and UDP as :

network_id semantics flags protofamily protoname device
tcp tpi_cots_ord v inet tcp /dev/tcp
udp tpi_clts v inet udp /dev/udp
sctp ??????? v inet sctp /dev/sctp

But if we have to use the value of SOCK_SEQPACKET we cannot map it to
directly any TPI values which are allowed as current transport layer
protocols.

The values for TCP is NC_TPI_COTS and for UDP NC_TPI_CLTS which are for
connection oriented and connectionless protocol.
Since SCTP provides connection oriented services even for the UDP style of
working as it has to maintain the association until the user actually shuts
it down, it is not purely connectionless transport.
But as call set up is not done in a traditional method by the user it is not
conneciton oriented as far as the user is concerned.
So,
We would like to know if there are any new semantics for SCTP UDP style
socket which is a standard that can be used.

Thanks for your time,

Rgds,
SCTP-Team, Compaq

---

• [SCTP-Discussion] SCTP Unix UDP API question, Willette, Kevin, 06/18/2001

---

Archive powered by MHonArc 2.6.19+.