Use of ALTO for Determining Service Edge
draft-contreras-alto-service-edge-10
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Luis M. Contreras , Sabine Randriamasy , Jordi Ros-Giralt , Danny Alex Lachos Perez , Christian Esteve Rothenberg | ||
| Last updated | 2024-04-15 (Latest revision 2023-10-13) | ||
| 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 starting to deploy computing capabilities across the network for hosting applications such as AR/VR, vehicle networks, IoT, and AI training, among others. In these distributed computing environments, knowledge about computing and communication resources is necessary to determine the proper deployment location of each application. This document proposes an initial approach towards the use of ALTO to expose such information to the applications and assist the selection of their deployment locations.
Authors
Luis M. Contreras
Sabine Randriamasy
Jordi Ros-Giralt
Danny Alex Lachos Perez
Christian Esteve Rothenberg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)