Deterministic Networking Use Cases
RFC 8578
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Sarah Banks was marked no-response |
|
2019-05-10
|
(System) | Received changes through RFC Editor sync (created alias RFC 8578, changed abstract to 'This document presents use cases for diverse industries that have in … Received changes through RFC Editor sync (created alias RFC 8578, changed abstract to 'This document presents use cases for diverse industries that have in common a need for "deterministic flows". "Deterministic" in this context means that such flows provide guaranteed bandwidth, bounded latency, and other properties germane to the transport of time-sensitive data. These use cases differ notably in their network topologies and specific desired behavior, providing as a group broad industry context for Deterministic Networking (DetNet). For each use case, this document will identify the use case, identify representative solutions used today, and describe potential improvements that DetNet can enable.', changed pages to 97, changed standardization level to Informational, changed state to RFC, added RFC published event at 2019-05-10, changed IESG state to RFC Published) |
|
2019-05-10
|
(System) | RFC published |