| Internet-Draft | SCTP Next Generation Ideas | March 2024 |
| Dreibholz | Expires 1 October 2024 | [Page] |
This document collects some ideas for a next generation of the Stream Control Transmission Protocol (SCTP) for further discussion. It is a result of lessons learned from more than one decade of SCTP deployment.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 1 October 2024.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Stream Control Transmission Protocol (SCTP) has been defined as RFCs in [1], [2], [3], [4], [5], [6], [7], [8], [10], [11], [12], [13], [14], [15]. There is also a detailed introduction provided by [22] as well as lots of further information material on [19]. SCTP is therefore not introduced in more detail here.¶
The scope of this document is to collect some ideas of what to update/change for a next generation of the SCTP protocol. It is a result of lessons learned from more than one decade of SCTP deployment (see also [22]) as well as ongoing discussions on applying SCTP for WebRTC Data Channels (as introduced in more detail in [18]).¶
Make useful extensions part of the next generation core protocol itself (that is, make their implementation a MUST):¶
Consider additional features as part of the next generation core protocol:¶
This document introduces no additional considerations for IANA.¶
An Open Source simulation model for SCTP is available for OMNeT++ within the INET Framework. See [23] for the Git repository. For documentation on the model, see [25] and [22]. This model can be used to evaluate future ideas for SCTP.¶
NorNet is a large-scale and realistic Internet testbed platform with support for multi-homing. A description of and introduction to NorNet is provided in [26], [27], [28], [29]. Further information can be found on the project website [30] at https://www.nntb.no.¶
The author would like to thank Martin Becke for discussions and support.¶