Topology API Use Cases
draft-amante-irs-topology-use-cases-01

Document Type Expired Internet-Draft (individual)
Last updated 2014-03-03 (latest revision 2013-08-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-amante-irs-topology-use-cases-01.txt

Abstract

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.

Authors

Jan Medved (jmedved@cisco.com)
Thomas Nadeau (tnadeau@juniper.net)
Shane Amante

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