Post Sockets, An Abstract Programming Interface for the Transport Layer
draft-trammell-taps-post-sockets-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-08
Replaces draft-trammell-post-sockets
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda taps at IETF-98
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TAPS Working Group                                           B. Trammell
Internet-Draft                                                ETH Zurich
Intended status: Informational                                C. Perkins
Expires: September 9, 2017                         University of Glasgow
                                                                T. Pauly
                                                              Apple Inc.
                                                           M. Kuehlewind
                                                              ETH Zurich
                                                          March 08, 2017

Post Sockets, An Abstract Programming Interface for the Transport Layer
                  draft-trammell-taps-post-sockets-00

Abstract

   This document describes Post Sockets, an asynchronous abstract
   programming interface for the atomic transmission of messages in an
   inherently multipath environment.  Post replaces connections with
   long-lived associations between endpoints, with the possibility to
   cache cryptographic state in order to reduce amortized connection
   latency.  We present this abstract interface as an illustration of
   what is possible with present developments in transport protocols
   when freed from the strictures of the current sockets API.

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 http://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 September 9, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Trammell, et al.        Expires September 9, 2017               [Page 1]
Internet-Draft                Post Sockets                    March 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
   2.  Abstractions and Terminology  . . . . . . . . . . . . . . . .   5
     2.1.  Message Carrier . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  Listener  . . . . . . . . . . . . . . . . . . . . . .   7
       2.1.2.  Source  . . . . . . . . . . . . . . . . . . . . . . .   8
       2.1.3.  Sink  . . . . . . . . . . . . . . . . . . . . . . . .   8
       2.1.4.  Responder . . . . . . . . . . . . . . . . . . . . . .   8
       2.1.5.  Stream  . . . . . . . . . . . . . . . . . . . . . . .   8
     2.2.  Message . . . . . . . . . . . . . . . . . . . . . . . . .   8
       2.2.1.  Lifetime and Partial Reliability  . . . . . . . . . .   9
       2.2.2.  Priority  . . . . . . . . . . . . . . . . . . . . . .  10
       2.2.3.  Dependence  . . . . . . . . . . . . . . . . . . . . .  10
       2.2.4.  Idempotence . . . . . . . . . . . . . . . . . . . . .  10
       2.2.5.  Immediacy . . . . . . . . . . . . . . . . . . . . . .  10
       2.2.6.  Additional Events . . . . . . . . . . . . . . . . . .  10
     2.3.  Association . . . . . . . . . . . . . . . . . . . . . . .  11
     2.4.  Remote  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     2.5.  Local . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     2.6.  Transient . . . . . . . . . . . . . . . . . . . . . . . .  12
     2.7.  Path  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     2.8.  Policy Context  . . . . . . . . . . . . . . . . . . . . .  13
   3.  Abstract Programming Interface  . . . . . . . . . . . . . . .  14
     3.1.  Example Connection Patterns . . . . . . . . . . . . . . .  15
       3.1.1.  Client-Server . . . . . . . . . . . . . . . . . . . .  15
       3.1.2.  Client-Server with Happy Eyeballs and 0-RTT
               establishment . . . . . . . . . . . . . . . . . . . .  16
       3.1.3.  Peer to Peer with Network Address Translation . . . .  17
Show full document text