Services provided by IETF transport protocols and congestion control mechanisms
draft-ietf-taps-transports-14

Document Type Active Internet-Draft (taps WG)
Last updated 2016-12-09 (latest revision 2016-12-06)
Replaces draft-fairhurst-taps-transports
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication Nov 2016
Document shepherd Aaron Falk
Shepherd write-up Show (last changed 2016-06-17)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to "Aaron Falk" <aaron.falk@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
Network Working Group                                  G. Fairhurst, Ed.
Internet-Draft                                    University of Aberdeen
Intended status: Informational                          B. Trammell, Ed.
Expires: June 9, 2017                                 M. Kuehlewind, Ed.
                                                              ETH Zurich
                                                       December 06, 2016

  Services provided by IETF transport protocols and congestion control
                               mechanisms
                     draft-ietf-taps-transports-14

Abstract

   This document describes, surveys, and classifies the protocol
   mechanisms provided by existing IETF protocols, as background for
   determining a common set of transport services.  It examines the
   Transmission Control Protocol (TCP), Multipath TCP, the Stream
   Control Transmission Protocol (SCTP), the User Datagram Protocol
   (UDP), UDP-Lite, the Datagram Congestion Control Protocol (DCCP), the
   Internet Control Message Protocol (ICMP), the Realtime Transport
   Protocol (RTP), File Delivery over Unidirectional Transport/
   Asynchronous Layered Coding Reliable Multicast (FLUTE/ALC), and NACK-
   Oriented Reliable Multicast (NORM), Transport Layer Security (TLS),
   Datagram TLS (DTLS), and the Hypertext Transport Protocol (HTTP),
   when HTTP is used as a pseudotransport.  This survey provides
   background for the definition of transport services within the TAPS
   working group.

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 June 9, 2017.

Fairhurst, et al.         Expires June 9, 2017                  [Page 1]
Internet-Draft               TAPS Transports               December 2016

Copyright Notice

   Copyright (c) 2016 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 of Transport Features  . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Existing Transport Protocols  . . . . . . . . . . . . . . . .   6
     3.1.  Transport Control Protocol (TCP)  . . . . . . . . . . . .   6
       3.1.1.  Protocol Description  . . . . . . . . . . . . . . . .   6
       3.1.2.  Interface description . . . . . . . . . . . . . . . .   8
       3.1.3.  Transport Features  . . . . . . . . . . . . . . . . .   8
     3.2.  Multipath TCP (MPTCP) . . . . . . . . . . . . . . . . . .   9
       3.2.1.  Protocol Description  . . . . . . . . . . . . . . . .   9
       3.2.2.  Interface Description . . . . . . . . . . . . . . . .  10
       3.2.3.  Transport features  . . . . . . . . . . . . . . . . .  10
     3.3.  User Datagram Protocol (UDP)  . . . . . . . . . . . . . .  11
       3.3.1.  Protocol Description  . . . . . . . . . . . . . . . .  11
       3.3.2.  Interface Description . . . . . . . . . . . . . . . .  12
       3.3.3.  Transport Features  . . . . . . . . . . . . . . . . .  12
     3.4.  Lightweight User Datagram Protocol (UDP-Lite) . . . . . .  13
       3.4.1.  Protocol Description  . . . . . . . . . . . . . . . .  13
       3.4.2.  Interface Description . . . . . . . . . . . . . . . .  13
       3.4.3.  Transport Features  . . . . . . . . . . . . . . . . .  14
     3.5.  Stream Control Transmission Protocol (SCTP) . . . . . . .  14
       3.5.1.  Protocol Description  . . . . . . . . . . . . . . . .  14
       3.5.2.  Interface Description . . . . . . . . . . . . . . . .  16
       3.5.3.  Transport Features  . . . . . . . . . . . . . . . . .  19
Show full document text