An Abstract Application Layer Interface to Transport Services
draft-ietf-taps-interface-10
TAPS Working Group B. Trammell, Ed.
Internet-Draft Google Switzerland GmbH
Intended status: Standards Track M. Welzl, Ed.
Expires: 6 May 2021 University of Oslo
T. Enghardt
Netflix
G. Fairhurst
University of Aberdeen
M. Kuehlewind
Ericsson
C. Perkins
University of Glasgow
P. Tiesel
TU Berlin
C.A. Wood
Cloudflare
T. Pauly
Apple Inc.
2 November 2020
An Abstract Application Layer Interface to Transport Services
draft-ietf-taps-interface-10
Abstract
This document describes an abstract application programming
interface, API, to the transport layer, following the Transport
Services Architecture. It supports the asynchronous, atomic
transmission of messages over transport protocols and network paths
dynamically selected at runtime. It is intended to replace the
traditional BSD sockets API as the common interface to the transport
layer, in an environment where endpoints could select from multiple
interfaces and potential transport protocols.
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/.
Trammell, et al. Expires 6 May 2021 [Page 1]
Internet-Draft TAPS Interface November 2020
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 6 May 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 . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Notation . . . . . . . . . . . . . . . . . . 5
3. Overview of Interface Design . . . . . . . . . . . . . . . . 6
4. API Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Usage Examples . . . . . . . . . . . . . . . . . . . . . 8
4.1.1. Server Example . . . . . . . . . . . . . . . . . . . 8
4.1.2. Client Example . . . . . . . . . . . . . . . . . . . 9
4.1.3. Peer Example . . . . . . . . . . . . . . . . . . . . 10
4.2. Transport Properties . . . . . . . . . . . . . . . . . . 11
4.2.1. Transport Property Names . . . . . . . . . . . . . . 12
4.2.2. Transport Property Types . . . . . . . . . . . . . . 13
4.3. Scope of the Interface Definition . . . . . . . . . . . . 14
5. Pre-Establishment Phase . . . . . . . . . . . . . . . . . . . 15
5.1. Specifying Endpoints . . . . . . . . . . . . . . . . . . 16
5.1.1. Using Multicast Endpoints . . . . . . . . . . . . . . 17
5.1.2. Endpoint Aliases . . . . . . . . . . . . . . . . . . 17
5.1.3. Endpoint Examples . . . . . . . . . . . . . . . . . . 18
5.2. Specifying Transport Properties . . . . . . . . . . . . . 19
5.2.1. Reliable Data Transfer (Connection) . . . . . . . . . 22
Show full document text