Compute First Networking (CFN) Scenarios and Requirements
draft-geng-rtgwg-cfn-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Liang Geng , Peter Willis | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| 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
Service providers are exploring the edge computing to achieve better response times and transfer rate by moving the computing towards the edge of the network in scenarios like 5G MEC, virtualized central office, etc. Providing services by sharing computing resources from multiple edges is emerging. The service nodes from multiple edges normally have two key features, service equivalency and service dynamics. When the computing resources attached to a single edge site is overloaded, static service dispatch can possibly keep allocating the service request to it and cause inefficient utilization. The service request to edge computing needs to be dispatched to and served by the most suitable edge to improve user experience and system utilization by taking both the available computing resources and network conditions into account. This draft describes scenarios and requirements of Compute First Networking (CFN) to make the computing and network resource to be considered in a collaborative way to achieve a more balanced network- based distributed service dispatching.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)