Ideas for a Next Generation of the Stream Control Transmission Protocol (SCTP)
draft-dreibholz-tsvwg-sctp-nextgen-ideas-12

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12

Network Working Group                                       T. Dreibholz
Internet-Draft                                                 SimulaMet
Intended status: Informational                        September 09, 2020
Expires: March 13, 2021

Ideas for a Next Generation of the Stream Control Transmission Protocol
                                 (SCTP)
              draft-dreibholz-tsvwg-sctp-nextgen-ideas-12

Abstract

   This document collects some ideas for a next generation of the Stream
   Control Transmission Protocol (SCTP) for further discussion.  It is a
   result of lessons learned from more than one decade of SCTP
   deployment.

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 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 March 13, 2021.

Copyright Notice

   Copyright (c) 2020 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 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.

Dreibholz                Expires March 13, 2021                 [Page 1]
Internet-Draft         SCTP Next Generation Ideas         September 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Stream Control Transmission Protocol  . . . . . . . . . .   2
     1.3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  What to Change in the Next Generation of SCTP?  . . . . . . .   2
     2.1.  Security Considerations . . . . . . . . . . . . . . . . .   3
     2.2.  IANA Considerations . . . . . . . . . . . . . . . . . . .   3
   3.  Experimental Implementations  . . . . . . . . . . . . . . . .   3
   4.  Testbed Platform  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

1.1.  Abbreviations

   o  SCTP: Stream Control Transmission Protocol

1.2.  Stream Control Transmission Protocol

   The Stream Control Transmission Protocol (SCTP) has been defined as
   RFCs in [1], [2], [3], [4], [5], [6], [7], [8], [10], [11], [12],
   [13], [14], [15].  There is also a detailed introduction provided by
   [22] as well as lots of further information material on [19].  SCTP
   is therefore not introduced in more detail here.

1.3.  Scope

   The scope of this document is to collect some ideas of what to
   update/change for a next generation of the SCTP protocol.  It is a
   result of lessons learned from more than one decade of SCTP
   deployment (see also [22]) as well as ongoing discussions on applying
   SCTP for WebRTC Data Channels (as introduced in more detail in [18]).

2.  What to Change in the Next Generation of SCTP?

   o  Make useful extensions part of the next generation core protocol
      itself (that is, make their implementation a MUST):

      *  Partial Reliablility ([4])

      *  Chunk Authentication ([6])

Dreibholz                Expires March 13, 2021                 [Page 2]
Internet-Draft         SCTP Next Generation Ideas         September 2020

      *  Partial Reliablility ([8])

      *  Stream Reconfiguration ([13])

      *  SACK Immediately ([15])

   o  Consider additional features as part of the next generation core
      protocol:

      *  Non-Renegable Selective Acknowledgments (NR-SACK) ([24])

      *  Concurrent Multi-Path Transfer for SCTP (CMT-SCTP) ([16])

   o  Chunk Authentication provides integrity but not confidentiality.
      There could be a feature for encryption as well, for example like
      [17].  Having encryption directly included inside the core