Transport APIs
draft-hurtig-tsvwg-transport-apis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Per Hurtig , Stein Gjessing , Michael Welzl , Martin Sustrik | ||
| Last updated | 2014-06-18 (Latest revision 2013-12-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Commonly used networking APIs are currently limited by the transport layer's inability to expose services instead of protocols. An API/ application/user is therefore forced to use exactly the services that are implemented by the selected transport. This document surveys networking APIs and discusses how they can be improved by a more expressive transport layer that hides and automatizes the choice of the transport protocol.
Authors
Per Hurtig
Stein Gjessing
Michael Welzl
Martin Sustrik
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)