@TechReport{ draft-ahmed-lssctp,
	author = "Ahmed Abd El Al and Tarek~N. Saadawi and Myung~J. Lee",
	title = "{Load Sharing in Stream Control Transmission Protocol}",
	type = "Internet Draft",
	number = "draft-ahmed-lssctp-01",
	day = "19",
	month = may,
	year = "2005",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "62567",
	url.md5 = "1c03d8b8dc5abdc68284ceeb34440bec",
	url.mime = "text/plain",
	url.checked = "2014-04-12 21:01:08 CEST"
}

@TechReport{ draft-dreibholz-tsvwg-sctpsocket-multipath,
	author = "Thomas Dreibholz and Martin Becke and Hakim Adhari",
	title = "{SCTP Socket API Extensions for Concurrent Multipath Transfer}",
	type = "Internet Draft",
	number = "draft-dreibholz-tsvwg-sctpsocket-multipath-33",
	day = "16",
	month = sep,
	year = "2026",
	institution = "IETF, Individual Submission",
	language = "english",
	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-33.txt",
	url.size = "12623",
	url.md5 = "33b50173ded369f664c07079902bbb71",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:48 CEST"
}

@TechReport{ draft-dreibholz-tsvwg-sctpsocket-sqinfo,
	author = "Thomas Dreibholz and Robin Seggelmann and Martin Becke",
	title = "{Sender Queue Info Option for the SCTP Socket API}",
	type = "Internet Draft",
	number = "draft-dreibholz-tsvwg-sctpsocket-sqinfo-33",
	day = "16",
	month = sep,
	year = "2026",
	institution = "IETF, Individual Submission",
	language = "english",
	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-33.txt",
	url.size = "14184",
	url.md5 = "864ea52d280ca188ecdd7dcce2359c1f",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:47 CEST"
}

@TechReport{ draft-hohendorf-secure-sctp,
	author = "Carsten Hohendorf and Esbold Unurkhaan and Thomas Dreibholz",
	title = "{Secure SCTP}",
	type = "Internet Draft",
	number = "draft-hohendorf-secure-sctp-42",
	day = "16",
	month = sep,
	year = "2026",
	institution = "IETF, Individual Submission",
	language = "english",
	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, it is designed to integrate cryptographic functions into SCTP.}",
	url = "https://tools.ietf.org/id/draft-hohendorf-secure-sctp-42.txt",
	url.size = "92342",
	url.md5 = "dac86401442fad0b3b1ca66a29bb998d",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:50 CEST"
}

@TechReport{ draft-ietf-behave-sctpnat,
	author = "Randall~R. Stewart and Michael Tüxen and Irene Rüngeler",
	title = "{Stream Control Transmission Protocol~(SCTP) Network Address Translation}",
	type = "Internet Draft",
	number = "draft-ietf-behave-sctpnat-09",
	day = "9",
	month = sep,
	year = "2013",
	institution = "IETF",
	language = "english",
	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",
	url.size = "51816",
	url.md5 = "bdcdd79c76bc371ee7cd27d2e3d6f962",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:52 CEST"
}

@TechReport{ draft-ietf-forces-sctptml,
	author = "Kentaro Ogawa and Jamal Hadi Salim",
	title = "{SCTP based TML~(Transport Mapping Layer) for ForCES protocol}",
	type = "Internet Draft",
	number = "draft-ietf-forces-sctptml-08",
	day = "19",
	month = jan,
	year = "2010",
	institution = "IETF",
	language = "english",
	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",
	url.size = "61602",
	url.md5 = "6d59c05966cdda45f7d0bda32a1e4312",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:05 CEST"
}

@TechReport{ draft-ietf-ipfix-export-per-sctp-stream,
	author = "Benoît Claise and Paul Aitken and Andrew Johnson and Gerhard Muenz",
	title = "{IPFIX Export per SCTP Stream}",
	type = "Internet Draft",
	number = "draft-ietf-ipfix-export-per-sctp-stream-08",
	day = "31",
	month = may,
	year = "2010",
	institution = "IETF",
	language = "english",
	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",
	url.size = "58667",
	url.md5 = "85477e4933b0eef969a37948dc3b5946",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:05 CEST"
}

@TechReport{ draft-ietf-mmusic-sctp-sdp,
	author = "Christer Holmberg and Roman Shpount and Salvatore Loreto and Gonzalo Camarillo",
	title = "{Stream Control Transmission Protocol~(SCTP)-Based Media Transport in the Session Description Protocol~(SDP)}",
	type = "Internet Draft",
	number = "draft-ietf-mmusic-sctp-sdp-26",
	day = "20",
	month = apr,
	year = "2017",
	institution = "IETF",
	language = "english",
	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",
	url.size = "54785",
	url.md5 = "0e68ad8cf3ddaed72122e4bfdd39cd60",
	url.mime = "application/x-wine-extension-ini",
	url.checked = "2026-05-26 23:03:06 CEST"
}

@TechReport{ draft-ietf-rohc-sctp-requirements,
	author = "Christian Schmidt and Michael Tüxen",
	title = "{Requirements for RoHC IP/SCTP Robust Header Compression}",
	type = "Internet Draft",
	number = "draft-ietf-rohc-sctp-requirements-03",
	day = "26",
	month = sep,
	year = "2003",
	institution = "IETF",
	language = "english",
	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",
	url.size = "18955",
	url.md5 = "4a8519e04a57ee8eade1541f651a9c21",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:06 CEST"
}

