A Minimal Set of Transport Services for TAPS Systems
draft-gjessing-taps-minset-04

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TAPS                                                         S. Gjessing
Internet-Draft                                                  M. Welzl
Intended status: Informational                        University of Oslo
Expires: September 14, 2017                               March 13, 2017

          A Minimal Set of Transport Services for TAPS Systems
                     draft-gjessing-taps-minset-04

Abstract

   This draft recommends a minimal set of IETF Transport Services
   offered by end systems supporting TAPS, and gives guidance on
   choosing among the available mechanisms and protocols.  It is based
   on the set of transport features given in the TAPS document
   draft-ietf-taps-transports-usage-03.

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 14, 2017.

Copyright Notice

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

Gjessing & Welzl       Expires September 14, 2017               [Page 1]
Internet-Draft       Minimal TAPS Transport Services          March 2017

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Step 1: Categorization -- The Superset of Transport
       Features . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  CONNECTION Related Transport Features  . . . . . . . . . .  7
     3.2.  DATA Transfer Related Transport Features . . . . . . . . . 18
       3.2.1.  Sending Data . . . . . . . . . . . . . . . . . . . . . 18
       3.2.2.  Receiving Data . . . . . . . . . . . . . . . . . . . . 20
       3.2.3.  Errors . . . . . . . . . . . . . . . . . . . . . . . . 21
   4.  Step 2: Reduction -- The Reduced Set of Transport Features . . 22
     4.1.  CONNECTION Related Transport Features  . . . . . . . . . . 23
     4.2.  DATA Transfer Related Transport Features . . . . . . . . . 24
       4.2.1.  Sending Data . . . . . . . . . . . . . . . . . . . . . 24
       4.2.2.  Receiving Data . . . . . . . . . . . . . . . . . . . . 24
       4.2.3.  Errors . . . . . . . . . . . . . . . . . . . . . . . . 24
   5.  Step 3: Discussion . . . . . . . . . . . . . . . . . . . . . . 24
     5.1.  Sending Messages, Receiving Bytes  . . . . . . . . . . . . 24
     5.2.  Stream Schedulers Without Streams  . . . . . . . . . . . . 26
     5.3.  Early Data Transmission  . . . . . . . . . . . . . . . . . 27
     5.4.  Sender Running Dry . . . . . . . . . . . . . . . . . . . . 27
     5.5.  Capacity Profile . . . . . . . . . . . . . . . . . . . . . 28
     5.6.  Security . . . . . . . . . . . . . . . . . . . . . . . . . 28
     5.7.  Packet Size  . . . . . . . . . . . . . . . . . . . . . . . 29
   6.  Step 4: Construction -- the Minimal Set of Transport
       Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     6.1.  Flow Creation, Connection and Termination  . . . . . . . . 30
     6.2.  Flow Group Configuration . . . . . . . . . . . . . . . . . 31
     6.3.  Flow Configuration . . . . . . . . . . . . . . . . . . . . 32
     6.4.  Data Transfer  . . . . . . . . . . . . . . . . . . . . . . 32
       6.4.1.  The Sender . . . . . . . . . . . . . . . . . . . . . . 32
       6.4.2.  The Receiver . . . . . . . . . . . . . . . . . . . . . 34
   7.  Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 34
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 35
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 36
Show full document text