An Abstract Application Layer Interface to Transport Services
draft-ietf-taps-interface-04
|
| Document |
Type |
|
Active Internet-Draft (taps WG)
|
|
Last updated |
|
2019-07-08
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
On Agenda |
|
taps at IETF-105
|
|
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 B. Trammell, Ed.
Internet-Draft Google
Intended status: Standards Track M. Welzl, Ed.
Expires: January 9, 2020 University of Oslo
T. Enghardt
TU Berlin
G. Fairhurst
University of Aberdeen
M. Kuehlewind
ETH Zurich
C. Perkins
University of Glasgow
P. Tiesel
TU Berlin
C. Wood
T. Pauly
Apple Inc.
July 08, 2019
An Abstract Application Layer Interface to Transport Services
draft-ietf-taps-interface-04
Abstract
This document describes an abstract programming interface 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 lowest common denominator interface to the transport layer, in
an environment where endpoints have multiple interfaces and potential
transport protocols to select from.
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."
Trammell, et al. Expires January 9, 2020 [Page 1]
Internet-Draft TAPS Interface 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 . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Notation . . . . . . . . . . . . . . . . . . 5
3. Interface Design Principles . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . 13
5. Pre-Establishment Phase . . . . . . . . . . . . . . . . . . . 14
5.1. Specifying Endpoints . . . . . . . . . . . . . . . . . . 14
5.2. Specifying Transport Properties . . . . . . . . . . . . . 16
5.2.1. Reliable Data Transfer (Connection) . . . . . . . . . 18
5.2.2. Preservation of Message Boundaries . . . . . . . . . 18
5.2.3. Configure Per-Message Reliability . . . . . . . . . . 18
5.2.4. Preservation of Data Ordering . . . . . . . . . . . . 18
5.2.5. Use 0-RTT Session Establishment with an Idempotent
Show full document text