Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol
draft-ietf-tsvwg-sctp-ndata-03

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2015-03-09
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         R. Stewart
Internet-Draft                                             Netflix, Inc.
Intended status: Standards Track                               M. Tuexen
Expires: September 10, 2015             Muenster Univ. of Appl. Sciences
                                                               S. Loreto
                                                                Ericsson
                                                           R. Seggelmann
                                            T-Systems International GmbH
                                                           March 9, 2015

 Stream Schedulers and User Message Interleaving for the Stream Control
                         Transmission Protocol
                   draft-ietf-tsvwg-sctp-ndata-03.txt

Abstract

   The Stream Control Transmission Protocol (SCTP) is a message oriented
   transport protocol supporting arbitrary large user messages.
   However, the sender can not interleave different user messages which
   causes head of line blocking at the sender side.  To overcome this
   limitation, this document adds a new data chunk to SCTP.

   Whenever an SCTP sender is allowed to send a user data, it can
   possibly choose from multiple outgoing SCTP streams.  Multiple ways
   for this selection, called stream schedulers, are defined.  Some of
   them don't require the support of user message interleaving, some do.

Status of This Memo

   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 http://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 September 10, 2015.

Stewart, et al.        Expires September 10, 2015               [Page 1]
Internet-Draft   Stream Schedulers and the I-DATA Chunk       March 2015

Copyright Notice

   Copyright (c) 2015 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
   (http://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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  User Message Interleaving . . . . . . . . . . . . . . . . . .   4
     2.1.  The I-DATA Chunk supporting User Message Interleaving . .   4
     2.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Negotiation . . . . . . . . . . . . . . . . . . . . .   5
       2.2.2.  Sender Side Considerations  . . . . . . . . . . . . .   6
       2.2.3.  Receiver Side Considerations  . . . . . . . . . . . .   6
     2.3.  Interaction with other SCTP Extensions  . . . . . . . . .   6
       2.3.1.  SCTP Partial Reliability Extension  . . . . . . . . .   7
       2.3.2.  SCTP Stream Reconfiguration Extension . . . . . . . .   7
   3.  Stream Schedulers . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Stream Scheduler without User Message Interleaving
           Support . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Stream Scheduler with User Message Interleaving Support .   7
   4.  Socket API Considerations . . . . . . . . . . . . . . . . . .   7
     4.1.  SCTP_ASSOC_CHANGE Notification  . . . . . . . . . . . . .   7
     4.2.  Socket Options  . . . . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Enable or Disable the Support of User Message
               Interleaving  . . . . . . . . . . . . . . . . . . . .   8
       4.2.2.  Get or Set the Stream Scheduler (SCTP_PLUGGABLE_SS) .   9
       4.2.3.  Get or Set the Stream Scheduler Parameter
               (SCTP_SS_VALUE) . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text