<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zinjuvadia-traceflow" target="https://datatracker.ietf.org/doc/html/draft-zinjuvadia-traceflow-02">
   <front>
      <title>TraceFlow</title>
      <author initials="A." surname="Viswanathan" fullname="Arun Viswanathan">
         <organization>Force10 Networks</organization>
      </author>
      <author initials="S." surname="Krishnamurthy" fullname="Subi Krishnamurthy">
         <organization>Force10 Networks</organization>
      </author>
      <author initials="R." surname="Manur" fullname="Rajeev Manur">
         <organization>Force10 Networks</organization>
      </author>
      <author initials="V." surname="Zinjuvadia" fullname="Vishal Zinjuvadia">
         <organization>Force10 Networks</organization>
      </author>
      <date month="August" day="16" year="2008" />
      <abstract>
	 <t>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 interface address, interface statistics, 
effect of network policies on the flow and so on. 

Conventions used in this document 

The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, 
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this 
document are to be interpreted as described in RFC-2119 [1].
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zinjuvadia-traceflow-02" />
   
</reference>
