ALTO in Mobile Core
draft-randriamasy-alto-mobile-core-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yacine Mghazli , Sabine Randriamasy , Francois Taburet | ||
| Last updated | 2010-10-22 | ||
| 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
The ALTO working group provides guidance to P2P applications, which have to select one or several hosts from a set of candidates, that are able to provide a desired resource. This guidance shall be based on parameters that affect performance and efficiency of the data transmission between the hosts, e.g., the topological distance. The ultimate goal is to improve performance (or Quality of Experience) in the application while reducing resource consumption in the underlying network infrastructure. The present document addresses the case of ALTO transactions involving a peers connected via a mobile core network. It proposes specific scopes and use cases for mobile core networks and as a first step, properties of paths and endpoints that allow to facilitate ALTO transaction within such a scope.
Authors
Yacine Mghazli
Sabine Randriamasy
Francois Taburet
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)