@TechReport{ draft-ietf-sigtran-sctp-applicability,
	author = "Lode Coene",
	title = "{Stream Control Transmission Protocol Applicability Statement}",
	type = "Internet Draft",
	number = "draft-ietf-sigtran-sctp-applicability-08",
	day = "13",
	month = apr,
	year = "2002",
	institution = "IETF",
	language = "english",
	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",
	url.size = "2082",
	url.md5 = "75f12811e1c058eb517f347c911d68a5",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:06 CEST"
}

@TechReport{ draft-ietf-sigtran-sctp-mib,
	author = "Javier Pastor-Balbas and Maria-Carmen Belinchón",
	title = "{Stream Control Transmission Protocol Management Information Base}",
	type = "Internet Draft",
	number = "draft-ietf-sigtran-sctp-mib-10",
	day = "6",
	month = jun,
	year = "2003",
	institution = "IETF",
	language = "english",
	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",
	url.size = "82783",
	url.md5 = "b1a76217884d1c93c4a516cab7b1ee8e",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:07 CEST"
}

@TechReport{ draft-ietf-sigtran-signalling-over-sctp-applic,
	author = "Javier Pastor-Balbas and Lode Coene",
	title = "{Telephony Signalling Transport over SCTP applicability statement}",
	type = "Internet Draft",
	number = "draft-ietf-sigtran-signalling-over-sctp-applic-09",
	day = "5",
	month = aug,
	year = "2003",
	institution = "IETF",
	language = "english",
	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",
	url.size = "45839",
	url.md5 = "4fb19c2bc1b416ea317b40cc0125d4b6",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:07 CEST"
}

@TechReport{ draft-ietf-tsvwg-dtls-over-sctp-bis,
	author = "Magnus Westerlund and John Preuß Mattsson and Claudio Porfiri",
	title = "{Datagram Transport Layer Security~(DTLS) over Stream Control Transmission Protocol~(SCTP)}",
	type = "Internet Draft",
	number = "draft-ietf-tsvwg-dtls-over-sctp-bis-08",
	day = "3",
	month = may,
	year = "2024",
	institution = "IETF",
	language = "english",
	abstract = "{This document describes the usage of the Datagram Transport Layer Security~(DTLS) protocol to protect user messages sent over the Stream Control Transmission Protocol~(SCTP). It is an improved alternative to the existing RFC~6083. DTLS over SCTP provides mutual authentication, confidentiality, integrity protection, and partial replay protection for applications that use SCTP as their transport protocol and allows client/server applications to communicate in a way that is designed to give communications privacy and to prevent eavesdropping and detect tampering or message forgery. Applications using DTLS over SCTP can use almost all transport features provided by SCTP and its extensions. This document is an improved alternative to RFC~6083 and removes the 16 kbytes limitation on protected user message size by defining a secure user message fragmentation so that multiple DTLS records can be used to protect a single user message. It further contains a large number of security fixes and improvements. It updates the DTLS versions and SCTP-AUTH HMAC algorithms to use. It mitigates reflection attacks of data and control chunks and replay attacks of data chunks. It simplifies secure implementation by some stricter requirements on the establishment procedures as well as rekeying to align with zero trust principles.}",
	url = "https://tools.ietf.org/id/draft-ietf-tsvwg-dtls-over-sctp-bis-08.txt",
	url.size = "109806",
	url.md5 = "5ca69edcb74f440f0ed57a6f37a6089b",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:03 CEST"
}

@TechReport{ draft-ietf-tsvwg-natsupp,
	author = "Randall~R. Stewart and Michael Tüxen and Irene Rüngeler",
	title = "{Stream Control Transmission Protocol~(SCTP) Network Address Translation Support}",
	type = "Internet Draft",
	number = "draft-ietf-tsvwg-natsupp-23",
	day = "25",
	month = oct,
	year = "2021",
	institution = "IETF",
	language = "english",
	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",
	url.size = "110487",
	url.md5 = "92485035b81c664b7dd389ddbe0e85b1",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:51 CEST"
}

@TechReport{ draft-ietf-tsvwg-rfc4895-bis,
	author = "Michael Tüxen and Randall~R. Stewart and Peter Lei and Hannes Tschofenig",
	title = "{Authenticated Chunks for the Stream Control Transmission Protocol~(SCTP)}",
	type = "Internet Draft",
	number = "draft-ietf-tsvwg-rfc4895-bis-05",
	day = "21",
	month = apr,
	year = "2025",
	institution = "IETF",
	language = "english",
	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. This document obsoletes RFC~4895.}",
	url = "https://tools.ietf.org/id/draft-ietf-tsvwg-rfc4895-bis-05.txt",
	url.size = "56150",
	url.md5 = "7979dcf0fedc4810e0c1d0632e5d1834",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:03 CEST"
}

@TechReport{ draft-iyengar-sctp-cacc,
	author = "Janardhan~R. Iyengar and Paul~D. Amer and Randall~R. Stewart and Iván Arias Rodríguez",
	title = "{Preventing SCTP Congestion Window Overgrowth During Changeover}",
	type = "Internet Draft",
	number = "draft-iyengar-sctp-cacc-03",
	day = "2",
	month = dec,
	year = "2005",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "23080",
	url.md5 = "035f34210c38cca45be5334c89bd169c",
	url.mime = "text/plain",
	url.checked = "2014-04-12 21:01:07 CEST"
}

