datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Traceflow
draft-janapath-intarea-traceflow-00

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-07-30 (latest revision 2012-01-24)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-janapath-intarea-traceflow

Abstract

This document describes a new OAM protocol - TraceFlow that captures information pertaining to a traffic flow along the path that the flow takes through the network. TraceFlow is ECMP and link-aggregation aware and captures the information about constituent members through which the traffic flow passes. TraceFlow gathers information that is relevant to the flow such as outgoing interface Layer 3 address, Next-hop to which the packet of the flow is forwarded, effect of network policies such as access control lists on the flow. This draft requires the Traceflow protocol to be processed by Layer 3 devices only. Devices such as Layer 2 devices, MPLS LERs/LSRs along the way are passed through without any processing as if in a pass-through mode. IP tunnels such as IP-in-IP, IP-in-GRE mechanisms are expected to pass the Traceflow packets through them using the pass through mode. For achieving its purpose Traceflow advocates the use of a specific UDP destination port to be assigned from IANA.

Authors

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)