- From: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
- To: Rohit Sharma <rsharma AT mahindrabt.com>, discussion AT sctp.de
- Subject: Re: [SCTP-Discussion] SCTP API
- Date: Tue Oct 29 13:02:01 2002
- List-id: SCTP Discussions <discussion.sctp.de>
- Organization: University of Essen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 29 October 2002 10:02, Rohit Sharma wrote:
>
Hi
>
>
Do we have a well defined SCTP API Library. I can see a few libraries as
>
defined http://www.csm.ornl.gov/~dunigan/netperf/sctp.html (Siemens and
>
Computer Networking Group)
>
and
>
http://www.sctp.de/sctp-download.html sctp-lib
>
>
Please can anyone guide me as to what library to use.
The SCTPLIB API was modeled after section 10 of RFC 2960, to which
it adheres pretty well. At the time of creation of this library there
was no such thing as the socket api. The SCTPLIB API is described in
the (somewhat outdated !) manual that comes with the SCTPLIB
distribution.
Native OS implementations (LK-SCTP, FreeBSD-KAME) will come with
a socket interface similar to TCP (described in the document
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-05.txt)
With this, applications would ideally
continue to work with SCTP (instead of TCP) just by replacing
socketfd = socket(PF_INET, SOCK_STREAM, 0)
with
socketfd = socket(PF_INET, SOCK_SEQPACKET, IPPROTO_SCTP);
The very fine SOCKET-API library Thomas mentioned was written to
provide an API that allows applications to use functions as specified
in the socket api draft, and uses an underlying SCTPLIB implementation
or an underlying native OS implementation (whatever you have).
The cleanest solution is use of the socket api, as applications
using this API will continue to work nearly unchanged in the future.
Regards,
Andreas
- --
- ---------------------------------------------------------------------------
Dipl.-Ing. Andreas Jungmaier | Stop sending E-POSTCARDS !
Computer Networking Technology Group | Send E-MAILS -- Use PGP !
University of Essen |
http://www.exp-math.uni-essen.de/~ajung |
http://www.gnupg.org
My PGP Key-ID: D3824AC0 |
http://wwwkeys.pgp.net
- ---------------------------------------------------------------------------
My PGP Key-Fingerprint: 228C 7C2C 3381 2DD4 9998 2812 5C0B 0B04 D382 4AC0
- ---------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9vngbXAsLBNOCSsARAka3AKCmdAjKilGVWUHD1TWDjzb+9Hnx6ACfes7k
/+vA1B5gp/noyYCvkpRPT50=
=KKcv
-----END PGP SIGNATURE-----
Archive powered by MHonArc 2.6.19+.