Deterministic Networking Architecture
draft-finn-detnet-architecture-08
| Document | Type |
Replaced Internet-Draft
(candidate for detnet WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Norman Finn , Pascal Thubert | ||
| Last updated | 2016-09-02 (Latest revision 2016-08-18) | ||
| Replaced by | draft-ietf-detnet-architecture | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-detnet-architecture | |
| Consensus boilerplate | Unknown | ||
| 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) provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency. Techniques used include: 1) reserving data plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes (e.g. bridges or routers) along the path of the flow; 2) providing explicit routes for DetNet flows that do not rapidly change with the network topology; and 3) distributing data from DetNet flow packets over time and/or space to ensure delivery of each packet's data' in spite of the loss of a path. The capabilities can be managed by configuration, or by manual or automatic network management.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)