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

Document Type Active Internet-Draft (taps WG)
Last updated 2018-10-22
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Nov 2019 - Submit document(s) t... )
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: April 25, 2019                                       ETH Zurich
                                                            A. Brunstrom
                                                     Karlstad University
                                                            G. Fairhurst
                                                  University of Aberdeen
                                                              C. Perkins
                                                   University of Glasgow
                                                               P. Tiesel
                                                               TU Berlin
                                                                 C. Wood
                                                              Apple Inc.
                                                        October 22, 2018

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

Abstract

   This document provides an overview of the architecture of Transport
   Services, a system for exposing the features of transport protocols
   to applications.  This architecture serves as a basis for Application
   Programming Interfaces (APIs) and implementations that provide
   flexible transport networking services.  It defines the common set of
   terminology and concepts to be used in more detailed discussion of
   Transport Services.

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 April 25, 2019.

Pauly, et al.            Expires April 25, 2019                 [Page 1]
Internet-Draft              TAPS Architecture               October 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.

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  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Design Principles . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Common APIs for Common Features . . . . . . . . . . . . .   7
     3.2.  Access to Specialized Features  . . . . . . . . . . . . .   7
     3.3.  Scope for API and Implementation Definitions  . . . . . .   8
   4.  Transport Services Architecture and Concepts  . . . . . . . .   9
     4.1.  Transport Services API Concepts . . . . . . . . . . . . .  10
       4.1.1.  Basic Objects . . . . . . . . . . . . . . . . . . . .  12
       4.1.2.  Pre-Establishment . . . . . . . . . . . . . . . . . .  13
       4.1.3.  Establishment Actions . . . . . . . . . . . . . . . .  14
       4.1.4.  Data Transfer Objects and Actions . . . . . . . . . .  14
       4.1.5.  Event Handling  . . . . . . . . . . . . . . . . . . .  15
       4.1.6.  Termination Actions . . . . . . . . . . . . . . . . .  16
     4.2.  Transport System Implementation Concepts  . . . . . . . .  16
       4.2.1.  Candidate Gathering . . . . . . . . . . . . . . . . .  17
       4.2.2.  Candidate Racing  . . . . . . . . . . . . . . . . . .  17
     4.3.  Protocol Stack Equivalence  . . . . . . . . . . . . . . .  18
       4.3.1.  Transport Security Equivalence  . . . . . . . . . . .  19
     4.4.  Message Framing, Parsing, and Serialization . . . . . . .  19
Show full document text