Architecture for delivering low latency service
draft-ding-low-latency-delivery-arch-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | ding xiaojian, Jinwei Xia | ||
| Last updated | 2018-04-19 (Latest revision 2017-07-19) | ||
| 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
Demand for Ultra high-Reliability and Low-latency Communication (URLLC) and Broadband Assured IP Services (BAS) will grow as new service scenarios like 5G, IoT, AR/VR, Cloud are deployed. As these new service scenarios will typically rely on shared packet infrastructure like Internet, methods to ensure URLLC and BAS performance across the underlying network resources will be required. This document outlines the motivation and key requirements for URLLC or BAS connectivity across heterogeneous network domains. It also outlines the corresponding models and architecture required for providing orchestrated URLLC or BAS communication.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)