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

Document Type Active Internet-Draft (taps WG)
Last updated 2020-07-13
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call
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: 14 January 2021                         Google Switzerland GmbH
                                                            A. Brunstrom
                                                     Karlstad University
                                                            G. Fairhurst
                                                  University of Aberdeen
                                                              C. Perkins
                                                   University of Glasgow
                                                               P. Tiesel
                                                               TU Berlin
                                                               C.A. Wood
                                                              Cloudflare
                                                            13 July 2020

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

Abstract

   This document describes an architecture for exposing transport
   protocol features to applications for network communication, the
   Transport Services architecture.  The Transport Services Application
   Programming Interface (API) is based on an asynchronous, event-driven
   interaction pattern.  It uses messages for representing data transfer
   to applications, and it describes how implementations can use
   multiple IP addresses, multiple protocols, and multiple paths, and
   provide multiple application streams.  This document further defines
   common 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 14 January 2021                [Page 1]
Internet-Draft              TAPS Architecture                  July 2020

   This Internet-Draft will expire on 14 January 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Specification of Requirements . . . . . . . . . . . . . .   5
   2.  API Model . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Event-Driven API  . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Data Transfer Using Messages  . . . . . . . . . . . . . .   7
     2.3.  Flexibile Implementation  . . . . . . . . . . . . . . . .   8
   3.  API and Implementation Requirements . . . . . . . . . . . . .   9
     3.1.  Provide Common APIs for Common Features . . . . . . . . .   9
     3.2.  Allow Access to Specialized Features  . . . . . . . . . .  10
     3.3.  Select Equivalent Protocol Stacks . . . . . . . . . . . .  11
     3.4.  Maintain Interoperability . . . . . . . . . . . . . . . .  12
   4.  Transport Services Architecture and Concepts  . . . . . . . .  12
     4.1.  Transport Services API Concepts . . . . . . . . . . . . .  13
       4.1.1.  Connections and Related Objects . . . . . . . . . . .  15
       4.1.2.  Pre-Establishment . . . . . . . . . . . . . . . . . .  16
       4.1.3.  Establishment Actions . . . . . . . . . . . . . . . .  17
       4.1.4.  Data Transfer Objects and Actions . . . . . . . . . .  18
       4.1.5.  Event Handling  . . . . . . . . . . . . . . . . . . .  19
       4.1.6.  Termination Actions . . . . . . . . . . . . . . . . .  20
Show full document text