ALTO Network-Server and Server-Server APIs
draft-medved-alto-svr-apis-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2011-03-04 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-medved-alto-svr-apis-00.txt
Abstract
ALTO servers require automated operation, where the topology of the underlying networks is incorporated into network maps automatically. In addition to the Client-to-Server API defined in the ALTO protocol document, two more standardized API are required: an API between the ALTO Server and networking nodes (e.g. routers), through which the ALTO Server can get topology information from the network, and an API between the ALTO Servers, through which they can exchange topology and status information between themselves.
Authors
Jan Medved
(jmedved@juniper.net)
David Ward
(dward@cisco.com)
Jon Peterson
(jon.peterson@neustar.biz)
Richard Woundy
(Richard_Woundy@cable.comcast.com)
Dave McDysan
(dave.mcdysan@verizon.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)