ALTO Topology Service: Uses Cases, Requirements, and Framework
draft-bernstein-alto-topo-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg M. Bernstein , Y. Richard Yang , Young Lee | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| 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
Exposing additional topology information of networks to applications and users beyond that of the current ALTO protocol can enable many important existing and emerging use cases, and many network providers already provide additional information about their networks. At the same time, there is no standard for exposing network topology in a manner that provides simplification via abstraction to the application layer and information hiding via abstraction to the network provider. In this document, we provide a survey of use-cases for extended network topology information, present some initial requirements for such services, and then give a framework of how to integrate such an extended ALTO topology service with network control infrastructure.
Authors
Greg M. Bernstein
Y. Richard Yang
Young Lee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)