idnits 2.17.1 draft-dreibholz-tsvwg-sctpsocket-sqinfo-01.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 (May 05, 2011) is 4732 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 4960 (Obsoleted by RFC 9260) == Outdated reference: A later version (-32) exists of draft-ietf-tsvwg-sctpsocket-29 == Outdated reference: A later version (-28) exists of draft-dreibholz-tsvwg-sctpsocket-multipath-00 == Outdated reference: A later version (-27) exists of draft-tuexen-tsvwg-sctp-multipath-01 Summary: 1 error (**), 0 flaws (~~), 4 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 University of Duisburg-Essen 4 Intended status: Experimental R. Seggelmann 5 Expires: November 6, 2011 Muenster Univ. of Applied 6 Sciences 7 M. Becke 8 University of Duisburg-Essen 9 May 05, 2011 11 Sender Queue Info Option for the SCTP Socket API 12 draft-dreibholz-tsvwg-sctpsocket-sqinfo-01.txt 14 Abstract 16 This document describes an extension to the SCTP sockets API for 17 querying information about the sender queue. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on November 6, 2011. 36 Copyright Notice 38 Copyright (c) 2011 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Sender Queue Info (SCTP_SQINFO) . . . . . . . . . . . . . . . . 3 56 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 57 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 61 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 This draft describes an extension to the SCTP sockets API (see 67 [I-D.ietf-tsvwg-sctpsocket], 68 [I-D.dreibholz-tsvwg-sctpsocket-multipath] [RFC4960]) which allows an 69 application to query the sender queue utilization per stream. This 70 information is necessary for applications to make efficient use of a 71 mapping of streams to dissimilar paths. A detailed description 72 including simulation results can be found in [PFLDNeT2010]. 74 In particular, this API extension is useful when using the CMT-SCTP, 75 CMT/RPv1-SCTP or CMT/RPv2-SCTP extension (see 76 [I-D.tuexen-tsvwg-sctp-multipath], [Globecom2010], [ConTEL2011]) for 77 Concurrent Multipath Transfer (CMT) with SCTP. 79 1.1. Conventions 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in [RFC2119]. 85 2. 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 3. Security Considerations 128 Security considerations for the SCTP sockets API are described by 129 [I-D.ietf-tsvwg-sctpsocket]. 131 4. IANA Considerations 133 This document does not require IANA actions. 135 5. Acknowledgments 137 The authors would like to thank Michael Tuexen and Irene Ruengeler 138 for their support. 140 6. References 142 6.1. Normative References 144 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 145 Requirement Levels", BCP 14, RFC 2119, March 1997. 147 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 148 RFC 4960, September 2007. 150 [I-D.ietf-tsvwg-sctpsocket] 151 Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. 152 Yasevich, "Sockets API Extensions for Stream Control 153 Transmission Protocol (SCTP)", 154 draft-ietf-tsvwg-sctpsocket-29 (work in progress), 155 April 2011. 157 [I-D.dreibholz-tsvwg-sctpsocket-multipath] 158 Dreibholz, T. and M. Becke, "SCTP Socket API Extensions 159 for Concurrent Multipath Transfer", 160 draft-dreibholz-tsvwg-sctpsocket-multipath-00 (work in 161 progress), November 2010. 163 [I-D.tuexen-tsvwg-sctp-multipath] 164 Becke, M., Dreibholz, T., Iyengar, J., Natarajan, P., and 165 M. Tuexen, "Load Sharing for the Stream Control 166 Transmission Protocol (SCTP)", 167 draft-tuexen-tsvwg-sctp-multipath-01 (work in progress), 168 December 2010. 170 6.2. Informative References 172 [PFLDNeT2010] 173 Dreibholz, T., Seggelmann, R., Tuexen, M., and E. Rathgeb, 174 "Transmission Scheduling Optimizations for Concurrent 175 Multipath Transfer", Proceedings of the 8th International 176 Workshop on Protocols for Future, Large-Scale and Diverse 177 Network Transports (PFLDNeT) , November 2010. 179 [Globecom2010] 180 Dreibholz, T., Becke, M., Rathgeb, E., and M. Tuexen, "On 181 the Use of Concurrent Multipath Transfer over Asymmetric 182 Paths", Proceedings of the IEEE Global Communications 183 Conference (GLOBECOM), December 2010. 185 [ConTEL2011] 186 Dreibholz, T., Becke, M., Adhari, H., and E. Rathgeb, "On 187 the Impact of Congestion Control for Concurrent Multipath 188 Transfer on the Transport Layer", Proceedings of the 11th 189 IEEE International Conference on 190 Telecommunications (ConTEL), April 2011. 192 Authors' Addresses 194 Thomas Dreibholz 195 University of Duisburg-Essen, Institute for Experimental Mathematics 196 Ellernstrasse 29 197 45326 Essen, Nordrhein-Westfalen 198 Germany 200 Phone: +49-201-1837637 201 Fax: +49-201-1837673 202 Email: dreibh@iem.uni-due.de 203 URI: http://www.iem.uni-due.de/~dreibh/ 205 Robin Seggelmann 206 Muenster University of Applied Sciences 207 Stegerwaldstrasse 39 208 48565 Steinfurt, Nordrhein-Westfalen 209 Germany 211 Email: seggelmann@fh-muenster.de 213 Martin Becke 214 University of Duisburg-Essen, Institute for Experimental Mathematics 215 Ellernstrasse 29 216 45326 Essen, Nordrhein-Westfalen 217 Germany 219 Phone: +49-201-183-7667 220 Fax: +49-201-183-7673 221 Email: martin.becke@uni-due.de