Deterministic Networking Requirements on Data and Control Plane
draft-zha-detnet-requirments-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yiyong Zha , Liang Geng | ||
| Last updated | 2016-09-17 (Latest revision 2016-03-16) | ||
| 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
Deterministic Networking (DetNet) is focused on how to serve time critical flow with low data loss and bounded delay. Unlike contemporary solution which improves QoS such as TE, redundant bandwidth provisioning and dedicated channel reservation, DetNet provides more general approaches that use IP-based techniques and guarantee the worst-case latency of DetNet flows while allowing sharing among best-effort flows. For this purpose, DetNet may require upgraded or redefined data plane as well as control plane, since current networking cannot assure maximum end-to-end latency. This document describes some technical requirements on possible data plane, control plane and DetNet flow modeling that can help to clarify those capabilities DetNet should have.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)