Simula Research Laboratory /
Center for Resilient Networks and Applications /
NorNet
Homepage of Thomas Dreibholz /
sctplib and socketapi Homepage
Simula Research Laboratory /
Center for Resilient Networks and Applications /
NorNet
Homepage of Thomas Dreibholz /
sctplib and socketapi Homepage
New release: socketapi-2.2.24.
New release: sctplib-1.0.31.
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 Michael Tüxen's SCTP Page 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.
socketapi is the corresponding BSD sockets API library, corresponding to RFC 6458. That is, unlike the usrsctp user-space SCTP implementation, sctplib also supports a full sockets API, including important and commonly-used functions like select() and poll(). This makes it possible to use sctplib e.g. with the following programs:
This work was partially funded by the Bundesministerium für Bildung und Forschung (BMBF) of the Federal Republic of Germany (Förderkennzeichen 01AK045). The authors alone are responsible for the results.
The complete BibTeX references in a single file can be found here!
Dreibholz, Thomas; Becke, Martin and Adhari, Hakim: ``SCTP Socket API Extensions for Concurrent Multipath Transfer´´ (TXT, 13 KiB, 🇬🇧), Internet Draft draft-dreibholz-tsvwg-sctpsocket-multipath-28, IETF, Individual Submission, March 30, 2024, [BibTeX, XML].
Previous versions: draft-dreibholz-tsvwg-sctpsocket-multipath-27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes extensions to the SCTP sockets API for configuring the CMT-SCTP and CMT/RP-SCTP extensions.
URL: https://tools.ietf.org/id/draft-dreibholz-tsvwg-sctpsocket-multipath-28.txt
MD5: 8936e1e53da47b029e996bad7e0768dc
Hohendorf, Carsten; Unurkhaan, Esbold and Dreibholz, Thomas: ``Secure SCTP´´ (TXT, 90 KiB, 🇬🇧), Internet Draft draft-hohendorf-secure-sctp-37, IETF, Individual Submission, March 30, 2024, [BibTeX, XML].
Previous versions: draft-hohendorf-secure-sctp-36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document explains the reason for the integration of security functionality into SCTP, and gives a short description of S-SCTP and its services. S-SCTP is fully compatible with SCTP defined in RFC4960, it is designed to integrate cryptographic functions into SCTP.
URL: https://tools.ietf.org/id/draft-hohendorf-secure-sctp-37.txt
MD5: 0ced3ba75597c7374d0582dfc8e40dda
Dreibholz, Thomas; Seggelmann, Robin and Becke, Martin: ``Sender Queue Info Option for the SCTP Socket API´´ (TXT, 14 KiB, 🇬🇧), Internet Draft draft-dreibholz-tsvwg-sctpsocket-sqinfo-28, IETF, Individual Submission, March 30, 2024, [BibTeX, XML].
Previous versions: draft-dreibholz-tsvwg-sctpsocket-sqinfo-27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes an extension to the SCTP sockets API for querying information about the sender queue.
URL: https://tools.ietf.org/id/draft-dreibholz-tsvwg-sctpsocket-sqinfo-28.txt
MD5: 75e72e843de0ccd2d80788ff428187ca
Tüxen, Michael and Stewart, Randall R.: ``Additional Considerations for UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets´´ (TXT, 15 KiB, 🇬🇧), Internet Draft draft-tuexen-tsvwg-sctp-udp-encaps-cons-09, IETF, Individual Submission, March 3, 2024, [BibTeX, XML].
Previous versions: draft-tuexen-tsvwg-sctp-udp-encaps-cons-08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: RFC 6951 specifies the UDP encapsulation of SCTP packets. The described handling of received packets requires the check of the verification tag. However, RFC 6951 misses a specification of the handling of received packets for which this check is not possible. This document updates RFC 6951 by specifying the handling of received packets for which the verification tag can not be checked.
URL: https://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-udp-encaps-cons-09.txt
MD5: 9746b77f1ed5457d374d872aa8cc2b71
Becke, Martin; Dreibholz, Thomas; Ekiz, Nasif; Iyengar, Janardhan R.; Natarajan, Preethi; Stewart, Randall R. and Tüxen, Michael: ``Load Sharing for the Stream Control Transmission Protocol (SCTP)´´ (TXT, 61 KiB, 🇬🇧), Internet Draft draft-tuexen-tsvwg-sctp-multipath-27, IETF, Individual Submission, March 1, 2024, [BibTeX, XML].
Previous versions: draft-tuexen-tsvwg-sctp-multipath-26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) supports multi-homing for providing network fault tolerance. However, mainly one path is used for data transmission. Only timer-based retransmissions are carried over other paths as well. This document describes how multiple paths can be used simultaneously for transmitting user messages.
URL: https://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-multipath-27.txt
MD5: 1f7b5569ca33fdac980f448c3b3df96b
Stewart, Randall R. and Tüxen, Michael: ``ECN for Stream Control Transmission Protocol (SCTP)´´ (TXT, 27 KiB, 🇬🇧), Internet Draft draft-stewart-tsvwg-sctpecn-06, IETF, Individual Submission, October 20, 2023, [BibTeX, XML].
Previous versions: draft-stewart-tsvwg-sctpecn-05, 04, 03, 02, 01, 00.
Abstract: This document describes the addition of the Explicit Congestion Notification (ECN) to the Stream Control Transmission Protocol (SCTP).
URL: https://tools.ietf.org/id/draft-stewart-tsvwg-sctpecn-06.txt
MD5: f5da3fb7cff24c33f44d6b12817bd36e
Stewart, Randall R.; Tüxen, Michael and Rüngeler, Irene: ``Stream Control Transmission Protocol (SCTP) Network Address Translation Support´´ (TXT, 108 KiB, 🇬🇧), Internet Draft draft-ietf-tsvwg-natsupp-23, IETF, October 25, 2021, [BibTeX, XML].
Previous versions: draft-stewart-natsupp-tsvwg-01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) provides a reliable communications channel between two end-hosts in many ways similar to the Transmission Control Protocol (TCP). With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT functions for TCP that allows multiple hosts to reside behind a NAT function and yet share a single IPv4 address, even when two hosts (behind a NAT function) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation (NAPT). This document describes the protocol extensions needed for the SCTP endpoints and the mechanisms for NAT functions necessary to provide similar features of NAPT in the single point and multipoint traversal scenario. Finally, a YANG module for SCTP NAT is defined.
URL: https://tools.ietf.org/id/draft-ietf-tsvwg-natsupp-23.txt
MD5: 92485035b81c664b7dd389ddbe0e85b1
Proshin, Maksim: ``Retransmit bit for SCTP DATA, I-DATA and SACK´´ (TXT, 27 KiB, 🇬🇧), Internet Draft draft-proshin-tsvwg-sctp-rtx-bit-03, IETF, Individual Submission, June 1, 2020, [BibTeX, XML].
Previous versions: draft-proshin-tsvwg-sctp-rtx-bit-02, 01, 00.
Abstract: This document defines a method which helps an SCTP sender to understand when a received SACK acknowledges the original transmission of a TSN or its retransmission. It is done by specifying a new bit, called Retransmit bit (R-bit), in the header of DATA, I-DATA and SACK chunks. The bit is used when a TSN is retransmitted and returned back in the acknowledgement. This document updates [RFC4960] if approved.
URL: https://tools.ietf.org/id/draft-proshin-tsvwg-sctp-rtx-bit-03.txt
MD5: dd68dac19392f454f65821df6782d691
Stewart, Randall R.; Tüxen, Michael and Proshin, Maksim: ``Stream Control Transmission Protocol: Errata and Issues in RFC 4960´´ (TXT, 163 KiB, 🇬🇧), Informational RFC 8540, IETF, DOI 10.17487/RFC8540, ISSN 2070-1721, February 2019, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-rfc4960-errata-08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-tsvwg-rfc4960-errata-04, 03, 02, 01, 00.
Abstract: This document is a compilation of issues found since the publication of RFC 4960 in September 2007, based on experience with implementing, testing, and using the Stream Control Transmission Protocol (SCTP) along with the suggested fixes. This document provides deltas to RFC 4960 and is organized in a time-ordered way. The issues are listed in the order in which they were brought up. Because some text is changed several times, the last delta in the text is the one that should be applied. In addition to the deltas, a description of each problem and the details of the solution for each are also provided.
URL: https://www.rfc-editor.org/rfc/rfc8540.txt
MD5: dd9ae5373c2c992b651c9c9da40b1c44
Tüxen, Michael; Stewart, Randall R.; Jesup, Randell and Loreto, Salvatore: ``Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets´´ (TXT, 21 KiB, 🇬🇧), Standards Track RFC 8261, IETF, DOI 10.17487/RFC8261, ISSN 2070-1721, November 2017, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-dtls-encaps-09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-tsvwg-sctp-dtls-encaps-01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) is a transport protocol originally defined to run on top of the network protocols IPv4 or IPv6. This document specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol. Using the encapsulation method described in this document, SCTP is unaware of the protocols being used below DTLS; hence, explicit IP addresses cannot be used in the SCTP control chunks. As a consequence, the SCTP associations carried over DTLS can only be single-homed.
URL: https://www.rfc-editor.org/rfc/rfc8261.txt
MD5: 0a4d0602366ca70c4a3f0005fd4cf3d0
Stewart, Randall R.; Tüxen, Michael; Loreto, Salvatore and Seggelmann, Robin: ``Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol´´ (TXT, 50 KiB, 🇬🇧), Standards Track RFC 8260, IETF, DOI 10.17487/RFC8260, ISSN 2070-1721, November 2017, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-ndata-13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-stewart-tsvwg-sctp-ndata-03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) is a message-oriented transport protocol supporting arbitrarily large user messages. This document adds a new chunk to SCTP for carrying payload data. This allows a sender to interleave different user messages that would otherwise result in head-of-line blocking at the sender. The interleaving of user messages is required for WebRTC data channels.
URL: https://www.rfc-editor.org/rfc/rfc8260.txt
MD5: 03c8abcd8fea90ca1c6d27aadfc8bb09
Holmberg, Christer; Shpount, Roman; Loreto, Salvatore and Camarillo, Gonzalo: ``Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)´´ (application/x-wine-extension-ini, 54 KiB, 🇬🇧), Internet Draft draft-ietf-mmusic-sctp-sdp-26, IETF, April 20, 2017, [BibTeX, XML].
Previous versions: draft-ietf-mmusic-sctp-sdp-25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) is a transport protocol used to establish associations between two endpoints. RFC 8261 specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol, which is referred to as SCTP-over-DTLS. This specification defines the following new Session Description Protocol (SDP) protocol identifiers (proto values): "UDP/DTLS/SCTP" and "TCP/DTLS/SCTP". This specification also specifies how to use the new proto values with the SDP offer/answer mechanism for negotiating SCTP-over-DTLS associations.
URL: https://tools.ietf.org/id/draft-ietf-mmusic-sctp-sdp-26.txt
MD5: 0e68ad8cf3ddaed72122e4bfdd39cd60
Nishida, Yoshifumi; Natarajan, Preethi; Caro, Armando L.; Amer, Paul D. and Nielsen, Karen E. E.: ``SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol´´ (TXT, 53 KiB, 🇬🇧), Standards Track RFC 7829, IETF, DOI 10.17487/RFC7829, ISSN 2070-1721, April 2016, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-failover-16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-nishida-tsvwg-sctp-failover-05, 04, 03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) supports multihoming. However, when the failover operation specified in RFC 4960 is followed, there can be significant delay and performance degradation in the data transfer path failover. This document specifies a quick failover algorithm and introduces the SCTP Potentially Failed (SCTP-PF) destination state in SCTP Path Management.
URL: https://www.rfc-editor.org/rfc/rfc7829.txt
MD5: 60d432c139bf20e68d6df218163bfa95
Penno, Reinaldo; Perreault, Simon; Boucadair, Mohamed; Sivakumar, Senthil and Naito, Kengo: ``Updates to Network Address Translation (NAT) Behavioral Requirements´´ (TXT, 29 KiB, 🇬🇧), Best Current Practice RFC 7857, IETF, DOI 10.17487/RFC7857, ISSN 2070-1721, April 2016, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-behave-requirements-update-08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document clarifies and updates several requirements of RFCs 4787, 5382, and 5508 based on operational and development experience. The focus of this document is Network Address Translation from IPv4 to IPv4 (NAT44).
URL: https://www.rfc-editor.org/rfc/rfc7857.txt
MD5: a9336f2acc5edd1ab5ec0a33499ea3f4
Morand, Lionel and Bonnet, Cedric: ``Update of the List of Configurable SCTP Protocol Parameters´´ (TXT, 12 KiB, 🇬🇧), Internet Draft draft-morand-tsvwg-sctp-parameters-update-00, IETF, Individual Submission, March 7, 2016, [BibTeX, XML].
Abstract: In the SCTP protocol stack implementations available for deployment in operational networks, it has been usually observed that the list of parameters that can be configured by the operators is often restricted to the list of SCTP protocol parameter values that are recommended for SCTP given in the IETF RFC 4960. However, this list is not exhaustive. This document updates the IETF RFC 4960 by including the SACK delay as part of the list of SCTP protocol parameters that can be configurable by an SCTP administrator. The associated recommended value is also given, according to the IETF RFC 4960
URL: https://tools.ietf.org/id/draft-morand-tsvwg-sctp-parameters-update-00.txt
MD5: c15c1c848d9b7297426190041ddb9119
Tüxen, Michael; Seggelmann, Robin; Stewart, Randall R. and Loreto, Salvatore: ``Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension´´ (TXT, 21 KiB, 🇬🇧), Standards Track RFC 7496, IETF, DOI 10.17487/RFC7496, ISSN 2070-1721, April 2015, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-prpolicies-07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-tsvwg-sctp-prpolicies-03, 02, 01, 00.
Abstract: This document defines two additional policies for the Partially Reliable Stream Control Transmission Protocol (PR-SCTP) extension. These policies allow limitation of the number of retransmissions and prioritization of user messages for more efficient usage of the send buffer.
URL: https://www.rfc-editor.org/rfc/rfc7496.txt
MD5: 7fbe15c06aa1e3f4ff4876603ce88e67
Stewart, Randall R.; Lei, Peter and Tüxen, Michael: ``Stream Control Transmission Protocol (SCTP) Packet Drop Reporting´´ (TXT, 27 KiB, 🇬🇧), Internet Draft draft-stewart-sctp-pktdrprep-16, IETF, Individual Submission, January 15, 2014, [BibTeX, XML].
Previous versions: draft-stewart-sctp-pktdrprep-15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes a new chunk type for SCTP. This new chunk type can be used by both endhosts and routers to report the loss of SCTP datagrams due to errors in transmission or other drops not due to congestion.
URL: https://tools.ietf.org/id/draft-stewart-sctp-pktdrprep-16.txt
MD5: 93cc5b5f6155751476e26ebf8977ab24
Tüxen, Michael; Rüngeler, Irene and Stewart, Randall R.: ``SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol´´ (TXT, 16 KiB, 🇬🇧), Standards Track RFC 7053, IETF, DOI 10.17487/RFC7053, ISSN 2070-1721, November 2013, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-sack-immediately-10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-tsvwg-sctp-sack-immediately-10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the application using an SCTP stack. Since unknown flags in chunk headers are ignored by SCTP implementations, this extension does not introduce any interoperability problems.
URL: https://www.rfc-editor.org/rfc/rfc7053.txt
MD5: cd6ad1605e58c36d3cc56bc4cbe96891
Stewart, Randall R.; Tüxen, Michael and Rüngeler, Irene: ``Stream Control Transmission Protocol (SCTP) Network Address Translation´´ (TXT, 51 KiB, 🇬🇧), Internet Draft draft-ietf-behave-sctpnat-09, IETF, September 9, 2013, [BibTeX, XML].
Previous versions: draft-ietf-behave-sctpnat-08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: Stream Control Transmission Protocol [RFC4960] provides a reliable communications channel between two end-hosts in many ways similar to TCP [RFC0793]. With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT for TCP that allows multiple hosts to reside behind a NAT and yet use only a single globally unique IPv4 address, even when two hosts (behind a NAT) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation or NAPT. To date, specialized code for SCTP has NOT yet been added to most NATs so that only pure NAT is available. The end result of this is that only one SCTP capable host can be behind a NAT. This document describes an SCTP specific variant of NAT which provides similar features of NAPT in the single point and multi-point traversal scenario.
URL: https://tools.ietf.org/id/draft-ietf-behave-sctpnat-09.txt
MD5: bdcdd79c76bc371ee7cd27d2e3d6f962
Tüxen, Michael and Stewart, Randall R.: ``UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication´´ (TXT, 26 KiB, 🇬🇧), Standards Track RFC 6951, IETF, DOI 10.17487/RFC6951, ISSN 2070-1721, May 2013, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-udp-encaps-14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-sctp-udp-encaps-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes a simple method of encapsulating Stream Control Transmission Protocol (SCTP) packets into UDP packets and its limitations. This allows the usage of SCTP in networks with legacy NATs that do not support SCTP. It can also be used to implement SCTP on hosts without directly accessing the IP layer, for example, implementing it as part of the application without requiring special privileges.
URL: https://www.rfc-editor.org/rfc/rfc6951.txt
MD5: 76d8a098f7aeeb7a20c685cd32c4846e
Seggelmann, Robin; Stewart, Randall R. and Tüxen, Michael: ``Pluggable Stream Scheduling for the Stream Control Transmission Protocol´´ (TXT, 11 KiB, 🇬🇧), Internet Draft draft-tuexen-tsvwg-sctp-scheduling-00, IETF, Individual Submission, November 19, 2012, [BibTeX, XML].
Abstract: This document describes pluggable stream scheduling to change the scheduling behavior of the Stream Control Transmission Protocol (SCTP). Pluggable stream scheduling allows to use different scheduling algorithms to optimize SCTP's behavior in different scenarios.
URL: https://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-scheduling-00.txt
MD5: 330a192561319fdc4875c34afd2d8c98
Stewart, Randall R.; Tüxen, Michael and Lei, Peter: ``Stream Control Transmission Protocol (SCTP) Stream Reconfiguration´´ (TXT, 72 KiB, 🇬🇧), Standards Track RFC 6525, IETF, DOI 10.17487/RFC6525, ISSN 2070-1721, February 2012, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-strrst-13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-stewart-tsvwg-sctpstrrst-01, 00.
Abstract: Many applications that use the Stream Control Transmission Protocol (SCTP) want the ability to "reset" a stream. The intention of resetting a stream is to set the numbering sequence of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want it so that they can "reuse" streams for different purposes but still utilize the stream sequence number so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result in message numbers greater than expected, unless there is a protocol mechanism to "reset the streams back to zero". This document also includes methods for resetting the transmission sequence numbers, adding additional streams, and resetting all stream sequence numbers.
URL: https://www.rfc-editor.org/rfc/rfc6525.txt
MD5: 2830fa011c68023335a4c1860d88b0a8
Stewart, Randall R.; Tüxen, Michael; Poon, Kacheong; Lei, Peter and Yasevich, Vladislav: ``Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)´´ (TXT, 232 KiB, 🇬🇧), Informational RFC 6458, IETF, DOI 10.17487/RFC6458, ISSN 2070-1721, December 2011, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctpsocket-32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes a mapping of the Stream Control Transmission Protocol (SCTP) into a sockets API. The benefits of this mapping include compatibility for TCP applications, access to new SCTP features, and a consolidated error and event notification scheme. This document is not an Internet Standards Track specification; it is published for informational purposes.
URL: https://www.rfc-editor.org/rfc/rfc6458.txt
MD5: 61cefc730d709cb22842b791a891d6ae
Ekiz, Nasif; Amer, Paul D.; Natarajan, Preethi; Stewart, Randall R. and Iyengar, Janardhan R.: ``Non-Renegable Selective Acknowledgements (NR-SACKs) for SCTP´´ (TXT, 41 KiB, 🇬🇧), Internet Draft draft-natarajan-tsvwg-sctp-nrsack-08, IETF, Individual Submission, August 15, 2011, [BibTeX, XML].
Previous versions: draft-natarajan-tsvwg-sctp-nrsack-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: Stream Control Transmission Protocol (SCTP) [RFC4960] specifies Selective Acknowledgements (SACKs) to allow an SCTP data receiver to acknowledge DATA chunks which arrive out-of-order. In SCTP, SACK information is advisory – though SACKs notify a data sender about the reception of specific out-of-order data, the SCTP data receiver is permitted to later discard the data, a.k.a reneging. Since delivery of a SACKed out-of-order DATA chunk is not guaranteed, a copy of this DATA chunk MUST be kept in the data sender's retransmission queue until this DATA chunk is cumulatively acked. By definition, data that has been delivered to the application is non-renegable by the SCTP data receiver. (Recall that, in SCTP, out- of-order data can sometimes be delivered.) Also, SCTP implementations can be configured such that the SCTP data receiver is not allowed to, and therefore, never reneges on out-of-order data. With SCTP's current SACK mechanism, non-renegable out-of-order data is selectively acked, and is (wrongly) deemed renegable by the SCTP data sender. This document specifies an extension to SCTP's acknowledgment mechanism called Non-Renegable Selective Acknowledgements (NR-SACKs.) NR-SACKs enable a data receiver to explicitly inform the data sender of non-renegable out-of-order data. As opposed to renegable data, a data sender can consider non-renegable data as never requiring retransmission, and therefore can remove non-renegable data from the retransmission queue.
URL: https://tools.ietf.org/id/draft-natarajan-tsvwg-sctp-nrsack-08.txt
MD5: 0955c82e76a45506f1259c3753bd3e03
Stewart, Randall R.; Lei, Peter and Tüxen, Michael: ``Uses of Stream Reconfiguration for SCTP´´ (TXT, 19 KiB, 🇬🇧), Internet Draft draft-stewart-tsvwg-reconfuse-sctp-00, IETF, Individual Submission, March 29, 2011, [BibTeX, XML].
Abstract: This document is used to convey different use cases for the Stream Reconfiguration draft xxxxxxx. It does not represent a standard nor does it represent real applications that are available for download. Instead it illustrates various use cases of the stream reconfiguration facilities for SCTP [RFC4960]. It serves as a guideline to application developers to show the stream reconfigurations various potentials.
URL: https://tools.ietf.org/id/draft-stewart-tsvwg-reconfuse-sctp-00.txt
MD5: a84dd9ebc2c42fb73264a0f24d9fa68b
Loreto, Salvatore and Camarillo, Gonzalo: ``Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)´´ (TXT, 18 KiB, 🇬🇧), Internet Draft draft-loreto-mmusic-sctp-sdp-07, IETF, Individual Submission, March 14, 2011, [BibTeX, XML].
Previous versions: draft-loreto-mmusic-sctp-sdp-06, 05, 04, 03, 02, 01, 00.
Abstract: SCTP (Stream Control Transmission Protocol) is a transport protocol used to establish associations between two endpoints. This document describes how to express media transport over SCTP in SDP (Session Description Protocol). This document defines the 'SCTP' and 'SCTP/ DTLS' protocol identifiers for SDP.
URL: https://tools.ietf.org/id/draft-loreto-mmusic-sctp-sdp-07.txt
MD5: 01a4e2f012a883adc4334de358e19128
Tüxen, Michael; Seggelmann, Robin and Rescorla, Eric: ``Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)´´ (TXT, 17 KiB, 🇬🇧), Standards Track RFC 6083, IETF, DOI 10.17487/RFC6083, ISSN 2070-1721, January 2011, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-dtls-for-sctp-06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-tsvwg-dtls-for-sctp-00.
Abstract: This document describes the usage of the Datagram Transport Layer Security (DTLS) protocol over the Stream Control Transmission Protocol (SCTP).
URL: https://www.rfc-editor.org/rfc/rfc6083.txt
MD5: fd61d60a952f67832b30ff862bffdfec
Tüxen, Michael and Stewart, Randall R.: ``Stream Control Transmission Protocol (SCTP) Chunk Flags Registration´´ (TXT, 16 KiB, 🇬🇧), Standards Track RFC 6096, IETF, DOI 10.17487/RFC6096, ISSN 2070-1721, January 2011, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-chunk-flags-02, 01, 00.
Historic versions: draft-tuexen-tsvwg-sctp-chunk-flags-00.
Abstract: This document defines the procedure for registering chunk flags with the Internet Assigned Numbers Authority (IANA) for the Stream Control Transmission Protocol (SCTP). It updates RFC 4960 and also defines the IANA registry for contents for currently defined chunk types. It does not change SCTP in any other way.
URL: https://www.rfc-editor.org/rfc/rfc6096.txt
MD5: f389ae29c46ae60428664892a5a3869b
Stewart, Randall R. and Spring, Neil: ``ECN Nonces for Stream Control Transmission Protocol (SCTP)´´ (TXT, 25 KiB, 🇬🇧), Internet Draft draft-stewart-tsvwg-sctp-nonce-02, IETF, Individual Submission, June 29, 2010, [BibTeX, XML].
Previous versions: draft-ladha-sctp-nonce-06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes the addition of the ECN-nonce RFC 3540 [RFC3540] to the Stream Control Transmission Protocol (SCTP) RFC 2960 [RFC2960]. The ECN-nonce reduces the vulnerability of ECN senders to misbehaving receivers that conceal congestion signals like ECN marks and packet losses. The ECN-nonce approach is different in SCTP because SCTP uses chunks for extensible protocol features and is selective acknowlegement (SACK)-based; this document describes those differences. In particular this document describes (1) protocol extensions in the form of a single new parameter for the INIT/ INIT-ACK chunks, and a single bit flag in the SACK chunk, and (2) rules governing the sender and receiver side implementation. This document outlines a minimum response that an SCTP sender should apply after detecting a misbehaving receiver.
URL: https://tools.ietf.org/id/draft-stewart-tsvwg-sctp-nonce-02.txt
MD5: 7ac5f5ab47477f5b537691875dbfc905
Zhu, Lei: ``Requirements and ROHC compression profile for SCTP´´ (TXT, 40 KiB, 🇬🇧), Internet Draft draft-lei-tsvwg-sctp-compr-requirements-profile-00, IETF, Individual Submission, June 22, 2010, [BibTeX, XML].
Abstract: This document is to specify the requirements to compress headers of IP/SCTP package and how ROHC mechanism compresses SCTP. Streaming Control Transport Protocol is new generation IP transport protocol which has been published in RFC2960 and updated by RFC4960. SCTP can maintain association among multiple peers, thus supports multiple homing and multiple streaming, while inherits most functions of TCP. SCTP as transport protocol has been used to carry signaling or possible user plane data in turbulence network which needs to save spectrum resource by compressing IP headers.
URL: https://tools.ietf.org/id/draft-lei-tsvwg-sctp-compr-requirements-profile-00.txt
MD5: 90c9c1743a28dec02bd997cb1a06d6c2
Claise, Benoît; Aitken, Paul; Johnson, Andrew and Muenz, Gerhard: ``IPFIX Export per SCTP Stream´´ (TXT, 58 KiB, 🇬🇧), Internet Draft draft-ietf-ipfix-export-per-sctp-stream-08, IETF, May 31, 2010, [BibTeX, XML].
Previous versions: draft-ietf-ipfix-export-per-sctp-stream-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document specifies an extension to the specifications in RFC 5101, IP Flow Information Export (IPFIX), when using the Partial Reliability extension of SCTP (PR-SCTP, Partial Reliability Stream Control Transmission Protocol). When implemented at both the Exporting Process and Collecting Process, this method offers several advantages, such as the ability to calculate Data Record losses for PR-SCTP per Template, immediate export of Template Withdrawal Messages, immediate reuse of Template IDs within an SCTP stream, reduced likelihood of Data Record loss, and reduced demands on the Collecting Process. When implemented in only the Collecting Process or Exporting Process, then normal IPFIX behavior will be seen without all of the additional benefits.
URL: https://tools.ietf.org/id/draft-ietf-ipfix-export-per-sctp-stream-08.txt
MD5: 85477e4933b0eef969a37948dc3b5946
Ogawa, Kentaro and Salim, Jamal Hadi: ``SCTP based TML (Transport Mapping Layer) for ForCES protocol´´ (TXT, 61 KiB, 🇬🇧), Internet Draft draft-ietf-forces-sctptml-08, IETF, January 19, 2010, [BibTeX, XML].
Previous versions: draft-ietf-forces-sctptml-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document defines the SCTP-based TML (Transport Mapping Layer) for the ForCES (Forwarding and Control Element Separation) protocol. It explains the rationale for choosing the SCTP (Stream Control Transmission Protocol) and also describes how this TML addresses all the requirements required by and the ForCES protocol. [STANDARDS TRACK]
URL: https://tools.ietf.org/id/draft-ietf-forces-sctptml-08.txt
MD5: 6d59c05966cdda45f7d0bda32a1e4312
Xie, Qiaobing; Stewart, Randall R.; Holdrege, Matt and Tüxen, Michael: ``SCTP NAT Traversal Considerations´´ (TXT, 13 KiB, 🇬🇧), Internet Draft draft-xie-behave-sctp-nat-cons-03, IETF, Individual Submission, November 17, 2007, [BibTeX, XML].
Previous versions: draft-xie-behave-sctp-nat-cons-02, 01, 00.
Abstract: This document defines and classifies scenarios for the usage of SCTP in networks with NATs and similar middleboxes.
URL: https://tools.ietf.org/id/draft-xie-behave-sctp-nat-cons-03.txt
MD5: a4c3706a220bd69b0a55af51b55972e6
Riegel, Max and Tüxen, Michael: ``Mobile SCTP´´ (TXT, 29 KiB, 🇬🇧), Internet Draft draft-riegel-tuexen-mobile-sctp-09, IETF, Individual Submission, November 5, 2007, [BibTeX, XML].
Previous versions: draft-riegel-tuexen-mobile-sctp-08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: Transport layer mobility management is presented in addition to Mobile IP for providing seamless mobility in the Internet. By use of SCTP (Stream Control Transmission Protocol) and some of its currently proposed extensions a seamless handover can be fully accomplished in the mobile client without any provisions in the network, only assisted by functions embedded in Mobile SCTP enabled servers. Client mobility management based on Mobile SCTP seems not to require any new protocol development. It is a particular application of SCTP eventually solving the requirements of transport layer mobility in the Internet.
URL: https://tools.ietf.org/id/draft-riegel-tuexen-mobile-sctp-09.txt
MD5: 5e393894e54c0539f7c7a28756348ef3
Stewart, Randall R.; Tüxen, Michael and Camarillo, Gonzalo: ``Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures´´ (TXT, 30 KiB, 🇬🇧), Informational RFC 5062, IETF, DOI 10.17487/RFC5062, ISSN 2070-1721, September 2007, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctpthreat-05, 04, 03, 02, 01, 00.
Historic versions: draft-stewart-tsvwg-sctpthreat-04, 03, 02, 01, 00.
Abstract: This document describes certain security threats to SCTP. It also describes ways to mitigate these threats, in particular by using techniques from the SCTP Specification Errata and Issues memo (RFC 4460). These techniques are included in RFC 4960, which obsoletes RFC 2960. It is hoped that this information will provide some useful background information for many of the newest requirements spelled out in the SCTP Specification Errata and Issues and included in RFC 4960. This memo provides information for the Internet community.
URL: https://www.rfc-editor.org/rfc/rfc5062.txt
MD5: b3feb1bb3c349fff6ffd3d23c5c71430
Stewart, Randall R.: ``Stream Control Transmission Protocol´´ (TXT, 338 KiB, 🇬🇧), RFC 4960, IETF, DOI 10.17487/RFC4960, ISSN 2070-1721, September 2007, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-2960bis-05, 04, 03, 02, 01, 00.
Abstract: This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks, but is capable of broader applications.
URL: https://www.rfc-editor.org/rfc/rfc4960.txt
MD5: 9eeb61074f2f4f6c5c88b0554ece6a4e
Stewart, Randall R.; Xie, Qiaobing; Tüxen, Michael; Maruyama, Shin and Kozuka, Masahiro: ``Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration´´ (TXT, 90 KiB, 🇬🇧), Standards Track RFC 5061, IETF, DOI 10.17487/RFC5061, ISSN 2070-1721, September 2007, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-addip-sctp-22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: A local host may have multiple points of attachment to the Internet, giving it a degree of fault tolerance from hardware failures. Stream Control Transmission Protocol (SCTP) (RFC 4960) was developed to take full advantage of such a multi-homed host to provide a fast failover and association survivability in the face of such hardware failures. This document describes an extension to SCTP that will allow an SCTP stack to dynamically add an IP address to an SCTP association, dynamically delete an IP address from an SCTP association, and to request to set the primary address the peer will use when sending to an endpoint.
URL: https://www.rfc-editor.org/rfc/rfc5061.txt
MD5: 8df71e2f2521a699a26652eac3381e9b
Tüxen, Michael; Stewart, Randall R.; Lei, Peter and Rescorla, Eric: ``Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)´´ (TXT, 42 KiB, 🇬🇧), Standards Track RFC 4895, IETF, DOI 10.17487/RFC4895, ISSN 2070-1721, August 2007, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-auth-08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-tuexen-sctp-auth-chunk-03, 02, 01, 00.
Abstract: This document describes a new chunk type, several parameters, and procedures for the Stream Control Transmission Protocol (SCTP). This new chunk type can be used to authenticate SCTP chunks by using shared keys between the sender and receiver. The new parameters are used to establish the shared keys.
URL: https://www.rfc-editor.org/rfc/rfc4895.txt
MD5: 2b7207bc23f5bb90945d8274572238a5
Trammell, Brian H. and Boschi, Elisa: ``IP Flow Information Export (IPFIX) SCTP Stream Restriction Change´´ (TXT, 20 KiB, 🇬🇧), Internet Draft draft-trammell-ipfix-sctp-change-01, IETF, Individual Submission, August 1, 2007, [BibTeX, XML].
Previous versions: draft-trammell-ipfix-sctp-change-00.
Abstract: The IPFIX protocol mandates the use of PR-SCTP as transport protocol. The document specifies the transmission of Templates over SCTP stream zero with reliable delivery and the transmission of Data Records over separate streams. This constraint is unnecessary. This document relaxes all restrictions on the use of SCTP streams within IPFIX, allowing IPFIX implementations to use SCTP streams as most appropriate for their respective applications.
URL: https://tools.ietf.org/id/draft-trammell-ipfix-sctp-change-01.txt
MD5: 774f96c585c6f8475a81006418b1f3ed
Tüxen, Michael; Stewart, Randall R. and Lei, Peter: ``Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)´´ (TXT, 12 KiB, 🇬🇧), Standards Track RFC 4820, IETF, DOI 10.17487/RFC4820, ISSN 2070-1721, March 2007, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctp-padding-02, 01, 00.
Historic versions: draft-tuexen-tsvwg-sctp-padding-01, 00.
Abstract: This document defines a padding chunk and a padding parameter and describes the required receiver side procedures. The padding chunk is used to pad a Stream Control Transmission Protocol (SCTP) packet to an arbitrary size. The padding parameter is used to pad an SCTP INIT chunk to an arbitrary size.
URL: https://www.rfc-editor.org/rfc/rfc4820.txt
MD5: 49b9e39c784d55abbe3704522a889d26
Stewart, Randall R. and Tüxen, Michael: ``Stream Control Transmission Protocol (SCTP) Interop Scoring´´ (TXT, 21 KiB, 🇬🇧), Internet Draft draft-stewart-tsvwg-sctpscore-04, IETF, Individual Submission, July 19, 2006, [BibTeX, XML].
Previous versions: draft-stewart-tsvwg-sctpscore-03, 02, 01, 00.
Abstract: This memo describes some of the scoring to be used in the testing of Stream Control Transmission Protocol (SCTP) at upcoming interops.
URL: https://tools.ietf.org/id/draft-stewart-tsvwg-sctpscore-04.txt
MD5: f19d9f9ae2b38b6ea5cabf46e351b128
Maruyama, Shin and Kozuka, Masahiro: ``Stream Control Transmission Protocol (SCTP) Cumulative ASCONF Chunk Transmission Extension´´ (TXT, 27 KiB, 🇬🇧), Internet Draft draft-marushin-sctp-asconfext-01, IETF, Individual Submission, June 26, 2006, [BibTeX, XML].
Previous versions: draft-marushin-sctp-asconfext-00.
Abstract: This document describes extensions to the Stream Control Transmission Protocol(SCTP) [RFC2960] and the "Dynamic Address Reconfiguration" [draft-ietf-tsvwg-addip-sctp]. In this proposal, we propose changes to the way ASCONF's are handled and bundled to allow multiple ASCONF's to be sent during times of disconnected connectivity. This then allows a method which allows the retransmit of multiple ASCONF chunk within a single packet to better support reliable handover.
URL: https://tools.ietf.org/id/draft-marushin-sctp-asconfext-01.txt
MD5: 8a2604f115705d0c23b155b3763d5498
Stewart, Randall R.; Rodríguez, Iván Arias; Poon, Kacheong; Caro, Armando L. and Tüxen, Michael: ``Stream Control Transmission Protocol (SCTP) Specification Errata and Issues´´ (TXT, 211 KiB, 🇬🇧), Informational RFC 4460, IETF, DOI 10.17487/RFC4460, ISSN 2070-1721, April 2006, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctpimpguide-16, 15, 14, 13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document is a compilation of issues found during six interoperability events and 5 years of experience with implementing, testing, and using SCTP along with the suggested fixes. This document provides deltas to RFC 2960 and is organized in a time-based way. The issues are listed in the order they were brought up. Because some text is changed several times, the last delta in the text is the one that should be applied. In addition to the delta, a description of the problem and the details of the solution are also provided. This memo provides information for the Internet community.
URL: https://www.rfc-editor.org/rfc/rfc4460.txt
MD5: 78bc6d48031bb8606f4d618fd0abed95
Iyengar, Janardhan R.; Amer, Paul D.; Stewart, Randall R. and Rodríguez, Iván Arias: ``Preventing SCTP Congestion Window Overgrowth During Changeover´´ (TXT, 23 KiB, 🇬🇧), Internet Draft draft-iyengar-sctp-cacc-03, IETF, Individual Submission, December 2, 2005, [BibTeX, XML].
Previous versions: draft-iyengar-sctp-cacc-02, 01, 00.
Abstract: SCTP [RFC2960] supports IP multihoming at the transport layer. SCTP allows an association to span multiple local and peer IP addresses, and allows the application to dynamically change the primary destination during an active association. We present a problem in the current SCTP specification that results in unnecessary retransmissions and "TCP-unfriendly" growth of the sender's congestion window during certain changeover conditions. We present the problem and propose an algorithm called the Split Fast Retransmit Changeover Aware Congestion Control algorithm (SFR-CACC) as a solution. We recommend the addition of SFR-CACC to the SCTP specification [RFC2960].
URL: https://tools.ietf.org/id/draft-iyengar-sctp-cacc-03.txt
MD5: 035f34210c38cca45be5334c89bd169c
Al, Ahmed Abd El; Saadawi, Tarek N. and Lee, Myung J.: ``Load Sharing in Stream Control Transmission Protocol´´ (TXT, 62 KiB, 🇬🇧), Internet Draft draft-ahmed-lssctp-01, IETF, Individual Submission, May 19, 2005, [BibTeX, XML].
Previous versions: draft-ahmed-lssctp-00.
Abstract: Stream Control Transmission Protocol (SCTP) RFC2960 [SXM00] specifications utilize the possible multiple paths between the sender and receiver for retransmission of lost data chunks and as a backup for the primary path, in case of primary path failure. Other than that, all the data chunks are being sent on the primary path chosen by the SCTP user during the association initiation. This memo describes an extension to SCTP that allows endpoints to use the multiple available paths for simultaneous data transmission. The extension maintains SCTP congestion control on each path, so as to ensure fair integration with other traffic in the network.
URL: https://tools.ietf.org/id/draft-ahmed-lssctp-01.txt
MD5: 1c03d8b8dc5abdc68284ceeb34440bec
Bansal, Vivek and Ezhirpavai, R: ``SCTP Sockets API Extension for Congestion Handling´´ (TXT, 24 KiB, 🇬🇧), Internet Draft draft-vibansal-sctpsocket-congestion-00, IETF, Individual Submission, December 7, 2004, [BibTeX, XML].
Abstract: This draft defines extension to the SCTP Socket API draft[1] for Congestion Handling. SCTP Protocol has been widely accepted by the VoIP forum. SIGTRAN protocols (M3UA/SUA/M2UA/M2PA etc) provide procedures for handling congestion notification from the SCTP Stack layer. This draft provides mechanism for SCTP applications to enable/ disable notification of congestion indications over SCTP Socket Interface. This draft suggests notification to application at onset and abatement of congestion.
URL: https://tools.ietf.org/id/draft-vibansal-sctpsocket-congestion-00.txt
MD5: c6d8d135f26874c86d1ebbed005c2b19
Pastor-Balbas, Javier and Belinchón, Maria-Carmen: ``Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)´´ (TXT, 81 KiB, 🇬🇧), Standards Track RFC 3873, IETF, DOI 10.17487/RFC3873, ISSN 2070-1721, September 2004, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-sctp-mib-10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) is a reliable transport protocol operating on top of a connectionless packet network such as IP. It is designed to transport public switched telephone network (PSTN) signaling messages over the connectionless packet network, but is capable of broader applications.
URL: https://www.rfc-editor.org/rfc/rfc3873.txt
MD5: 0abd2ec982fcb655651024020859c50a
Xie, Qiaobing: ``SCTP NAT Transverse Considerations´´ (TXT, 14 KiB, 🇬🇧), Internet Draft draft-xie-tsvwg-sctp-nat-00, IETF, Individual Submission, July 9, 2004, [BibTeX, XML].
Abstract: This document provides guidelines and solutions for dealing with SCTP association transversing NAT and similar middleboxes.
URL: https://tools.ietf.org/id/draft-xie-tsvwg-sctp-nat-00.txt
MD5: 4dfc1190359c80765e7398401acab73b
Koh, Seok-Joo and Xie, Qiaobing: ``Mobile SCTP with Mobile IP for Transport Layer Mobility´´ (TXT, 27 KiB, 🇬🇧), Internet Draft draft-sjkoh-mobile-sctp-mobileip-04, IETF, Individual Submission, June 22, 2004, [BibTeX, XML].
Previous versions: draft-sjkoh-mobile-sctp-mobileip-03, 02, 01, 00.
Abstract: Mobile SCTP (mSCTP) is defined as SCTP with the ADDIP extension. The mSCTP can be used for providing seamless handover by exploiting its multi-homing feature. On the other hand, the Mobile IP basically provides the location management. In this document, we discuss the use of mSCTP along with Mobile IP for Internet mobility support in the transport layer. The use of SCTP with Mobile IP is focused on the mobile sessions that are initiated by CN to MN.
URL: https://tools.ietf.org/id/draft-sjkoh-mobile-sctp-mobileip-04.txt
MD5: ea8de46f82bd9fd18332743d3a9bf572
Koh, Seok-Joo: ``Mobile SCTP for Transport Layer Mobility´´ (TXT, 37 KiB, 🇬🇧), Internet Draft draft-sjkoh-sctp-mobility-04, IETF, Individual Submission, June 15, 2004, [BibTeX, XML].
Previous versions: draft-sjkoh-sctp-mobility-03, 02, 01, 00.
Abstract: This document discusses the architecture of mobile SCTP (mSCTP) for IP mobility support. The SCTP is the third transport layer protocol next to TCP/UDP. It can also be used for IP mobility from the multi- homing features. The SCTP with the ADDIP extension (or mSCTP) would provide seamless or soft handover for the mobile host without support of routers or agents in the networks. For location management, the mSCTP could be used along with Mobile IP, Session Initiation Protocol or Reliable Server Pooling.
URL: https://tools.ietf.org/id/draft-sjkoh-sctp-mobility-04.txt
MD5: 555bf644fc828f0815862c14f31d06b8
Stewart, Randall R.; Ramalho, Michael A.; Xie, Qiaobing; Tüxen, Michael and Conrad, Phillip T.: ``Stream Control Transmission Protocol (SCTP) Partial Reliability Extension´´ (TXT, 50 KiB, 🇬🇧), Standards Track RFC 3758, IETF, DOI 10.17487/RFC3758, ISSN 2070-1721, May 2004, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-prsctp-03, 02, 01, 00.
Historic versions: draft-stewart-tsvwg-prsctp-04, 03, 02, 01, 00.
Abstract: This memo describes an extension to the Stream Control Transmission Protocol (SCTP) that allows an SCTP endpoint to signal to its peer that it should move the cumulative ack point forward. When both sides of an SCTP association support this extension, it can be used by an SCTP implementation to provide partially reliable data transmission service to an upper layer protocol. This memo describes the protocol extensions, which consist of a new parameter for INIT and INIT ACK, and a new FORWARD TSN chunk type, and provides one example of a partially reliable service that can be provided to the upper layer via this mechanism.
URL: https://www.rfc-editor.org/rfc/rfc3758.txt
MD5: 0c9d421b69393c27cfc729e606373157
Schmidt, Christian and Tüxen, Michael: ``Requirements for RoHC IP/SCTP Robust Header Compression´´ (TXT, 19 KiB, 🇬🇧), Internet Draft draft-ietf-rohc-sctp-requirements-03, IETF, September 26, 2003, [BibTeX, XML].
Previous versions: draft-ietf-rohc-sctp-requirements-02, 01, 00.
Abstract: This document contains requirements for the IP/SCTP header compression scheme (profile) to be developed by the ROHC WG. The structure of this document is inherited from the document defining IP/TCP requirements for ROHC.
URL: https://tools.ietf.org/id/draft-ietf-rohc-sctp-requirements-03.txt
MD5: 4a8519e04a57ee8eade1541f651a9c21
Pastor-Balbas, Javier and Coene, Lode: ``Telephony Signalling Transport over SCTP applicability statement´´ (TXT, 45 KiB, 🇬🇧), Internet Draft draft-ietf-sigtran-signalling-over-sctp-applic-09, IETF, August 5, 2003, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-signalling-over-sctp-applic-08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes the applicability of the several protocols developed under the signalling transport framework. A description of the main issues regarding the use of the Stream Control Transmission Protocol (SCTP) and an explanation of each adaptation layer for transport of telephony signalling information over IP infrastructure are given. This memo provides information for the Internet community.
URL: https://tools.ietf.org/id/draft-ietf-sigtran-signalling-over-sctp-applic-09.txt
MD5: 4fb19c2bc1b416ea317b40cc0125d4b6
Bellovin, Steven M.; Ioannidis, John; Keromytis, Angelos D. and Stewart, Randall R.: ``On the Use of Stream Control Transmission Protocol (SCTP) with IPsec´´ (TXT, 20 KiB, 🇬🇧), Standards Track RFC 3554, IETF, DOI 10.17487/RFC3554, ISSN 2070-1721, July 2003, [BibTeX, XML].
Previous versions: draft-ietf-ipsec-sctp-05, 04, 03, 02, 01, 00.
Abstract: This document describes functional requirements for IPsec (RFC 2401) and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in securing SCTP (RFC 2960) traffic.
URL: https://www.rfc-editor.org/rfc/rfc3554.txt
MD5: f028d5c10961516d6c892f1e462a2474
West, Mark A. and Surtees, Abigail: ``SCTP Profile for EPIC´´ (TXT, 52 KiB, 🇬🇧), Internet Draft draft-west-sctp-epic-01, IETF, Individual Submission, June 27, 2003, [BibTeX, XML].
Previous versions: draft-west-sctp-epic-00.
Abstract: This draft describes a profile for compressing SCTP/IP using the Robust Header Compression Formal Notation. The RObust Header Compression [1] scheme is designed to compress packet headers over error prone channels. It is built around an extensible core framework that can be tailored to compress new protocol stacks by adding additional ROHC profiles. This profile describes a new profile for ROHC which will allow SCTP/ IP headers to be compressed.
URL: https://tools.ietf.org/id/draft-west-sctp-epic-01.txt
MD5: b90ac9bfbaae1909e64d3a0e238fb97f
Pastor-Balbas, Javier and Belinchón, Maria-Carmen: ``Stream Control Transmission Protocol Management Information Base´´ (TXT, 81 KiB, 🇬🇧), Internet Draft draft-ietf-sigtran-sctp-mib-10, IETF, June 6, 2003, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-sctp-mib-09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Abstract: The Stream Control Transmission Protocol (SCTP) is a reliable transport protocol operating on top of a connectionless packet network such as IP. It is designed to transport public switched telephone network (PSTN) signaling messages over the connectionless packet network, but is capable of broader applications. This memo defines the Management Information Base (MIB) module which describes the minimum set of objects needed to manage the implementation of the SCTP.
URL: https://tools.ietf.org/id/draft-ietf-sigtran-sctp-mib-10.txt
MD5: b1a76217884d1c93c4a516cab7b1ee8e
Koh, Seok-Joo: ``Use of SCTP for Seamless Handover´´ (TXT, 25 KiB, 🇬🇧), Internet Draft draft-sjkoh-mobile-sctp-handover-00, IETF, Individual Submission, February 12, 2003, [BibTeX, XML].
Abstract: The Stream Control Transmission Protocol (SCTP) is a new reliable transport protocol that provides the multihoming feature. Without support of routers in the networks, the SCTP with the ADDIP extension (called mobile SCTP) can be used to provide seamless handover for the mobile host that is changing its IP subnetworks during the session. In the present form, the use of mobile SCTP is targeted for handover of the mobile sessions that are originated from the mobile clients (located in mobile networks) toward the fixed servers (located in the fixed networks). The support for the opposite directional session (initiated by fixed node to mobile node) requires an additional location management scheme such as Mobile IP. In this document, we discuss the generic procedures for seamless handover of mobile SCTP and the concerned implementation issues.
URL: https://tools.ietf.org/id/draft-sjkoh-mobile-sctp-handover-00.txt
MD5: 05363cbfb6e6603aac0d0aa42c8bfdd7
Jungmaier, Andreas; Rescorla, Eric and Tüxen, Michael: ``Transport Layer Security over Stream Control Transmission Protocol´´ (TXT, 16 KiB, 🇬🇧), Standards Track RFC 3436, IETF, DOI 10.17487/RFC3436, ISSN 2070-1721, December 2002, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-tls-over-sctp-00.
Abstract: This document describes the usage of the Transport Layer Security (TLS) protocol, as defined in RFC 2246, over the Stream Control Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309. The user of TLS can take advantage of the features provided by SCTP, namely the support of multiple streams to avoid head of line blocking and the support of multi-homing to provide network level fault tolerance. Additionally, discussions of extensions of SCTP are also supported, meaning especially the support of dynamic reconfiguration of IP- addresses.
URL: https://www.rfc-editor.org/rfc/rfc3436.txt
MD5: e859fb7bbf61142eb6527425ef2cec25
Stone, Jonathan; Stewart, Randall R. and Otis, Douglas: ``Stream Control Transmission Protocol (SCTP) Checksum Change´´ (TXT, 34 KiB, 🇬🇧), Standards RFC 3309, IETF, DOI 10.17487/RFC3309, ISSN 2070-1721, September 2002, [BibTeX, XML].
Previous versions: draft-ietf-tsvwg-sctpcsum-06, 05, 04, 03, 02, 01, 00.
URL: https://www.rfc-editor.org/rfc/rfc3309.txt
MD5: 197f2ac17be990dc4ba7c6a3a90d5cc0
Loughney, John A. and Sanchez, Raquel: ``SCTP Layer for Transporting Signaling Protocols´´ (application/octet-stream, 13 KiB, 🇬🇧), Internet Draft draft-loughney-sctp-sig-prot-00, IETF, Individual Submission, June 27, 2002, [BibTeX, XML].
Abstract: The Stream Control Transport Protocol (SCTP) has been standardized to provide a reliable transport services for signaling protocols. SCTP features a number of new features that are useful for transporting signaling protocols, but may require additional information on how to use them to transport existing signaling protocols.
URL: https://tools.ietf.org/id/draft-loughney-sctp-sig-prot-00.txt
MD5: 97593513166c44bb332219bd317451ec
Ong, Lyndon and Yoakum, John: ``An Introduction to the Stream Control Transmission Protocol (SCTP)´´ (TXT, 23 KiB, 🇬🇧), Informational RFC 3286, IETF, DOI 10.17487/RFC3286, ISSN 2070-1721, May 2002, [BibTeX, XML].
Previous versions: draft-ong-sigtran-sctpover-01, 00.
Abstract: This document provides a high level introduction to the capabilities supported by the Stream Control Transmission Protocol (SCTP). It is intended as a guide for potential users of SCTP as a general purpose transport protocol. This memo provides information for the Internet community.
URL: https://www.rfc-editor.org/rfc/rfc3286.txt
MD5: 3962ec32c91639aae167ee96badf6cdf
Yoakum, John and Ong, Lyndon: ``An Introduction to the SCTP´´ (TXT, 2 KiB, 🇬🇧), Internet Draft draft-ong-sigtran-sctpover-02, IETF, Individual Submission, May 15, 2002, [BibTeX, XML].
Previous versions: draft-ong-sigtran-sctpover-01, 00.
Abstract: This document provides a high level introduction to the capabilities supported by the Stream Control Transmission Protocol (SCTP). It is intended as a guide for potential users of SCTP as a general purpose transport protocol. This memo provides information for the Internet community.
URL: https://tools.ietf.org/id/draft-ong-sigtran-sctpover-02.txt
MD5: 045414cc087efef3540cac97c6c41c8f
Coene, Lode: ``Stream Control Transmission Protocol Applicability Statement´´ (TXT, 24 KiB, 🇬🇧), Informational RFC 3257, IETF, DOI 10.17487/RFC3257, ISSN 2070-1721, April 2002, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-sctp-applicability-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: <p>This document describes the applicability of the Stream Control Transmission Protocol (SCTP). It also contrasts SCTP with the two dominant transport protocols, User Datagram Protocol (UDP) & Transmission Control Protocol (TCP), and gives some guidelines for when best to use SCTP and when not best to use SCTP. This memo provides information for the Internet community.</p>
URL: https://www.rfc-editor.org/rfc/rfc3257.txt
MD5: 17532fe7fca05269d94f29717536e22c
Coene, Lode: ``Stream Control Transmission Protocol Applicability Statement´´ (TXT, 3 KiB, 🇬🇧), Internet Draft draft-ietf-sigtran-sctp-applicability-08, IETF, April 13, 2002, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-sctp-applicability-07, 06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes the applicability of the Stream Control Transmission Protocol (SCTP). It also contrasts SCTP with the two dominant transport protocols, User Datagram Protocol (UDP) & Transmission Control Protocol (TCP), and gives some guidelines for when best to use SCTP and when not best to use SCTP. This memo provides information for the Internet community.
URL: https://tools.ietf.org/id/draft-ietf-sigtran-sctp-applicability-08.txt
MD5: 75f12811e1c058eb517f347c911d68a5
Stewart, Randall R.: ``SCTP DDP Adaptation´´ (TXT, 11 KiB, 🇬🇧), Internet Draft draft-stewart-sctp-roi-00, IETF, Individual Submission, March 27, 2002, [BibTeX, XML].
Abstract: This document describes a method to adapt DDP to SCTP using a generic DDP description found in [DDP-DRAFT]. This adaption provides a method for two peers to know that each side is performing direct placement thus enabling hardware acceleration if available.
URL: https://tools.ietf.org/id/draft-stewart-sctp-roi-00.txt
MD5: 013aee1d4c55e0cf3e3b102e951a41d0
Stewart, Randall R. and Otis, Douglas: ``SCTP DDP/RDMA Adaptation´´ (TXT, 21 KiB, 🇬🇧), Internet Draft draft-stewart-otis-sctp-ddp-rdma-01, IETF, Individual Submission, February 27, 2002, [BibTeX, XML].
Previous versions: draft-otis-sctp-ddp-01, 00.
Abstract: In many applications, direct placement of data without the overhead of multiple copies or excessive context switching is a desirable feature. To accomplish this goal, a direct placement adaptation layer is defined within this document.
URL: https://tools.ietf.org/id/draft-stewart-otis-sctp-ddp-rdma-01.txt
MD5: 21871004ff405d1f752aa715f78e6267
Stewart, Randall R.; Xie, Qiaobing; Morneault, Ken; Sharp, Chip; Schwarzbauer, Hanns Jürgen; Taylor, Tom; Rytina, Ian; Kalla, Malleswar; Zhang, Lixia and Paxson, Vern: ``Stream Control Transmission Protocol´´ (TXT, 291 KiB, 🇬🇧), Standards Track RFC 2960, IETF, DOI 10.17487/RFC2960, ISSN 2070-1721, October 2000, [BibTeX, XML].
Previous versions: draft-ietf-sigtran-sctp-13, 12, 11, 10, 09, 08, 07, 06, 05, 04, 03, 02, 01, 00.
Historic versions: draft-ietf-sigtran-mdtp-06, 05, 04, 03, 02, 01, 00.
Abstract: This document describes the Stream Control Transmission Protocol (SCTP).
URL: https://www.rfc-editor.org/rfc/rfc2960.txt
MD5: 8c7ae0988fb53c647b7111bb6c9af1d4
If something is missing, see the Internet Draft archive at Watersprings.org. Please also contact me in case of missing or dead links.
Please use the issue tracker at https://github.com/dreibh/sctplib/issues (sctplib) and https://github.com/dreibh/socketapi/issues (socketapi) to report bugs and issues!
For ready-to-install Ubuntu Linux packages of sctplib and socketapi, see Launchpad PPA for Thomas Dreibholz!
sudo apt-add-repository -sy ppa:dreibh/ppa sudo apt-get update sudo apt-get install libsctplib-dev libsctplib1 sctplib-doc libsctpsocket-dev libsctpsocket2
For ready-to-install Fedora Linux packages of sctplib and socketapi, see COPR PPA for Thomas Dreibholz!
sudo dnf copr enable -y dreibh/ppa sudo dnf install sctplib-libsctplib-devel sctplib-libsctplib sctplib-docs sctplib-libsctpsocket-devel sctplib-libsctpsocket
For ready-to-install FreeBSD packages of sctplib and socketapi, it is included in the ports collection, see FreeBSD ports tree index of net/sctplib/ and FreeBSD ports tree index of net/socketapi/!
pkg install sctplib socketapi
Alternatively, to compile it from the ports sources:
cd /usr/ports/net/sctplib make make install cd /usr/ports/net/socketapi make make install
sctplib and socketapi are released under GNU General Public Licence (GPL) and partly under GNU Lesser General Public License (LGPL).
Please use the issue tracker at https://github.com/dreibh/sctplib/issues (sctplib) and https://github.com/dreibh/socketapi/issues (socketapi) to report bugs and issues!
The Git repository of the sctplib sources can be found at https://github.com/dreibh/sctplib:
git clone https://github.com/dreibh/sctplib cd sctplib ./autogen.sh
Contributions:
Issue tracker: https://github.com/dreibh/sctplib/issues.
Please submit bug reports, issues, questions, etc. in the issue tracker!
Pull Requests for sctplib: https://github.com/dreibh/sctplib/pulls.
Your contributions to sctplib are always welcome!
CI build tests of sctplib: https://github.com/dreibh/sctplib/actions.
Coverity Scan analysis of sctplib: https://scan.coverity.com/projects/dreibh-sctplib.
The Git repository of the socketapi sources can be found at https://github.com/dreibh/socketapi:
git clone https://github.com/dreibh/socketapi cd socketapi ./autogen.sh
Contributions:
Issue tracker: https://github.com/dreibh/socketapi/issues.
Please submit bug reports, issues, questions, etc. in the issue tracker!
Pull Requests for socketapi: https://github.com/dreibh/socketapi/pulls.
Your contributions to socketapi are always welcome!
CI build tests of socketapi: https://github.com/dreibh/socketapi/actions.
Coverity Scan analysis of socketapi: https://scan.coverity.com/projects/dreibh-socketapi.
The tarballs have been signed with my GnuPG key 21412672518D8B2D1862EFEF5CD5D12AA0877B49. Their authenticity and integrity can be verified by:
gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 21412672518D8B2D1862EFEF5CD5D12AA0877B49 gpg --verify PACKAGE-VERSION.tar.gz.asc PACKAGE-VERSION.tar.gz
The tarballs have been signed with my GnuPG key 21412672518D8B2D1862EFEF5CD5D12AA0877B49. Their authenticity and integrity can be verified by:
gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 21412672518D8B2D1862EFEF5CD5D12AA0877B49 gpg --verify PACKAGE-VERSION.tar.gz.asc PACKAGE-VERSION.tar.gz
