<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.amante-irs-topology-use-cases" target="https://datatracker.ietf.org/doc/html/draft-amante-irs-topology-use-cases-01">
   <front>
      <title>Topology API Use Cases</title>
      <author initials="J." surname="Medved" fullname="Jan Medved">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T." surname="Nadeau" fullname="Thomas Nadeau">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="S." surname="Amante" fullname="Shane Amante">
         </author>
      <date month="August" day="16" year="2013" />
      <abstract>
	 <t>   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 &quot;Topology
   Manager&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-amante-irs-topology-use-cases-01" />
   
</reference>
