Use of ALTO for Determining Service Edge
draft-contreras-alto-service-edge-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Luis M. Contreras , Danny Alex Lachos Perez , Christian Esteve Rothenberg | ||
| Last updated | 2021-05-06 (Latest revision 2020-11-02) | ||
| RFC stream | (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 and interconnect computing capabilities across the network for hosting network functions and applications. In distributed computing environments, both computing and topological information are necessary in order to determine the more convenient infrastructure where to deploy such a service or application. This document raises an initial approach towards the use of ALTO to provide such information and assist in the selection of proper execution environments.
Authors
Luis M. Contreras
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.)