Flexibility of Transport Layer Protocols: Use Cases
draft-mihaly-tp-flexibility-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Attila Mihaly , Lars Westberg , Robert Skog | ||
| Last updated | 2015-09-07 (Latest revision 2015-03-06) | ||
| 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 document argues for increasing the flexibility of the transport layer protocols to be possible to tailor the transport protocols to different needs (today and tomorrow) of different applications and access networks. We discuss various use cases to show that there is a need for transport protocol flexibility.
Authors
Attila Mihaly
Lars Westberg
Robert Skog
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)