Architectural Considerations for Delivering Latency Critical Communication over the Internet
draft-xia-latency-critical-communication-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jinwei Xia | ||
| Last updated | 2018-05-03 (Latest revision 2017-10-30) | ||
| 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
There is clear demand for Internet applications requiring critical low-latency and reliable communication - Latency Critical Communication (LCC). This document is intended to stimulate LCC discussion and is not expected to be published as an RFC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)