idnits 2.17.1 draft-dreibholz-tsvwg-sctp-nextgen-ideas-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 13, 2020) is 1476 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4960 (ref. '7') (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 6096 (ref. '11') (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 7053 (ref. '15') (Obsoleted by RFC 9260) == Outdated reference: A later version (-27) exists of draft-tuexen-tsvwg-sctp-multipath-19 == Outdated reference: A later version (-36) exists of draft-hohendorf-secure-sctp-28 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Dreibholz 3 Internet-Draft SimulaMet 4 Intended status: Informational March 13, 2020 5 Expires: September 14, 2020 7 Ideas for a Next Generation of the Stream Control Transmission Protocol 8 (SCTP) 9 draft-dreibholz-tsvwg-sctp-nextgen-ideas-11 11 Abstract 13 This document collects some ideas for a next generation of the Stream 14 Control Transmission Protocol (SCTP) for further discussion. It is a 15 result of lessons learned from more than one decade of SCTP 16 deployment. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 14, 2020. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2 54 1.2. Stream Control Transmission Protocol . . . . . . . . . . 2 55 1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. What to Change in the Next Generation of SCTP? . . . . . . . 2 57 2.1. Security Considerations . . . . . . . . . . . . . . . . . 3 58 2.2. IANA Considerations . . . . . . . . . . . . . . . . . . . 3 59 3. Experimental Implementations . . . . . . . . . . . . . . . . 3 60 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4 61 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 6 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 67 1. Introduction 69 1.1. Abbreviations 71 o SCTP: Stream Control Transmission Protocol 73 1.2. Stream Control Transmission Protocol 75 The Stream Control Transmission Protocol (SCTP) has been defined as 76 RFCs in [1], [2], [3], [4], [5], [6], [7], [8], [10], [11], [12], 77 [13], [14], [15]. There is also a detailed introduction provided by 78 [22] as well as lots of further information material on [19]. SCTP 79 is therefore not introduced in more detail here. 81 1.3. Scope 83 The scope of this document is to collect some ideas of what to 84 update/change for a next generation of the SCTP protocol. It is a 85 result of lessons learned from more than one decade of SCTP 86 deployment (see also [22]) as well as ongoing discussions on applying 87 SCTP for WebRTC Data Channels (as introduced in more detail in [18]). 89 2. What to Change in the Next Generation of SCTP? 91 o Make useful extensions part of the next generation core protocol 92 itself (that is, make their implementation a MUST): 94 * Partial Reliablility ([4]) 96 * Chunk Authentication ([6]) 97 * Partial Reliablility ([8]) 99 * Stream Reconfiguration ([13]) 101 * SACK Immediately ([15]) 103 o Consider additional features as part of the next generation core 104 protocol: 106 * Non-Renegable Selective Acknowledgments (NR-SACK) ([24]) 108 * Concurrent Multi-Path Transfer for SCTP (CMT-SCTP) ([16]) 110 o Chunk Authentication provides integrity but not confidentiality. 111 There could be a feature for encryption as well, for example like 112 [17]. Having encryption directly included inside the core 113 transport protocol may make it easier to use (less error-prone 114 work for application developers). 116 o SCTP assigns a fixed TSN per DATA chunk. The TSN cannot be 117 changed any more. That is, it is not possible for a middlebox to 118 split chunks into smaller pieces (for example, for hardware 119 offloading). For further discussion: may it be useful to consider 120 a different behavior? 122 o Definition of path: For SCTP, a path is defined by a remote 123 destination address. [20], [21] shows that CMT-SCTP performance 124 also depends on the local endpoint's outgoing links. Considering 125 each pair of local outgoing and remote incoming address as 126 different path may lead to improved performance in many Internet 127 scenarios. 129 2.1. Security Considerations 131 Security considerations for SCTP can be found in [9]. 133 2.2. IANA Considerations 135 This document introduces no additional considerations for IANA. 137 3. Experimental Implementations 139 An Open Source simulation model for SCTP is available for OMNeT++ 140 within the INET Framework. See [23] for the Git repository. For 141 documentation on the model, see [25] and [22]. This model can be 142 used to evaluate future ideas for SCTP. 144 4. Testbed Platform 146 NorNet is a large-scale and realistic Internet testbed platform with 147 support for multi-homing. A description of and introduction to 148 NorNet is provided in [26], [27], [28], [29]. Further information 149 can be found on the project website [30] at https://www.nntb.no. 151 5. Acknowledgments 153 The author would like to thank Martin Becke for discussions and 154 support. 156 6. References 158 6.1. Normative References 160 [1] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., 161 Loughney, J., and M. Stillman, "Requirements for Reliable 162 Server Pooling", RFC 3237, DOI 10.17487/RFC3237, January 163 2002, . 165 [2] Jungmaier, A., Rescorla, E., and M. Tuexen, "Transport 166 Layer Security over Stream Control Transmission Protocol", 167 RFC 3436, DOI 10.17487/RFC3436, December 2002, 168 . 170 [3] Bellovin, S., Ioannidis, J., Keromytis, A., and R. 171 Stewart, "On the Use of Stream Control Transmission 172 Protocol (SCTP) with IPsec", RFC 3554, 173 DOI 10.17487/RFC3554, July 2003, 174 . 176 [4] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. 177 Conrad, "Stream Control Transmission Protocol (SCTP) 178 Partial Reliability Extension", RFC 3758, 179 DOI 10.17487/RFC3758, May 2004, 180 . 182 [5] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and 183 Parameter for the Stream Control Transmission Protocol 184 (SCTP)", RFC 4820, DOI 10.17487/RFC4820, March 2007, 185 . 187 [6] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, 188 "Authenticated Chunks for the Stream Control Transmission 189 Protocol (SCTP)", RFC 4895, DOI 10.17487/RFC4895, August 190 2007, . 192 [7] Stewart, R., Ed., "Stream Control Transmission Protocol", 193 RFC 4960, DOI 10.17487/RFC4960, September 2007, 194 . 196 [8] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. 197 Kozuka, "Stream Control Transmission Protocol (SCTP) 198 Dynamic Address Reconfiguration", RFC 5061, 199 DOI 10.17487/RFC5061, September 2007, 200 . 202 [9] Stillman, M., Ed., Gopal, R., Guttman, E., Sengodan, S., 203 and M. Holdrege, "Threats Introduced by Reliable Server 204 Pooling (RSerPool) and Requirements for Security in 205 Response to Threats", RFC 5355, DOI 10.17487/RFC5355, 206 September 2008, . 208 [10] Tuexen, M., Seggelmann, R., and E. Rescorla, "Datagram 209 Transport Layer Security (DTLS) for Stream Control 210 Transmission Protocol (SCTP)", RFC 6083, 211 DOI 10.17487/RFC6083, January 2011, 212 . 214 [11] Tuexen, M. and R. Stewart, "Stream Control Transmission 215 Protocol (SCTP) Chunk Flags Registration", RFC 6096, 216 DOI 10.17487/RFC6096, January 2011, 217 . 219 [12] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. 220 Yasevich, "Sockets API Extensions for the Stream Control 221 Transmission Protocol (SCTP)", RFC 6458, 222 DOI 10.17487/RFC6458, December 2011, 223 . 225 [13] Stewart, R., Tuexen, M., and P. Lei, "Stream Control 226 Transmission Protocol (SCTP) Stream Reconfiguration", 227 RFC 6525, DOI 10.17487/RFC6525, February 2012, 228 . 230 [14] Tuexen, M. and R. Stewart, "UDP Encapsulation of Stream 231 Control Transmission Protocol (SCTP) Packets for End-Host 232 to End-Host Communication", RFC 6951, 233 DOI 10.17487/RFC6951, May 2013, 234 . 236 [15] Tuexen, M., Ruengeler, I., and R. Stewart, "SACK- 237 IMMEDIATELY Extension for the Stream Control Transmission 238 Protocol", RFC 7053, DOI 10.17487/RFC7053, November 2013, 239 . 241 [16] Amer, P., Becke, M., Dreibholz, T., Ekiz, N., Iyengar, J., 242 Natarajan, P., Stewart, R., and M. Tuexen, "Load Sharing 243 for the Stream Control Transmission Protocol (SCTP)", 244 draft-tuexen-tsvwg-sctp-multipath-19 (work in progress), 245 January 2020. 247 [17] Hohendorf, C., Unurkhaan, E., and T. Dreibholz, "Secure 248 SCTP", draft-hohendorf-secure-sctp-28 (work in progress), 249 September 2019. 251 [18] Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data 252 Channels", draft-ietf-rtcweb-data-channel-13 (work in 253 progress), January 2015. 255 6.2. Informative References 257 [19] Dreibholz, T., "Thomas Dreibholz's SCTP Page", 258 Online: https://www.uni-due.de/~be0001/sctp/, 2019, 259 . 261 [20] Becke, M., Adhari, H., Rathgeb, E., Fu, F., Yang, X., and 262 X. Zhou, "Comparison of Multipath TCP and CMT-SCTP based 263 on Intercontinental Measurements", Proceedings of the 264 IEEE Global Communications Conference (GLOBECOM), December 265 2013, . 268 [21] Adhari, H., "Practical Experiences with an Inter- 269 Continental Testbed for Multi-Path 270 Transport", Proceedings of the 1st International NorNet 271 Users Workshop (NNUW-1), September 2013, . 275 [22] Dreibholz, T., "Evaluation and Optimisation of Multi-Path 276 Transport using the Stream Control Transmission 277 Protocol", Habilitation Treatise, March 2012, 278 . 282 [23] Varga, A., "INET Framework for OMNeT++", 2014, 283 . 285 [24] Natarajan, P., Ekiz, N., Yilmaz, E., Amer, P., and J. 286 Iyengar, "Non-Renegable Selective Acknowledgments (NR- 287 SACKs) for SCTP", Proceedings of the 16th IEEE 288 International Conference on Network Protocols (ICNP) Pages 289 187-196, ISBN 978-1-4244-2506-8, 290 DOI 10.1109/ICNP.2008.4697037, October 2008, 291 . 294 [25] Ruengeler, I., "SCTP - Evaluating, Improving and Extending 295 the Protocol for Broader Deployment", December 2009, 296 . 300 [26] Gran, E., Dreibholz, T., and A. Kvalbein, "NorNet Core - A 301 Multi-Homed Research Testbed", Computer Networks, Special 302 Issue on Future Internet Testbeds Volume 61, Pages 75-87, 303 ISSN 1389-1286, DOI 10.1016/j.bjp.2013.12.035, March 2014, 304 . 306 [27] Dreibholz, T. and E. Gran, "Design and Implementation of 307 the NorNet Core Research Testbed for Multi-Homed Systems", 308 Proceedings of the 3nd International Workshop on Protocols 309 and Applications with Multi-Homing Support (PAMS) Pages 310 1094-1100, ISBN 978-0-7695-4952-1, 311 DOI 10.1109/WAINA.2013.71, March 2013, 312 . 316 [28] Dreibholz, T., "The NorNet Core Testbed - Introduction and 317 Status", Proceedings of the 1st International NorNet 318 Users Workshop (NNUW-1), September 2013, 319 . 321 [29] Dreibholz, T., "The NorNet Core Testbed - An Experiment 322 Tutorial", Proceedings of the 1st International NorNet 323 Users Workshop (NNUW-1), September 2013, 324 . 326 [30] Dreibholz, T., "NorNet - A Real-World, Large-Scale Multi- 327 Homing Testbed", Online: https://www.nntb.no/, 2019, 328 . 330 Author's Address 332 Thomas Dreibholz 333 Simula Metropolitan Centre for Digital Engineering 334 Pilestredet 52 335 0167 Oslo, Oslo 336 Norway 338 Phone: +47-6782-8200 339 Fax: +47-6782-8201 340 Email: dreibh@simula.no 341 URI: https://www.simula.no/people/dreibh