User-space implementation of the SCTP protocol RFC 4960
The SCTPLIB library is a prototype implementation of the Stream Control Transmission Protocol (SCTP), a message-oriented reliable transport protocol that supports multi-homing, and multiple message streams multiplexed within an SCTP connection (also named association). SCTP is described in RFC 4960. See https://www.uni-due.de/~be0001/sctplib/ for details. The API of the library is modeled after Section 10 of RFC 4960, and most parameters and functions should be self-explanatory to the user familiar with this document. In addition to these interface functions between an Upper Layer Protocol (ULP) and an SCTP instance, the library also provides a number of helper functions that can be used to manage callbacks and timers, as well as UDP sockets for simple IPC. Furthermore, SCTPLIB provides support for UDP encapsulation, making it possible to co-exist with kernel SCTP implementations.
git clone https://github.com/dreibh/sctplib.git
Leaders and contributors
|See the AUTHORS file in the distribution for a complete list||Contributor|
|Thomas Dreibholz (Dreibh)||Maintainer|
Resources and communication
|VCS Repository Webview||https://github.com/dreibh/sctplib|
|SCTP Discussions||Mailing List Info/Archive||https://lists.franken.de/lists/arc/sctp-discussion/|
|SCTP Announcement List||Mailing List Info/Archive||https://lists.franken.de/lists/arc/sctp-announce/|
|Required to use||glib 2.0.0 or later|
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.