@TechReport{ draft-lei-tsvwg-sctp-compr-requirements-profile,
	author = "Lei Zhu",
	title = "{Requirements and ROHC compression profile for SCTP}",
	type = "Internet Draft",
	number = "draft-lei-tsvwg-sctp-compr-requirements-profile-00",
	day = "22",
	month = jun,
	year = "2010",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "40496",
	url.md5 = "90c9c1743a28dec02bd997cb1a06d6c2",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:53 CEST"
}

@TechReport{ draft-loreto-mmusic-sctp-sdp,
	author = "Salvatore Loreto and Gonzalo Camarillo",
	title = "{Stream Control Transmission Protocol~(SCTP)-Based Media Transport in the Session Description Protocol~(SDP)}",
	type = "Internet Draft",
	number = "draft-loreto-mmusic-sctp-sdp-07",
	day = "14",
	month = mar,
	year = "2011",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "17651",
	url.md5 = "01a4e2f012a883adc4334de358e19128",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:53 CEST"
}

@TechReport{ draft-loughney-sctp-sig-prot,
	author = "John~A. Loughney and Raquel Sanchez",
	title = "{SCTP Layer for Transporting Signaling Protocols}",
	type = "Internet Draft",
	number = "draft-loughney-sctp-sig-prot-00",
	day = "27",
	month = jun,
	year = "2002",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "12573",
	url.md5 = "97593513166c44bb332219bd317451ec",
	url.mime = "application/octet-stream",
	url.checked = "2026-05-26 23:03:07 CEST"
}

@TechReport{ draft-marushin-sctp-asconfext,
	author = "Shin Maruyama and Masahiro Kozuka",
	title = "{Stream Control Transmission Protocol (SCTP) Cumulative ASCONF Chunk Transmission Extension}",
	type = "Internet Draft",
	number = "draft-marushin-sctp-asconfext-01",
	day = "26",
	month = jun,
	year = "2006",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "27092",
	url.md5 = "8a2604f115705d0c23b155b3763d5498",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:53 CEST"
}

@TechReport{ draft-morand-tsvwg-sctp-parameters-update,
	author = "Lionel Morand and Cedric Bonnet",
	title = "{Update of the List of Configurable SCTP Protocol Parameters}",
	type = "Internet Draft",
	number = "draft-morand-tsvwg-sctp-parameters-update-00",
	day = "7",
	month = mar,
	year = "2016",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "12035",
	url.md5 = "c15c1c848d9b7297426190041ddb9119",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:04 CEST"
}

@TechReport{ draft-natarajan-tsvwg-sctp-nrsack,
	author = "Nasif Ekiz and Paul~D. Amer and Preethi Natarajan and Randall~R. Stewart and Janardhan~R. Iyengar",
	title = "{Non-Renegable Selective Acknowledgements~(NR-SACKs) for SCTP}",
	type = "Internet Draft",
	number = "draft-natarajan-tsvwg-sctp-nrsack-08",
	day = "15",
	month = aug,
	year = "2011",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "41772",
	url.md5 = "0955c82e76a45506f1259c3753bd3e03",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:54 CEST"
}

@TechReport{ draft-ong-sigtran-sctpover,
	author = "John Yoakum and Lyndon Ong",
	title = "{An Introduction to the SCTP}",
	type = "Internet Draft",
	number = "draft-ong-sigtran-sctpover-02",
	day = "15",
	month = may,
	year = "2002",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "1930",
	url.md5 = "045414cc087efef3540cac97c6c41c8f",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:08 CEST"
}

@TechReport{ draft-proshin-tsvwg-sctp-rtx-bit,
	author = "Maksim Proshin",
	title = "{Retransmit bit for SCTP DATA, I-DATA and SACK}",
	type = "Internet Draft",
	number = "draft-proshin-tsvwg-sctp-rtx-bit-03",
	day = "1",
	month = jun,
	year = "2020",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "27146",
	url.md5 = "dd68dac19392f454f65821df6782d691",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:56 CEST"
}

@TechReport{ draft-riegel-tuexen-mobile-sctp,
	author = "Max Riegel and Michael Tüxen",
	title = "{Mobile SCTP}",
	type = "Internet Draft",
	number = "draft-riegel-tuexen-mobile-sctp-09",
	day = "5",
	month = nov,
	year = "2007",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "29451",
	url.md5 = "5e393894e54c0539f7c7a28756348ef3",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:54 CEST"
}

@TechReport{ draft-sjkoh-mobile-sctp-handover,
	author = "Seok-Joo Koh",
	title = "{Use of SCTP for Seamless Handover}",
	type = "Internet Draft",
	number = "draft-sjkoh-mobile-sctp-handover-00",
	day = "12",
	month = feb,
	year = "2003",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "25195",
	url.md5 = "05363cbfb6e6603aac0d0aa42c8bfdd7",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:10 CEST"
}

