idnits 2.17.1 draft-dreibholz-tsvwg-sctpsocket-sqinfo-24.txt: -(5): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(266): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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: ---------------------------------------------------------------------------- == There are 8 instances of lines with non-ascii characters in the document. 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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (21 March 2022) is 761 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4960 (ref. '3') (Obsoleted by RFC 9260) == Outdated reference: A later version (-27) exists of draft-tuexen-tsvwg-sctp-multipath-23 == Outdated reference: A later version (-28) exists of draft-dreibholz-tsvwg-sctpsocket-multipath-23 Summary: 1 error (**), 0 flaws (~~), 5 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: Experimental R. Seggelmann 5 Expires: 22 September 2022 Münster Univ. of App. Sciences 6 M. Becke 7 HAW Hamburg 8 21 March 2022 10 Sender Queue Info Option for the SCTP Socket API 11 draft-dreibholz-tsvwg-sctpsocket-sqinfo-24 13 Abstract 15 This document describes an extension to the SCTP sockets API for 16 querying information about the sender queue. 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 22 September 2022. 35 Copyright Notice 37 Copyright (c) 2022 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 (https://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Revised BSD License text as 46 described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Revised BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 3. Sender Queue Info (SCTP_SQINFO) . . . . . . . . . . . . . . . 2 54 4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 3 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 57 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 58 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 60 8.2. Informative References . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 63 1. Introduction 65 This draft describes an extension to the SCTP sockets API (see [4], 66 [6] [3]) which allows an application to query the sender queue 67 utilization per stream. This information is necessary for 68 applications to make efficient use of a mapping of streams to 69 dissimilar paths. A detailed description including simulation 70 results can be found in [7]. 72 In particular, this API extension is useful when using the CMT-SCTP, 73 CMT/RPv1-SCTP, CMT/RPv2-SCTP and MPTCP-like extensions (see [5], 74 [13], [12], [9], [10], [11], [8]) for Concurrent Multipath Transfer 75 (CMT) with SCTP. 77 2. Conventions 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 81 "OPTIONAL" in this document are to be interpreted as described in BCP 82 14 [1] [2] when, and only when, they appear in all capitals, as shown 83 here. 85 3. Sender Queue Info (SCTP_SQINFO) 87 This socket option obtains the maximum sender queue size (in bytes), 88 the current total sender queue utilization (in bytes) as well as the 89 current utilization per stream (in bytes). 91 The following structure is used to obtain the sender queue 92 information: 94 struct sctp_sndqueueinfo { 95 sctp_assoc_t sq_assoc_id; 96 uint32_t sq_queue_limit; 97 uint32_t sq_total_queued; 98 uint32_t sq_number_of_streams; 99 uint32_t sq_queued_on_stream[]; 100 }; 102 sq_assoc_id: This parameter is ignored for one-to-one style sockets. 103 For one-to-many style sockets this parameter indicates which 104 association the user is performing an action upon. It is an error 105 to use SCTP_{CURRENT|ALL}_ASSOC in sq_assoc_id. 107 sq_queue_limit: This field gives the maximum sender queue size in 108 bytes. 110 sq_total_queued: This field gives the current total sender queue 111 utilization in bytes. 113 sq_number_of_streams: This field gives the number of outgoing 114 streams. That is, it will contain the number of valid 115 sq_queued_on_stream entries. 117 sq_queued_on_stream: This array gives the current number of bytes 118 queued for the streams 0 to sq_number_of_streams-1. 120 Note, that the caller of getsockopt() MUST provide a 121 sctp_sndqueueinfo structure which can hold at least as many 122 sq_queued_on_stream entries as the association's number of outgoing 123 streams. Otherwise, the getsockopt() call will fail and return an 124 error. 126 4. Testbed Platform 128 A large-scale and realistic Internet testbed platform with support 129 for the multi-homing feature of the underlying SCTP protocol is 130 NorNet. A description of NorNet is provided in [14], [15], some 131 further information can be found on the project website [16]. 133 5. Security Considerations 135 Security considerations for the SCTP sockets API are described by 136 [4]. 138 6. IANA Considerations 140 This document does not require IANA actions. 142 7. Acknowledgments 144 The authors would like to thank Michael Tuexen and Irene Ruengeler 145 for their support. 147 8. References 149 8.1. Normative References 151 [1] Bradner, S., "Key words for use in RFCs to Indicate 152 Requirement Levels", BCP 14, RFC 2119, 153 DOI 10.17487/RFC2119, March 1997, 154 . 156 [2] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 157 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 158 May 2017, . 160 [3] Stewart, R., Ed., "Stream Control Transmission Protocol", 161 RFC 4960, DOI 10.17487/RFC4960, September 2007, 162 . 164 [4] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. 165 Yasevich, "Sockets API Extensions for the Stream Control 166 Transmission Protocol (SCTP)", RFC 6458, 167 DOI 10.17487/RFC6458, December 2011, 168 . 170 [5] Amer, P. D., Becke, M., Dreibholz, T., Ekiz, N., Iyengar, 171 J., Natarajan, P., Stewart, R. R., and M. Tuexen, "Load 172 Sharing for the Stream Control Transmission Protocol 173 (SCTP)", Work in Progress, Internet-Draft, draft-tuexen- 174 tsvwg-sctp-multipath-23, 9 February 2022, 175 . 178 [6] Dreibholz, T., Becke, M., and H. Adhari, "SCTP Socket API 179 Extensions for Concurrent Multipath Transfer", Work in 180 Progress, Internet-Draft, draft-dreibholz-tsvwg- 181 sctpsocket-multipath-23, 6 September 2021, 182 . 185 8.2. Informative References 187 [7] Dreibholz, T., Seggelmann, R., Tüxen, M., and E. P. 188 Rathgeb, "Transmission Scheduling Optimizations for 189 Concurrent Multipath Transfer", Proceedings of the 8th 190 International Workshop on Protocols for Future, Large- 191 Scale and Diverse Network Transports (PFLDNeT) Volume 8, 192 ISSN 2074-5168, 29 November 2010, . 196 [8] Dreibholz, T., Becke, M., Rathgeb, E. P., and M. Tüxen, 197 "On the Use of Concurrent Multipath Transfer over 198 Asymmetric Paths", Proceedings of the IEEE Global 199 Communications 200 Conference (GLOBECOM) ISBN 978-1-4244-5637-6, 201 DOI 10.1109/GLOCOM.2010.5683579, 7 December 2010, 202 . 205 [9] Adhari, H., Dreibholz, T., Becke, M., Rathgeb, E. P., and 206 M. Tüxen, "Evaluation of Concurrent Multipath Transfer 207 over Dissimilar Paths", Proceedings of the 1st 208 International Workshop on Protocols and Applications with 209 Multi-Homing Support (PAMS) Pages 708-714, 210 ISBN 978-0-7695-4338-3, DOI 10.1109/WAINA.2011.92, 22 211 March 2011, . 215 [10] Dreibholz, T., Becke, M., Adhari, H., and E. P. Rathgeb, 216 "On the Impact of Congestion Control for Concurrent 217 Multipath Transfer on the Transport Layer", Proceedings of 218 the 11th IEEE International Conference on 219 Telecommunications (ConTEL) Pages 397-404, 220 ISBN 978-953-184-152-8, 16 June 2011, 221 . 224 [11] Dreibholz, T., Becke, M., Adhari, H., and E. P. Rathgeb, 225 "Evaluation of A New Multipath Congestion Control Scheme 226 using the NetPerfMeter Tool-Chain", Proceedings of the 227 19th IEEE International Conference on Software, 228 Telecommunications and Computer Networks (SoftCOM) Pages 229 1-6, ISBN 978-953-290-027-9, 16 September 2011, 230 . 233 [12] Dreibholz, T., Adhari, H., Becke, M., and E. P. Rathgeb, 234 "Simulation and Experimental Evaluation of Multipath 235 Congestion Control Strategies", Proceedings of the 2nd 236 International Workshop on Protocols and Applications with 237 Multi-Homing Support (PAMS) ISBN 978-0-7695-4652-0, 238 DOI 10.1109/WAINA.2012.186, 29 March 2012, 239 . 242 [13] Dreibholz, T., "Evaluation and Optimisation of Multi-Path 243 Transport using the Stream Control Transmission 244 Protocol", Habilitation Treatise, 13 March 2012, 245 . 249 [14] Dreibholz, T. and E. G. Gran, "Design and Implementation 250 of the NorNet Core Research Testbed for Multi-Homed 251 Systems", Proceedings of the 3nd International Workshop on 252 Protocols and Applications with Multi-Homing 253 Support (PAMS) Pages 1094-1100, ISBN 978-0-7695-4952-1, 254 DOI 10.1109/WAINA.2013.71, 27 March 2013, 255 . 259 [15] Gran, E. G., Dreibholz, T., and A. Kvalbein, "NorNet Core 260 – A Multi-Homed Research Testbed", Computer Networks, 261 Special Issue on Future Internet Testbeds Volume 61, Pages 262 75-87, ISSN 1389-1286, DOI 10.1016/j.bjp.2013.12.035, 14 263 March 2014, 264 . 266 [16] Dreibholz, T., "NorNet – A Real-World, Large-Scale Multi- 267 Homing Testbed", 2022, . 269 Authors' Addresses 271 Thomas Dreibholz 272 Simula Metropolitan Centre for Digital Engineering 273 Pilestredet 52 274 0167 Oslo 275 Norway 276 Email: dreibh@simula.no 277 URI: https://www.simula.no/people/dreibh 279 Robin Seggelmann 280 Münster University of Applied Sciences 281 Stegerwaldstraße 39 282 48565 Steinfurt 283 Germany 284 Email: seggelmann@fh-muenster.de 285 Martin Becke 286 HAW Hamburg, Informatics Department 287 Berliner Tor 7 288 20099 Hamburg 289 Germany 290 Phone: +49-40-42875-8104 291 Email: martin.becke@haw-hamburg.de 292 URI: http://www.scimbe.de/about.html