IP Flow Path Trace Requirements
draft-yin-tsvwg-ipflow-pathtrace-ps-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuanbin Yin , Sheng Jiang , Gang Yan | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| 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 the requirements of IP flow path trace. Network administrators need to get the real IP flow path information, of which a specific IP flow goes through heterogeneous network environments. It is also desired for more information relevant to the IP flow path. Based on the information, network administrators can locate possible faults of the network quickly or optimize network resource for better network performance.
Authors
Yuanbin Yin
Sheng Jiang
Gang Yan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)