An Architecture for Transport Services
draft-ietf-taps-arch-04

Document Type Active Internet-Draft (taps WG)
Last updated 2019-07-08
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
TAPS Working Group                                         T. Pauly, Ed.
Internet-Draft                                                Apple Inc.
Intended status: Standards Track                        B. Trammell, Ed.
Expires: January 9, 2020                                          Google
                                                            A. Brunstrom
                                                     Karlstad University
                                                            G. Fairhurst
                                                  University of Aberdeen
                                                              C. Perkins
                                                   University of Glasgow
                                                               P. Tiesel
                                                               TU Berlin
                                                                 C. Wood
                                                              Apple Inc.
                                                           July 08, 2019

                 An Architecture for Transport Services
                        draft-ietf-taps-arch-04

Abstract

   This document provides an overview of the architecture of Transport
   Services, a model for exposing transport protocol features to
   applications for network communication.  In contrast to what is
   provided by most existing Application Programming Interfaces (APIs),
   Transport Services is based on an asynchronous, event-driven
   interaction pattern; it uses messages for representing data transfer
   to applications; and it assumes an implementation that can use
   multiple IP addresses, multiple protocols, and multiple paths, and
   provide multiple application streams.  This document further defines
   the common set of terminology and concepts to be used in definitions
   of Transport Services APIs and implementations.

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."

Pauly, et al.            Expires January 9, 2020                [Page 1]
Internet-Draft              TAPS Architecture                  July 2019

   This Internet-Draft will expire on January 9, 2020.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Event-Driven API  . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Data Transfer Using Messages  . . . . . . . . . . . . . .   5
     1.4.  Flexibile Implementation  . . . . . . . . . . . . . . . .   6
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Specification of Requirements . . . . . . . . . . . . . .   7
   3.  Design Principles . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  Common APIs for Common Features . . . . . . . . . . . . .   8
     3.2.  Access to Specialized Features  . . . . . . . . . . . . .   8
     3.3.  Scope for API and Implementation Definitions  . . . . . .   9
   4.  Transport Services Architecture and Concepts  . . . . . . . .  10
     4.1.  Transport Services API Concepts . . . . . . . . . . . . .  11
       4.1.1.  Basic Objects . . . . . . . . . . . . . . . . . . . .  13
       4.1.2.  Pre-Establishment . . . . . . . . . . . . . . . . . .  14
       4.1.3.  Establishment Actions . . . . . . . . . . . . . . . .  15
       4.1.4.  Data Transfer Objects and Actions . . . . . . . . . .  16
       4.1.5.  Event Handling  . . . . . . . . . . . . . . . . . . .  16
       4.1.6.  Termination Actions . . . . . . . . . . . . . . . . .  17
     4.2.  Transport System Implementation Concepts  . . . . . . . .  17
Show full document text