Topology API Use Cases
draft-amante-irs-topology-use-cases-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Shane Amante , Jan Medved , Thomas Nadeau | ||
| Last updated | 2013-04-05 (Latest revision 2012-10-02) | ||
| RFC stream | (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
This document describes use cases for gathering routing, forwarding and policy information, (hereafter referred to as topology information), about the network and reflecting changes to the topology back into the network and related systems. It describes several applications that need to view or change the topology of the underlying physical or logical network. This document further demonstrates a need for a "Topology Manager" and related functions that collects topology data from network elements and other data sources, coalesces the collected data into a coherent view of the overall network topology, and normalizes the network topology view for use by clients -- namely, applications that consume or want to change topology information.
Authors
Shane Amante
Jan Medved
Thomas Nadeau
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)