@TechReport{ draft-sjkoh-mobile-sctp-mobileip,
	author = "Seok-Joo Koh and Qiaobing Xie",
	title = "{Mobile SCTP with Mobile IP for Transport Layer Mobility}",
	type = "Internet Draft",
	number = "draft-sjkoh-mobile-sctp-mobileip-04",
	day = "22",
	month = jun,
	year = "2004",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "27504",
	url.md5 = "ea8de46f82bd9fd18332743d3a9bf572",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:55 CEST"
}

@TechReport{ draft-sjkoh-sctp-mobility,
	author = "Seok-Joo Koh",
	title = "{Mobile SCTP for Transport Layer Mobility}",
	type = "Internet Draft",
	number = "draft-sjkoh-sctp-mobility-04",
	day = "15",
	month = jun,
	year = "2004",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "36901",
	url.md5 = "555bf644fc828f0815862c14f31d06b8",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:55 CEST"
}

@TechReport{ draft-stewart-otis-sctp-ddp-rdma,
	author = "Randall~R. Stewart and Douglas Otis",
	title = "{SCTP DDP/RDMA Adaptation}",
	type = "Internet Draft",
	number = "draft-stewart-otis-sctp-ddp-rdma-01",
	day = "27",
	month = feb,
	year = "2002",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "20617",
	url.md5 = "21871004ff405d1f752aa715f78e6267",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:54 CEST"
}

@TechReport{ draft-stewart-sctp-pktdrprep,
	author = "Randall~R. Stewart and Peter Lei and Michael Tüxen",
	title = "{Stream Control Transmission Protocol~(SCTP) Packet Drop Reporting}",
	type = "Internet Draft",
	number = "draft-stewart-sctp-pktdrprep-16",
	day = "15",
	month = jan,
	year = "2014",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "26667",
	url.md5 = "93cc5b5f6155751476e26ebf8977ab24",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:08 CEST"
}

@TechReport{ draft-stewart-sctp-roi,
	author = "Randall~R. Stewart",
	title = "{SCTP DDP Adaptation}",
	type = "Internet Draft",
	number = "draft-stewart-sctp-roi-00",
	day = "27",
	month = mar,
	year = "2002",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "10606",
	url.md5 = "013aee1d4c55e0cf3e3b102e951a41d0",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:09 CEST"
}

@TechReport{ draft-stewart-tsvwg-reconfuse-sctp,
	author = "Randall~R. Stewart and Peter Lei and Michael Tüxen",
	title = "{Uses of Stream Reconfiguration for SCTP}",
	type = "Internet Draft",
	number = "draft-stewart-tsvwg-reconfuse-sctp-00",
	day = "29",
	month = mar,
	year = "2011",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "18561",
	url.md5 = "a84dd9ebc2c42fb73264a0f24d9fa68b",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:55 CEST"
}

@TechReport{ draft-stewart-tsvwg-sctpecn,
	author = "Randall~R. Stewart and Michael Tüxen",
	title = "{ECN for Stream Control Transmission Protocol~(SCTP)}",
	type = "Internet Draft",
	number = "draft-stewart-tsvwg-sctpecn-07",
	day = "22",
	month = apr,
	year = "2024",
	institution = "IETF, Individual Submission",
	language = "english",
	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-07.txt",
	url.size = "27241",
	url.md5 = "b9942e7767b715a9030e139184cc9f75",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:54 CEST"
}

@TechReport{ draft-stewart-tsvwg-sctp-nonce,
	author = "Randall~R. Stewart and Neil Spring",
	title = "{ECN Nonces for Stream Control Transmission Protocol~(SCTP)}",
	type = "Internet Draft",
	number = "draft-stewart-tsvwg-sctp-nonce-02",
	day = "29",
	month = jun,
	year = "2010",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "25481",
	url.md5 = "7ac5f5ab47477f5b537691875dbfc905",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:54 CEST"
}

@TechReport{ draft-stewart-tsvwg-sctpscore,
	author = "Randall~R. Stewart and Michael Tüxen",
	title = "{Stream Control Transmission Protocol~(SCTP) Interop Scoring}",
	type = "Internet Draft",
	number = "draft-stewart-tsvwg-sctpscore-04",
	day = "19",
	month = jul,
	year = "2006",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "21427",
	url.md5 = "f19d9f9ae2b38b6ea5cabf46e351b128",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:55 CEST"
}

@TechReport{ draft-trammell-ipfix-sctp-change,
	author = "Brian~H. Trammell and Elisa Boschi",
	title = "{IP Flow Information Export~(IPFIX) SCTP Stream Restriction Change}",
	type = "Internet Draft",
	number = "draft-trammell-ipfix-sctp-change-01",
	day = "1",
	month = aug,
	year = "2007",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "20400",
	url.md5 = "774f96c585c6f8475a81006418b1f3ed",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:10 CEST"
}

@TechReport{ draft-tuexen-tsvwg-sctp-init-fwd,
	author = "Michael Tüxen and Timo Völker",
	title = "{INIT Forwarding for the Stream Control Transmission Protocol}",
	type = "Internet Draft",
	number = "draft-tuexen-tsvwg-sctp-init-fwd-05",
	day = "2",
	month = mar,
	year = "2025",
	institution = "IETF, Individual Submission",
	language = "english",
	abstract = "{The Stream Control Transmission Protocol~(SCTP) extension described in this document allows the support of a simple mechanism to distribute association requests between a cluster of SCTP end points providing the same service. In particular, this allows the use of anycast addresses in combination with SCTP.}",
	url = "https://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-init-fwd-05.txt",
	url.size = "13663",
	url.md5 = "f8a276fd871ab1423d4712cc97975bdc",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:52 CEST"
}

