Internet-Draft | Sender Queue Info Option | March 2023 |
Dreibholz, et al. | Expires 27 September 2023 | [Page] |
This document describes an extension to the SCTP sockets API for querying information about the sender queue.¶
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 27 September 2023.¶
Copyright (c) 2023 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.¶
This draft describes an extension to the SCTP sockets API (see [4], [6] [3]) which allows an application to query the sender queue utilization per stream. This information is necessary for applications to make efficient use of a mapping of streams to dissimilar paths. A detailed description including simulation results can be found in [7].¶
In particular, this API extension is useful when using the CMT-SCTP, CMT/RPv1-SCTP, CMT/RPv2-SCTP and MPTCP-like extensions (see [5], [13], [12], [9], [10], [11], [8]) for Concurrent Multipath Transfer (CMT) with SCTP.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [1] [2] when, and only when, they appear in all capitals, as shown here.¶
This socket option obtains the maximum sender queue size (in bytes), the current total sender queue utilization (in bytes) as well as the current utilization per stream (in bytes).¶
The following structure is used to obtain the sender queue information:¶
struct sctp_sndqueueinfo { sctp_assoc_t sq_assoc_id; uint32_t sq_queue_limit; uint32_t sq_total_queued; uint32_t sq_number_of_streams; uint32_t sq_queued_on_stream[]; };¶
Note, that the caller of getsockopt() MUST provide a sctp_sndqueueinfo structure which can hold at least as many sq_queued_on_stream entries as the association's number of outgoing streams. Otherwise, the getsockopt() call will fail and return an error.¶
A large-scale and realistic Internet testbed platform with support for the multi-homing feature of the underlying SCTP protocol is NorNet. A description of NorNet is provided in [14], [15], some further information can be found on the project website [16].¶
Security considerations for the SCTP sockets API are described by [4].¶
This document does not require IANA actions.¶
The authors would like to thank Michael Tuexen and Irene Ruengeler for their support.¶