Considerations on Transport Services API for Data Centers
draft-deng-taps-datacenter-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Deng Lingli | ||
| Last updated | 2014-09-03 (Latest revision 2014-03-02) | ||
| 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
It is noticed that within a data center, unique traffic pattern and performance goals for the transport layer exist, as compared to things on the Internet. This draft discusses the usecases for applying transport APIs from the perspective of an application running in a data center environment, and proposes potential requirements for such API design.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)