Use case and Requirements for Latency Management in Network Slices
draft-suzuki-netslices-latency-management-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Toshiaki Suzuki | ||
| Last updated | 2018-09-02 (Latest revision 2018-03-01) | ||
| 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
This draft provides a use case that addresses the need for latency management for end-to-end data transmissions through multiple domains. Specifically, examples of latency management schemes are described. In addition, the necessity of a common latency management framework and of interfaces to gather latency information between edges in each domain and to determine data transmission paths is addressed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)