Requirements for OAM tools that enable flow Analysis
draft-janapath-opsawg-flowoam-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Janardhanan Pathangi , Balaji Venkat Venkataswami , Richard Groves , Peter Hoose | ||
| Last updated | 2012-11-09 (Latest revision 2012-05-08) | ||
| 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 specifies Operations and Management (OAM) requirements that improve on the traditional OAM tools like Ping and Traceroute. These requirements have arisen from the fact that more details than given by Ping and Traceroute are required while troubleshooting or doing performance and network planning. These requirements have been gathered from network operators especially from data centers where the networks have slightly different characteristics compared to regular campus/carrier networks.
Authors
Janardhanan Pathangi
Balaji Venkat Venkataswami
Richard Groves
Peter Hoose
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)