Topology API Requirements
draft-medved-i2rs-topology-requirements-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-08-22 (latest revision 2013-02-18) | ||
| 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-i2rs-topology-requirements-00.txt
Abstract
This document describes requirements for collecting topology data from network elements and other sources, creating a coherent view of the network topology from the collected data, and presenting the topology view to various applications that need to: a) understand the topology; and, b) leverage topology information in order to improve application specific mechanisms such as path selection, resources reservation, etc.
Authors
Jan Medved
(jmedved@cisco.com)
Stefano Previdi
(sprevidi@cisco.com)
Hannes Gredler
(hannes@juniper.net)
Thomas Nadeau
(tnadeau@juniper.net)
Shane Amante
(shane@level3.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)