An Architecture for Transport Services
draft-pauly-taps-arch-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-08-30 (latest revision 2018-02-26) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-pauly-taps-arch-00.txt
Abstract
This document provides an overview of the architecture of Transport Services, a system for exposing the features of transport protocols to applications. This architecture serves as a basis for Application Programming Interfaces (APIs) and implementations that provide flexible transport networking services. It defines the common set of terminology and concepts to be used in more detailed discussion of Transport Services.
Authors
Tommy Pauly
(tpauly@apple.com)
Brian Trammell
(ietf@trammell.ch)
Anna Brunstrom
(anna.brunstrom@kau.se)
Gorry Fairhurst
(gorry@erg.abdn.ac.uk)
Colin Perkins
(csp@csperkins.org)
Philipp Tiesel
(philipp@inet.tu-berlin.de)
Christopher Wood
(cawood@apple.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)