ALTO Multi-Domain Use Cases and Services
draft-yang-alto-multi-domain-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Danny Alex Lachos Perez , Ingmar Poese , Mario Lassnig , Annie Gu , Y. Richard Yang , Jordi Ros-Giralt | ||
| Last updated | 2024-01-11 (Latest revision 2023-07-10) | ||
| 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
Application-Layer Traffic Optimization (ALTO) provides means for network applications to obtain network information. Although ALTO is inherently multi-domain, in that the ALTO server representing the network and the ALTO client requesting the network information belong to different trust domains, there are more general cases where the path from the source and the destination spans multiple autonomous networks, which we call multi-domain settings. This document first gives three multi-domain use cases, and the challenges to address the challenges. It then gives a brief update on the implementation solutions that we explored to address the challenges.
Authors
Danny Alex Lachos Perez
Ingmar Poese
Mario Lassnig
Annie Gu
Y. Richard Yang
Jordi Ros-Giralt
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)