@TechReport{ draft-tuexen-tsvwg-sctp-multipath,
	author = "Martin Becke and Thomas Dreibholz and Nasif Ekiz and Janardhan~R. Iyengar and Preethi Natarajan and Randall~R. Stewart and Michael Tüxen",
	title = "{Load Sharing for the Stream Control Transmission Protocol~(SCTP)}",
	type = "Internet Draft",
	number = "draft-tuexen-tsvwg-sctp-multipath-32",
	day = "15",
	month = sep,
	year = "2026",
	institution = "IETF, Individual Submission",
	language = "english",
	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-32.txt",
	url.size = "61457",
	url.md5 = "71769a148fc58f36502e1b7a30189748",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:51 CEST"
}

@TechReport{ draft-tuexen-tsvwg-sctp-ppid-frag,
	author = "Michael Tüxen and Randell Jesup and Hannes Tschofenig",
	title = "{Payload Protocol Identifier based Fragmentation and Reassembly for the Stream Control Transmission Protocol}",
	type = "Internet Draft",
	number = "draft-tuexen-tsvwg-sctp-ppid-frag-03",
	day = "2",
	month = mar,
	year = "2025",
	institution = "IETF, Individual Submission",
	language = "english",
	abstract = "{This document describes a method for the Stream Control Transmission Protocol~(SCTP) allowing the upper layer to perform fragmentation, reassembly, and interleaving of large ordered user messages by using the payload protocol identifier~(PPID). According to the base specification supporting fragmentation of large user messages is optional. And even if an SCTP implementation supports fragmentation, interleaving of user messages is not supported by the base specification.}",
	url = "https://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-ppid-frag-03.txt",
	url.size = "9942",
	url.md5 = "42f56013b28d81233df937c73da9c5c2",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:04 CEST"
}

@TechReport{ draft-tuexen-tsvwg-sctp-scheduling,
	author = "Robin Seggelmann and Randall~R. Stewart and Michael Tüxen",
	title = "{Pluggable Stream Scheduling for the Stream Control Transmission Protocol}",
	type = "Internet Draft",
	number = "draft-tuexen-tsvwg-sctp-scheduling-00",
	day = "19",
	month = nov,
	year = "2012",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "10440",
	url.md5 = "330a192561319fdc4875c34afd2d8c98",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:11 CEST"
}

@TechReport{ draft-tuexen-tsvwg-sctp-udp-encaps-cons,
	author = "Michael Tüxen and Randall~R. Stewart",
	title = "{Additional Considerations for UDP Encapsulation of Stream Control Transmission Protocol~(SCTP) Packets}",
	type = "Internet Draft",
	number = "draft-tuexen-tsvwg-sctp-udp-encaps-cons-10",
	day = "7",
	month = sep,
	year = "2024",
	institution = "IETF, Individual Submission",
	language = "english",
	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-10.txt",
	url.size = "15092",
	url.md5 = "c23012fde770ab791cef964564ec707b",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:05 CEST"
}

@TechReport{ draft-vibansal-sctpsocket-congestion,
	author = "Vivek Bansal and R Ezhirpavai",
	title = "{SCTP Sockets API Extension for Congestion Handling}",
	type = "Internet Draft",
	number = "draft-vibansal-sctpsocket-congestion-00",
	day = "7",
	month = dec,
	year = "2004",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "23971",
	url.md5 = "c6d8d135f26874c86d1ebbed005c2b19",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:55 CEST"
}

@TechReport{ draft-westerlund-tsvwg-sctp-dtls-chunk,
	author = "Magnus Westerlund and John Preuß Mattsson and Claudio Porfiri and Michael Tüxen",
	title = "{Stream Control Transmission Protocol~(SCTP) DTLS Chunk}",
	type = "Internet Draft",
	number = "draft-westerlund-tsvwg-sctp-dtls-chunk-05",
	day = "7",
	month = jul,
	year = "2025",
	institution = "IETF, Individual Submission",
	language = "english",
	abstract = "{This document describes a method for adding Cryptographic protection to the Stream Control Transmission Protocol~(SCTP). The SCTP DTLS chunk defined in this document is intended to enable communications privacy for applications that use SCTP as their transport protocol and allows applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. Applications using SCTP DTLS chunk can use all transport features provided by SCTP and its extensions but with some limitations.}",
	url = "https://tools.ietf.org/id/draft-westerlund-tsvwg-sctp-dtls-chunk-05.txt",
	url.size = "82378",
	url.md5 = "852c6be1c1cbc754c4a70f275c80c9a2",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:03 CEST"
}

