Transport Adaptation Framework (TAF)
draft-satran-transport-adaptation-framework-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Julian Satran | ||
| Last updated | 2001-11-28 | ||
| 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
This draft is an attempt to outline a 'technique' (I hesitate to call it a protocol) to adapt a transport protocol to application needs, outside the protocol payload, without interfering with the transport protocol operation, nor directly affecting its implementation. It is based on an 'interposer' header between the IP header and the transport header (TCP or UDP) and, when needed, a trailer that that is appended to the transport PDU.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)