Post Sockets, An Abstract Programming Interface for the Transport Layer
draft-trammell-post-sockets-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian Trammell , Colin Perkins , Tommy Pauly , Mirja Kühlewind | ||
| Last updated | 2016-10-27 | ||
| Replaced by | draft-trammell-taps-post-sockets | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-trammell-taps-post-sockets | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes Post Sockets, an asynchronous abstract programming interface for the atomic transmission of objects in an explicitly 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.
Authors
Brian Trammell
Colin Perkins
Tommy Pauly
Mirja Kühlewind
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)