Skip to main content

Topology API Use Cases

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jan Medved , Stefano Previdi , Victor Lopez , Shane Amante
Last updated 2014-04-23 (Latest revision 2013-10-20)
RFC stream (None)
Intended RFC status (None)
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:


This document describes use cases for gathering routing, forwarding and policy information, (hereafter referred to as topology information), about the network. It describes several applications that need to view 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 topology information.


Jan Medved
Stefano Previdi
Victor Lopez
Shane Amante

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)