@TechReport{ draft-westerlund-tsvwg-sctp-dtls-handshake,
	author = "Magnus Westerlund and John Preuß Mattsson and Claudio Porfiri",
	title = "{Datagram Transport Layer Security~(DTLS) based key-management of the Stream Control Transmission Protocol~(SCTP) DTLS Chunk}",
	type = "Internet Draft",
	number = "draft-westerlund-tsvwg-sctp-dtls-handshake-05",
	day = "7",
	month = jul,
	year = "2025",
	institution = "IETF, Individual Submission",
	language = "english",
	abstract = "{This document defines a key-management solution based on Datagram Transport Layer Security 1.3~(DTLS) to protect the content of Stream Control Transmission Protocol~(SCTP) packets using the packet protection framework provided by the SCTP DTLS chunk. The combination provides encryption, source authentication, integrity and replay protection for the SCTP association with in-band DTLS based key-management and mutual authentication of the peers. The specification is enabling very long-lived sessions of weeks and months and supports mutual re-authentication and rekeying with ephemeral key exchange. The key-management solution does not require any additional defined features or implementation support beyond core DTLS 1.3. This is intended as a replacement to using DTLS/SCTP~(RFC6083) and SCTP-AUTH~(RFC4895).}",
	url = "https://tools.ietf.org/id/draft-westerlund-tsvwg-sctp-dtls-handshake-05.txt",
	url.size = "71910",
	url.md5 = "57806930e140f589e2512ade0328c8c8",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:04 CEST"
}

@TechReport{ draft-west-sctp-epic,
	author = "Mark~A. West and Abigail Surtees",
	title = "{SCTP Profile for EPIC}",
	type = "Internet Draft",
	number = "draft-west-sctp-epic-01",
	day = "27",
	month = jun,
	year = "2003",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "52719",
	url.md5 = "b90ac9bfbaae1909e64d3a0e238fb97f",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:56 CEST"
}

@TechReport{ draft-xie-behave-sctp-nat-cons,
	author = "Qiaobing Xie and Randall~R. Stewart and Matt Holdrege and Michael Tüxen",
	title = "{SCTP NAT Traversal Considerations}",
	type = "Internet Draft",
	number = "draft-xie-behave-sctp-nat-cons-03",
	day = "17",
	month = nov,
	year = "2007",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "12734",
	url.md5 = "a4c3706a220bd69b0a55af51b55972e6",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:11 CEST"
}

@TechReport{ draft-xie-tsvwg-sctp-nat,
	author = "Qiaobing Xie",
	title = "{SCTP NAT Transverse Considerations}",
	type = "Internet Draft",
	number = "draft-xie-tsvwg-sctp-nat-00",
	day = "9",
	month = jul,
	year = "2004",
	institution = "IETF, Individual Submission",
	language = "english",
	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",
	url.size = "14209",
	url.md5 = "4dfc1190359c80765e7398401acab73b",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:56 CEST"
}

@TechReport{ RFC2960,
	author = "Randall~R. Stewart and Qiaobing Xie and Ken Morneault and Chip Sharp and Hanns Jürgen Schwarzbauer and Tom Taylor and Ian Rytina and Malleswar Kalla and Lixia Zhang and Vern Paxson",
	title = "{Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "2960",
	month = oct,
	year = "2000",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC2960",
	abstract = "{This document describes the Stream Control Transmission Protocol~(SCTP).}",
	url = "https://www.rfc-editor.org/rfc/rfc2960.txt",
	url.size = "297757",
	url.md5 = "8c7ae0988fb53c647b7111bb6c9af1d4",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:26:49 CEST"
}

@TechReport{ RFC3257,
	author = "Lode Coene",
	title = "{Stream Control Transmission Protocol Applicability Statement}",
	type = "Informational RFC",
	number = "3257",
	month = apr,
	year = "2002",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3257",
	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",
	url.size = "24198",
	url.md5 = "17532fe7fca05269d94f29717536e22c",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:26:56 CEST"
}

@TechReport{ RFC3286,
	author = "Lyndon Ong and John Yoakum",
	title = "{An Introduction to the Stream Control Transmission Protocol~(SCTP)}",
	type = "Informational RFC",
	number = "3286",
	month = may,
	year = "2002",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3286",
	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",
	url.size = "22644",
	url.md5 = "3962ec32c91639aae167ee96badf6cdf",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:26:56 CEST"
}

@TechReport{ RFC3309,
	author = "Jonathan Stone and Randall~R. Stewart and Douglas Otis",
	title = "{Stream Control Transmission Protocol~(SCTP) Checksum Change}",
	type = "Standards RFC",
	number = "3309",
	month = sep,
	year = "2002",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3309",
	abstract = "{Stream Control Transmission Protocol [RFC2960]~(SCTP) currently uses an Adler-32 checksum. For small packets Adler-32 provides weak detection of errors. This document changes that checksum and updates SCTP to use a 32 bit CRC checksum.}",
	url = "https://www.rfc-editor.org/rfc/rfc3309.txt",
	url.size = "34670",
	url.md5 = "197f2ac17be990dc4ba7c6a3a90d5cc0",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:26:59 CEST"
}

@TechReport{ RFC3436,
	author = "Andreas Jungmaier and Eric Rescorla and Michael Tüxen",
	title = "{Transport Layer Security over Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "3436",
	month = dec,
	year = "2002",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3436",
	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",
	url.size = "16333",
	url.md5 = "e859fb7bbf61142eb6527425ef2cec25",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:26:59 CEST"
}

