Topology API Requirements
draft-medved-irs-topology-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jan Medved , Hannes Gredler , Stefano Previdi , Shane Amante | ||
| Last updated | 2013-04-12 (Latest revision 2012-10-09) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 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) interact/change the topology of the physical or logical network. for reflecting changes to the topology back in network elements..
Authors
Jan Medved
Hannes Gredler
Stefano Previdi
Shane Amante
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)