Requirements for OAM tools that enable flow Analysis
draft-janapath-opsawg-flowoam-req-00

 
Document
Type Expired Internet-Draft (individual)
Last updated 2012-11-09 (latest revision 2012-05-08)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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-janapath-opsawg-flowoam-req-00.txt

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 (pathangi_janardhanan@dell.com)
Balaji Venkataswami (balaji_venkat_venkat@dell.com)
Richard Groves (rgroves@microsoft.com)
Peter Hoose (phoose@fb.com)

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