@TechReport{ RFC3554,
	author = "Steven~M. Bellovin and John Ioannidis and Angelos~D. Keromytis and Randall~R. Stewart",
	title = "{On the Use of Stream Control Transmission Protocol~(SCTP) with IPsec}",
	type = "Standards Track RFC",
	number = "3554",
	month = jul,
	year = "2003",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3554",
	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",
	url.size = "20102",
	url.md5 = "f028d5c10961516d6c892f1e462a2474",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:03 CEST"
}

@TechReport{ RFC3758,
	author = "Randall~R. Stewart and Michael~A. Ramalho and Qiaobing Xie and Michael Tüxen and Phillip~T. Conrad",
	title = "{Stream Control Transmission Protocol~(SCTP) Partial Reliability Extension}",
	type = "Standards Track RFC",
	number = "3758",
	month = may,
	year = "2004",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3758",
	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",
	url.size = "50999",
	url.md5 = "0c9d421b69393c27cfc729e606373157",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:05 CEST"
}

@TechReport{ RFC3873,
	author = "J.~Pastor and Maria-Carmen Belinchón",
	title = "{Stream Control Transmission Protocol~(SCTP) Management Information Base~(MIB)}",
	type = "Standards Track RFC",
	number = "3873",
	month = sep,
	year = "2004",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC3873",
	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",
	url.size = "82403",
	url.md5 = "0abd2ec982fcb655651024020859c50a",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:24 CEST"
}

@TechReport{ RFC4460,
	author = "Randall~R. Stewart and Iván Arias Rodríguez and Kacheong Poon and Armando~L. Caro and Michael Tüxen",
	title = "{Stream Control Transmission Protocol~(SCTP) Specification Errata and Issues}",
	type = "Informational RFC",
	number = "4460",
	month = apr,
	year = "2006",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC4460",
	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",
	url.size = "215405",
	url.md5 = "78bc6d48031bb8606f4d618fd0abed95",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:08 CEST"
}

@TechReport{ RFC4820,
	author = "Michael Tüxen and Randall~R. Stewart and Peter Lei",
	title = "{Padding Chunk and Parameter for the Stream Control Transmission Protocol~(SCTP)}",
	type = "Standards Track RFC",
	number = "4820",
	month = mar,
	year = "2007",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC4820",
	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",
	url.size = "11597",
	url.md5 = "49b9e39c784d55abbe3704522a889d26",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:32 CEST"
}

@TechReport{ RFC4895,
	author = "Michael Tüxen and Randall~R. Stewart and Peter Lei and Eric Rescorla",
	title = "{Authenticated Chunks for the Stream Control Transmission Protocol~(SCTP)}",
	type = "Standards Track RFC",
	number = "4895",
	month = aug,
	year = "2007",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC4895",
	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",
	url.size = "42507",
	url.md5 = "2b7207bc23f5bb90945d8274572238a5",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:13 CEST"
}

@TechReport{ RFC4960,
	author = "Randall~R. Stewart",
	title = "{Stream Control Transmission Protocol}",
	type = "RFC",
	number = "4960",
	month = sep,
	year = "2007",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC4960",
	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",
	url.size = "346022",
	url.md5 = "9eeb61074f2f4f6c5c88b0554ece6a4e",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:14 CEST"
}

@TechReport{ RFC5061,
	author = "Randall~R. Stewart and Qiaobing Xie and Michael Tüxen and Shin Maruyama and Masahiro Kozuka",
	title = "{Stream Control Transmission Protocol~(SCTP) Dynamic Address Reconfiguration}",
	type = "Standards Track RFC",
	number = "5061",
	month = sep,
	year = "2007",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC5061",
	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",
	url.size = "91851",
	url.md5 = "8df71e2f2521a699a26652eac3381e9b",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:19 CEST"
}

@TechReport{ RFC5062,
	author = "Randall~R. Stewart and Michael Tüxen and Gonzalo Camarillo",
	title = "{Security Attacks Found Against the Stream Control Transmission Protocol~(SCTP) and Current Countermeasures}",
	type = "Informational RFC",
	number = "5062",
	month = sep,
	year = "2007",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC5062",
	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",
	url.size = "29702",
	url.md5 = "b3feb1bb3c349fff6ffd3d23c5c71430",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:19 CEST"
}

@TechReport{ RFC6083,
	author = "Michael Tüxen and Robin Seggelmann and Eric Rescorla",
	title = "{Datagram Transport Layer Security~(DTLS) for Stream Control Transmission Protocol~(SCTP)}",
	type = "Standards Track RFC",
	number = "6083",
	month = jan,
	year = "2011",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC6083",
	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",
	url.size = "16674",
	url.md5 = "fd61d60a952f67832b30ff862bffdfec",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:42 CEST"
}

@TechReport{ RFC6096,
	author = "Michael Tüxen and Randall~R. Stewart",
	title = "{Stream Control Transmission Protocol~(SCTP) Chunk Flags Registration}",
	type = "Standards Track RFC",
	number = "6096",
	month = jan,
	year = "2011",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC6096",
	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",
	url.size = "15368",
	url.md5 = "f389ae29c46ae60428664892a5a3869b",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:42 CEST"
}

@TechReport{ RFC6458,
	author = "Randall~R. Stewart and Michael Tüxen and Kacheong Poon and Peter Lei and Vladislav Yasevich",
	title = "{Sockets API Extensions for the Stream Control Transmission Protocol~(SCTP)}",
	type = "Informational RFC",
	number = "6458",
	month = dec,
	year = "2011",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC6458",
	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",
	url.size = "237112",
	url.md5 = "61cefc730d709cb22842b791a891d6ae",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:39 CEST"
}

