ALTO Deployment Considerations: Configuration and Monitoring by ISPs
draft-sun-alto-ispdeployment-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xianghui Sun , Y. Richard Yang | ||
| Last updated | 2011-03-14 | ||
| Replaces | draft-sun-deployment | ||
| 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
As ALTO specification continues in the ALTO Working Group and some applications start to conduct integration with ALTO, more ISPs start to evaluate key issues in the deployment of ALTO in their networks. In this document, we discuss key issues that an ISP needs to consider when deploying ALTO. In particular, we discuss issues on how to configure ALTO information as well as how to monitor the effectiveness of ALTO.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)