< draft-dreibholz-tsvwg-sctp-nextgen-ideas-14.txt   draft-dreibholz-tsvwg-sctp-nextgen-ideas-15.txt >
Network Working Group T. Dreibholz Network Working Group T. Dreibholz
Internet-Draft SimulaMet Internet-Draft SimulaMet
Intended status: Informational September 06, 2021 Intended status: Informational 21 March 2022
Expires: March 10, 2022 Expires: 22 September 2022
Ideas for a Next Generation of the Stream Control Transmission Protocol Ideas for a Next Generation of the Stream Control Transmission Protocol
(SCTP) (SCTP)
draft-dreibholz-tsvwg-sctp-nextgen-ideas-14 draft-dreibholz-tsvwg-sctp-nextgen-ideas-15
Abstract Abstract
This document collects some ideas for a next generation of the Stream This document collects some ideas for a next generation of the Stream
Control Transmission Protocol (SCTP) for further discussion. It is a Control Transmission Protocol (SCTP) for further discussion. It is a
result of lessons learned from more than one decade of SCTP result of lessons learned from more than one decade of SCTP
deployment. deployment.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 10, 2022. This Internet-Draft will expire on 22 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Stream Control Transmission Protocol . . . . . . . . . . 2 1.2. Stream Control Transmission Protocol . . . . . . . . . . 2
1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. What to Change in the Next Generation of SCTP? . . . . . . . 2 2. What to Change in the Next Generation of SCTP? . . . . . . . 2
2.1. Security Considerations . . . . . . . . . . . . . . . . . 3 2.1. Security Considerations . . . . . . . . . . . . . . . . . 3
2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 3 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 2, line 26 skipping to change at page 2, line 26
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
1.1. Abbreviations 1.1. Abbreviations
o SCTP: Stream Control Transmission Protocol * SCTP: Stream Control Transmission Protocol
1.2. Stream Control Transmission Protocol 1.2. Stream Control Transmission Protocol
The Stream Control Transmission Protocol (SCTP) has been defined as The Stream Control Transmission Protocol (SCTP) has been defined as
RFCs in [1], [2], [3], [4], [5], [6], [7], [8], [10], [11], [12], RFCs in [1], [2], [3], [4], [5], [6], [7], [8], [10], [11], [12],
[13], [14], [15]. There is also a detailed introduction provided by [13], [14], [15]. There is also a detailed introduction provided by
[22] as well as lots of further information material on [19]. SCTP [22] as well as lots of further information material on [19]. SCTP
is therefore not introduced in more detail here. is therefore not introduced in more detail here.
1.3. Scope 1.3. Scope
The scope of this document is to collect some ideas of what to 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 update/change for a next generation of the SCTP protocol. It is a
result of lessons learned from more than one decade of SCTP result of lessons learned from more than one decade of SCTP
deployment (see also [22]) as well as ongoing discussions on applying deployment (see also [22]) as well as ongoing discussions on applying
SCTP for WebRTC Data Channels (as introduced in more detail in [18]). SCTP for WebRTC Data Channels (as introduced in more detail in [18]).
2. What to Change in the Next Generation of SCTP? 2. What to Change in the Next Generation of SCTP?
o Make useful extensions part of the next generation core protocol * Make useful extensions part of the next generation core protocol
itself (that is, make their implementation a MUST): itself (that is, make their implementation a MUST):
* Partial Reliablility ([4]) - Partial Reliablility ([4])
* Chunk Authentication ([6]) - Chunk Authentication ([6])
* Partial Reliablility ([8]) - Partial Reliablility ([8])
* Stream Reconfiguration ([13]) - Stream Reconfiguration ([13])
* SACK Immediately ([15]) - SACK Immediately ([15])
o Consider additional features as part of the next generation core * Consider additional features as part of the next generation core
protocol: protocol:
* Non-Renegable Selective Acknowledgments (NR-SACK) ([24]) - Non-Renegable Selective Acknowledgments (NR-SACK) ([24])
* Concurrent Multi-Path Transfer for SCTP (CMT-SCTP) ([16]) - Concurrent Multi-Path Transfer for SCTP (CMT-SCTP) ([16])
o Chunk Authentication provides integrity but not confidentiality. * Chunk Authentication provides integrity but not confidentiality.
There could be a feature for encryption as well, for example like There could be a feature for encryption as well, for example like
[17]. Having encryption directly included inside the core [17]. Having encryption directly included inside the core
transport protocol may make it easier to use (less error-prone transport protocol may make it easier to use (less error-prone
work for application developers). work for application developers).
o SCTP assigns a fixed TSN per DATA chunk. The TSN cannot be * SCTP assigns a fixed TSN per DATA chunk. The TSN cannot be
changed any more. That is, it is not possible for a middlebox to changed any more. That is, it is not possible for a middlebox to
split chunks into smaller pieces (for example, for hardware split chunks into smaller pieces (for example, for hardware
offloading). For further discussion: may it be useful to consider offloading). For further discussion: may it be useful to consider
a different behavior? a different behavior?
o Definition of path: For SCTP, a path is defined by a remote * Definition of path: For SCTP, a path is defined by a remote
destination address. [20], [21] shows that CMT-SCTP performance destination address. [20], [21] shows that CMT-SCTP performance
also depends on the local endpoint's outgoing links. Considering also depends on the local endpoint's outgoing links. Considering
each pair of local outgoing and remote incoming address as each pair of local outgoing and remote incoming address as
different path may lead to improved performance in many Internet different path may lead to improved performance in many Internet
scenarios. scenarios.
2.1. Security Considerations 2.1. Security Considerations
Security considerations for SCTP can be found in [9]. Security considerations for SCTP can be found in [9].
skipping to change at page 4, line 10 skipping to change at page 4, line 10
An Open Source simulation model for SCTP is available for OMNeT++ An Open Source simulation model for SCTP is available for OMNeT++
within the INET Framework. See [23] for the Git repository. For within the INET Framework. See [23] for the Git repository. For
documentation on the model, see [25] and [22]. This model can be documentation on the model, see [25] and [22]. This model can be
used to evaluate future ideas for SCTP. used to evaluate future ideas for SCTP.
4. Testbed Platform 4. Testbed Platform
NorNet is a large-scale and realistic Internet testbed platform with NorNet is a large-scale and realistic Internet testbed platform with
support for multi-homing. A description of and introduction to support for multi-homing. A description of and introduction to
NorNet is provided in [26], [27], [28], [29]. Further information NorNet is provided in [26], [27], [28], [29]. Further information
can be found on the project website [30] at https://www.nntb.no. can be found on the project website [30] at https://www.nntb.no
(https://www.nntb.no).
5. Acknowledgments 5. Acknowledgments
The author would like to thank Martin Becke for discussions and The author would like to thank Martin Becke for discussions and
support. support.
6. References 6. References
6.1. Normative References 6.1. Normative References
skipping to change at page 6, line 8 skipping to change at page 6, line 8
<https://www.rfc-editor.org/info/rfc6951>. <https://www.rfc-editor.org/info/rfc6951>.
[15] Tuexen, M., Ruengeler, I., and R. Stewart, "SACK- [15] Tuexen, M., Ruengeler, I., and R. Stewart, "SACK-
IMMEDIATELY Extension for the Stream Control Transmission IMMEDIATELY Extension for the Stream Control Transmission
Protocol", RFC 7053, DOI 10.17487/RFC7053, November 2013, Protocol", RFC 7053, DOI 10.17487/RFC7053, November 2013,
<https://www.rfc-editor.org/info/rfc7053>. <https://www.rfc-editor.org/info/rfc7053>.
[16] Amer, P. D., Becke, M., Dreibholz, T., Ekiz, N., Iyengar, [16] Amer, P. D., Becke, M., Dreibholz, T., Ekiz, N., Iyengar,
J., Natarajan, P., Stewart, R. R., and M. Tuexen, "Load J., Natarajan, P., Stewart, R. R., and M. Tuexen, "Load
Sharing for the Stream Control Transmission Protocol Sharing for the Stream Control Transmission Protocol
(SCTP)", draft-tuexen-tsvwg-sctp-multipath-22 (work in (SCTP)", Work in Progress, Internet-Draft, draft-tuexen-
progress), August 2021. tsvwg-sctp-multipath-23, 9 February 2022,
<https://www.ietf.org/archive/id/draft-tuexen-tsvwg-sctp-
multipath-23.txt>.
[17] Hohendorf, C., Unurkhaan, E., and T. Dreibholz, "Secure [17] Hohendorf, C., Unurkhaan, E., and T. Dreibholz, "Secure
SCTP", draft-hohendorf-secure-sctp-31 (work in progress), SCTP", Work in Progress, Internet-Draft, draft-hohendorf-
March 2021. secure-sctp-32, 6 September 2021,
<https://www.ietf.org/archive/id/draft-hohendorf-secure-
sctp-32.txt>.
[18] Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data [18] Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", draft-ietf-rtcweb-data-channel-13 (work in Channels", Work in Progress, Internet-Draft, draft-ietf-
progress), January 2015. rtcweb-data-channel-13, 4 January 2015,
<https://www.ietf.org/archive/id/draft-ietf-rtcweb-data-
channel-13.txt>.
6.2. Informative References 6.2. Informative References
[19] Dreibholz, T., "Thomas Dreibholz's SCTP Page", [19] Dreibholz, T., "Thomas Dreibholz's SCTP Page", 2022,
Online: https://www.uni-due.de/~be0001/sctp/, 2019,
<https://www.uni-due.de/~be0001/sctp/>. <https://www.uni-due.de/~be0001/sctp/>.
[20] Becke, M., Adhari, H., Rathgeb, E., Fu, F., Yang, X., and [20] Becke, M., Adhari, H., Rathgeb, E. P., Fu, F., Yang, X.,
X. Zhou, "Comparison of Multipath TCP and CMT-SCTP based and X. Zhou, "Comparison of Multipath TCP and CMT-SCTP
on Intercontinental Measurements", Proceedings of the based on Intercontinental Measurements", Proceedings of
IEEE Global Communications Conference (GLOBECOM), December the IEEE Global Communications Conference (GLOBECOM), 10
2013, <https://www.wiwi.uni-due.de/fileadmin/fileupload/I- December 2013, <https://www.wiwi.uni-
TDR/Forschung/GLOBECOM2013.pdf>. due.de/fileadmin/fileupload/I-TDR/Forschung/
GLOBECOM2013.pdf>.
[21] Adhari, H., "Practical Experiences with an Inter- [21] Adhari, H., "Practical Experiences with an Inter-
Continental Testbed for Multi-Path Continental Testbed for Multi-Path
Transport", Proceedings of the 1st International NorNet Transport", Proceedings of the 1st International NorNet
Users Workshop (NNUW-1), September 2013, <https://web.arch Users Workshop (NNUW-1), 18 September 2013, <https://web.a
ive.org/web/20141127063815/https://simula.no/publications/ rchive.org/web/20141127063815/https://simula.no/
Simula.simula.2144/simula_pdf_file>. publications/Simula.simula.2144/simula_pdf_file>.
[22] Dreibholz, T., "Evaluation and Optimisation of Multi-Path [22] Dreibholz, T., "Evaluation and Optimisation of Multi-Path
Transport using the Stream Control Transmission Transport using the Stream Control Transmission
Protocol", Habilitation Treatise, March 2012, Protocol", Habilitation Treatise, 13 March 2012,
<https://duepublico.uni-duisburg- <https://duepublico.uni-duisburg-
essen.de/servlets/DerivateServlet/Derivate-29737/ essen.de/servlets/DerivateServlet/Derivate-29737/
Dre2012_final.pdf>. Dre2012_final.pdf>.
[23] Varga, A., "INET Framework for OMNeT++", 2014, [23] Varga, A., "INET Framework for OMNeT++", 2014,
<http://inet.omnetpp.org/>. <http://inet.omnetpp.org/>.
[24] Natarajan, P., Ekiz, N., Yilmaz, E., Amer, P., and J. [24] Natarajan, P., Ekiz, N., Yilmaz, E., Amer, P. D., and
Iyengar, "Non-Renegable Selective Acknowledgments (NR- J. R. Iyengar, "Non-Renegable Selective Acknowledgments
SACKs) for SCTP", Proceedings of the 16th IEEE (NR-SACKs) for SCTP", Proceedings of the 16th IEEE
International Conference on Network Protocols (ICNP) Pages International Conference on Network Protocols (ICNP) Pages
187-196, ISBN 978-1-4244-2506-8, 187-196, ISBN 978-1-4244-2506-8,
DOI 10.1109/ICNP.2008.4697037, October 2008, DOI 10.1109/ICNP.2008.4697037, October 2008,
<http://www.eecis.udel.edu/~amer/PEL/poc/pdf/ <http://www.eecis.udel.edu/~amer/PEL/poc/pdf/
ICNP2008-natarajanNonRenegableSacks.pdf>. ICNP2008-natarajanNonRenegableSacks.pdf>.
[25] Ruengeler, I., "SCTP - Evaluating, Improving and Extending [25] Rüngeler, I., "SCTP – Evaluating, Improving and Extending
the Protocol for Broader Deployment", December 2009, the Protocol for Broader Deployment", December 2009,
<http://duepublico.uni-duisburg- <http://duepublico.uni-duisburg-
essen.de/servlets/DerivateServlet/Derivate-23465/ essen.de/servlets/DerivateServlet/Derivate-23465/
Diss.pdf>. Diss.pdf>.
[26] Gran, E., Dreibholz, T., and A. Kvalbein, "NorNet Core - A [26] Gran, E. G., Dreibholz, T., and A. Kvalbein, "NorNet Core
Multi-Homed Research Testbed", Computer Networks, Special A Multi-Homed Research Testbed", Computer Networks,
Issue on Future Internet Testbeds Volume 61, Pages 75-87, Special Issue on Future Internet Testbeds Volume 61, Pages
ISSN 1389-1286, DOI 10.1016/j.bjp.2013.12.035, March 2014, 75-87, ISSN 1389-1286, DOI 10.1016/j.bjp.2013.12.035, 14
March 2014,
<https://www.simula.no/file/simulasimula2236pdf/download>. <https://www.simula.no/file/simulasimula2236pdf/download>.
[27] Dreibholz, T. and E. Gran, "Design and Implementation of [27] Dreibholz, T. and E. G. Gran, "Design and Implementation
the NorNet Core Research Testbed for Multi-Homed Systems", of the NorNet Core Research Testbed for Multi-Homed
Proceedings of the 3nd International Workshop on Protocols Systems", Proceedings of the 3nd International Workshop on
and Applications with Multi-Homing Support (PAMS) Pages Protocols and Applications with Multi-Homing
1094-1100, ISBN 978-0-7695-4952-1, Support (PAMS) Pages 1094-1100, ISBN 978-0-7695-4952-1,
DOI 10.1109/WAINA.2013.71, March 2013, DOI 10.1109/WAINA.2013.71, 27 March 2013,
<https://www.simula.no/file/ <https://www.simula.no/file/
threfereedinproceedingsreference2012-12-207643198512pdf/ threfereedinproceedingsreference2012-12-207643198512pdf/
download>. download>.
[28] Dreibholz, T., "The NorNet Core Testbed - Introduction and [28] Dreibholz, T., "The NorNet Core Testbed Introduction and
Status", Proceedings of the 1st International NorNet Status", Proceedings of the 1st International NorNet
Users Workshop (NNUW-1), September 2013, Users Workshop (NNUW-1), 18 September 2013,
<https://www.simula.no/file/simulasimula2124pdf/download>. <https://www.simula.no/file/simulasimula2124pdf/download>.
[29] Dreibholz, T., "The NorNet Core Testbed - An Experiment [29] Dreibholz, T., "The NorNet Core Testbed An Experiment
Tutorial", Proceedings of the 1st International NorNet Tutorial", Proceedings of the 1st International NorNet
Users Workshop (NNUW-1), September 2013, Users Workshop (NNUW-1), 19 September 2013,
<https://www.simula.no/file/simulasimula2130pdf/download>. <https://www.simula.no/file/simulasimula2130pdf/download>.
[30] Dreibholz, T., "NorNet - A Real-World, Large-Scale Multi- [30] Dreibholz, T., "NorNet A Real-World, Large-Scale Multi-
Homing Testbed", Online: https://www.nntb.no/, 2019, Homing Testbed", 2022, <https://www.nntb.no/>.
<https://www.nntb.no/>.
Author's Address Author's Address
Thomas Dreibholz Thomas Dreibholz
Simula Metropolitan Centre for Digital Engineering Simula Metropolitan Centre for Digital Engineering
Pilestredet 52 Pilestredet 52
0167 Oslo, Oslo 0167 Oslo
Norway Norway
Phone: +47-6782-8200
Fax: +47-6782-8201
Email: dreibh@simula.no Email: dreibh@simula.no
URI: https://www.simula.no/people/dreibh URI: https://www.simula.no/people/dreibh
 End of changes. 36 change blocks. 
70 lines changed or deleted 73 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/