A Minimal Set of Transport Services for End Systems
draft-ietf-taps-minset-04

Document Type Active Internet-Draft (taps WG)
Last updated 2018-06-05
Replaces draft-gjessing-taps-minset
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
Document shepherd Theresa Enghardt
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Theresa Enghardt <theresa@inet.tu-berlin.de>
TAPS                                                            M. Welzl
Internet-Draft                                               S. Gjessing
Intended status: Informational                        University of Oslo
Expires: December 7, 2018                                   June 5, 2018

          A Minimal Set of Transport Services for End Systems
                       draft-ietf-taps-minset-04

Abstract

   This draft recommends a minimal set of Transport Services offered by
   end systems, and gives guidance on choosing among the available
   mechanisms and protocols.  It is based on the set of transport
   features in RFC 8303.

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 December 7, 2018.

Copyright Notice

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

Welzl & Gjessing        Expires December 7, 2018                [Page 1]
Internet-Draft         Minimal Transport Services              June 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  The Minimal Set of Transport Features . . . . . . . . . . . .   5
     3.1.  ESTABLISHMENT, AVAILABILITY and TERMINATION . . . . . . .   5
     3.2.  MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  Connection groups . . . . . . . . . . . . . . . . . .   8
       3.2.2.  Individual connections  . . . . . . . . . . . . . . .  10
     3.3.  DATA Transfer . . . . . . . . . . . . . . . . . . . . . .  10
       3.3.1.  Sending Data  . . . . . . . . . . . . . . . . . . . .  10
       3.3.2.  Receiving Data  . . . . . . . . . . . . . . . . . . .  11
   4.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Deriving the minimal set . . . . . . . . . . . . . .  15
     A.1.  Step 1: Categorization -- The Superset of Transport
           Features  . . . . . . . . . . . . . . . . . . . . . . . .  15
       A.1.1.  CONNECTION Related Transport Features . . . . . . . .  17
       A.1.2.  DATA Transfer Related Transport Features  . . . . . .  32
     A.2.  Step 2: Reduction -- The Reduced Set of Transport
           Features  . . . . . . . . . . . . . . . . . . . . . . . .  37
       A.2.1.  CONNECTION Related Transport Features . . . . . . . .  38
       A.2.2.  DATA Transfer Related Transport Features  . . . . . .  39
     A.3.  Step 3: Discussion  . . . . . . . . . . . . . . . . . . .  40
       A.3.1.  Sending Messages, Receiving Bytes . . . . . . . . . .  40
       A.3.2.  Stream Schedulers Without Streams . . . . . . . . . .  41
       A.3.3.  Early Data Transmission . . . . . . . . . . . . . . .  42
       A.3.4.  Sender Running Dry  . . . . . . . . . . . . . . . . .  43
       A.3.5.  Capacity Profile  . . . . . . . . . . . . . . . . . .  43
       A.3.6.  Security  . . . . . . . . . . . . . . . . . . . . . .  44
       A.3.7.  Packet Size . . . . . . . . . . . . . . . . . . . . .  44
   Appendix B.  Revision information . . . . . . . . . . . . . . . .  45
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  46

1.  Introduction

   The task of a transport system is to offer transport services to its
   applications, i.e. the applications running on top of the transport
Show full document text