@TechReport{ RFC6525,
	author = "Randall~R. Stewart and Michael Tüxen and Peter Lei",
	title = "{Stream Control Transmission Protocol~(SCTP) Stream Reconfiguration}",
	type = "Standards Track RFC",
	number = "6525",
	month = feb,
	year = "2012",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC6525",
	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",
	url.size = "72734",
	url.md5 = "2830fa011c68023335a4c1860d88b0a8",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:39 CEST"
}

@TechReport{ RFC6951,
	author = "Michael Tüxen and Randall~R. Stewart",
	title = "{UDP Encapsulation of Stream Control Transmission Protocol~(SCTP) Packets for End-Host to End-Host Communication}",
	type = "Standards Track RFC",
	number = "6951",
	month = may,
	year = "2013",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC6951",
	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",
	url.size = "25676",
	url.md5 = "76d8a098f7aeeb7a20c685cd32c4846e",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:43 CEST"
}

@TechReport{ RFC7053,
	author = "Michael Tüxen and Irene Rüngeler and Randall~R. Stewart",
	title = "{SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "7053",
	month = nov,
	year = "2013",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC7053",
	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",
	url.size = "15773",
	url.md5 = "cd6ad1605e58c36d3cc56bc4cbe96891",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:43 CEST"
}

@TechReport{ RFC7496,
	author = "Michael Tüxen and Robin Seggelmann and Randall~R. Stewart and Salvatore Loreto",
	title = "{Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension}",
	type = "Standards Track RFC",
	number = "7496",
	month = apr,
	year = "2015",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC7496",
	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",
	url.size = "21272",
	url.md5 = "7fbe15c06aa1e3f4ff4876603ce88e67",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:01 CEST"
}

@TechReport{ RFC7829,
	author = "Yoshifumi Nishida and Preethi Natarajan and Armando~L. Caro and Paul~D. Amer and Karen~E.~E. Nielsen",
	title = "{SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "7829",
	month = apr,
	year = "2016",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC7829",
	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",
	url.size = "53922",
	url.md5 = "60d432c139bf20e68d6df218163bfa95",
	url.mime = "text/plain",
	url.checked = "2026-05-26 23:03:02 CEST"
}

@TechReport{ RFC7857,
	author = "Reinaldo Penno and Simon Perreault and Mohamed Boucadair and Senthil Sivakumar and Kengo Naito",
	title = "{Updates to Network Address Translation~(NAT) Behavioral Requirements}",
	type = "Best Current Practice RFC",
	number = "7857",
	month = apr,
	year = "2016",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC7857",
	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",
	url.size = "29255",
	url.md5 = "a9336f2acc5edd1ab5ec0a33499ea3f4",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:54 CEST"
}

@TechReport{ RFC8260,
	author = "Randall~R. Stewart and Michael Tüxen and Salvatore Loreto and Robin Seggelmann",
	title = "{Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "8260",
	month = nov,
	year = "2017",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC8260",
	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",
	url.size = "50887",
	url.md5 = "03c8abcd8fea90ca1c6d27aadfc8bb09",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:54 CEST"
}

@TechReport{ RFC8261,
	author = "Michael Tüxen and Randall~R. Stewart and Randell Jesup and Salvatore Loreto",
	title = "{Datagram Transport Layer Security~(DTLS) Encapsulation of SCTP Packets}",
	type = "Standards Track RFC",
	number = "8261",
	month = nov,
	year = "2017",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC8261",
	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",
	url.size = "21035",
	url.md5 = "0a4d0602366ca70c4a3f0005fd4cf3d0",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:55 CEST"
}

@TechReport{ RFC8540,
	author = "Randall~R. Stewart and Michael Tüxen and Maksim Proshin",
	title = "{Stream Control Transmission Protocol: Errata and Issues in RFC 4960}",
	type = "Informational RFC",
	number = "8540",
	month = feb,
	year = "2019",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC8540",
	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",
	url.size = "166198",
	url.md5 = "dd9ae5373c2c992b651c9c9da40b1c44",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:25:55 CEST"
}

@TechReport{ RFC9260,
	author = "Randall~R. Stewart and Michael Tüxen and Karen~E.~E. Nielsen",
	title = "{Stream Control Transmission Protocol}",
	type = "Standards Track RFC",
	number = "9260",
	month = jun,
	year = "2022",
	institution = "IETF",
	language = "english",
	issn = "2070-1721",
	doi = "10.17487/RFC9260",
	abstract = "{This document describes the Stream Control Transmission Protocol~(SCTP) and obsoletes RFC~4960. It incorporates the specification of the chunk flags registry from RFC~6096 and the specification of the I bit of DATA chunks from RFC~7053. Therefore, RFCs 6096 and 7053 are also obsoleted by this document. In addition, RFCs 4460 and 8540, which describe errata for SCTP, are obsoleted by this document.}",
	url = "https://www.rfc-editor.org/rfc/rfc9260.txt",
	url.size = "345864",
	url.md5 = "50fb17fe40b339e80fe3958a07ec4dec",
	url.mime = "text/plain",
	url.checked = "2026-09-20 12:27:14 CEST"
}