Jun-ichiro itojun Hagino wrote:
SCTP supports both SOCK_DGRAM, SOCK_STREAM as well as SOCK_SEQPACKET.
SOCK_STREAM sounds odd since SCTP doesn't provide a byte stream service - it
provides a service that has explicit message boundaries.
SCTP do provide three models (SOCK_xx).
draf
> > SCTP supports both SOCK_DGRAM, SOCK_STREAM as well as SOCK_SEQPACKET.
>
> SOCK_STREAM sounds odd since SCTP doesn't provide a byte stream service - it
> provides a service that has explicit message boundaries.
SCTP do provide three models (SOCK_xx).
draft-ietf-tsvwg-sctpso
> SCTP supports both SOCK_DGRAM, SOCK_STREAM as well as SOCK_SEQPACKET.
SOCK_STREAM sounds odd since SCTP doesn't provide a byte stream service - it
provides a service that has explicit message boundaries.
> DCCP should be SOCK_DGRAM only, if i understand correctly.
Also odd; you mea
On Dec 12, 2003, at 1:15 AM, Jun-ichiro itojun Hagino wrote:
now we have couple of new transport protocols coming, such as SCTP
and
DCCP. how can we support service name lookup for those? i.e.
how can we tell getnameinfo(3) to use "sctp" or "dccp" for the 2nd
argument of getservbyport(3)?
> > > now we have couple of new transport protocols coming, such as SCTP and
> > > DCCP. how can we support service name lookup for those? i.e.
> > > how can we tell getnameinfo(3) to use "sctp" or "dccp" for the 2nd
> > > argument of getservbyport(3)?
> > >
> > > my proposal:
> > >
