anchor.diff:  ** *Action*:  The next stream to go after this stream is finished. Valid for Burst/Continuous mode
   
   
  -=== Statful vs Stateless 
  +=== Stateful vs Stateless 
   
   TRex Stateless support is basic L2/L3 tests more for Switch/Router. 
   With Stateless it is possible to define a Stream that has a *one* packet template, define a program to change any fields in the packet and run it in continues/burst/multi-burst mode.
  
positive.code: And create a program for each stream to change src_ip=10. 0.0.1-10.0.0.254 this will create something similar to Stateful but the underline is totally different.  
  If you are confused you probably need Stateless.
  
  .Statful vs Stateless 
  [cols="1^,3^,3^", options="header"]
  |=================
  | Feature       |  Stateless  |Statful 
  
negative.code: 
  *Discussion*::
  
  The following are the main traffic profile formats. Native is the preferred format. There is a separation between how the traffic is defined and how to control/activate it. The API/Console/GUI can load a traffic profile and start/stop/get a statistic. Due to this separation it is possible to share traffic profiles.
  
  .Traffic profiles formats
  [cols="1^,1^,10<", options="header",width="80%"]
  |=================
  | Profile Type       | Format | Description  
  | Native             | Python | Has the most flexibility. Any format can be converted to native using `stl-sim` using --native option
  | HLT                | Python | Uses HLT arguments 
  | YAML               | YAML   | It is the common denominator traffic profile. We suggest not to use it by human as it is not possible to compose packet using scapy. it is used to move a profile between GUI and Console or API. It can be converted to native using the stl-sim using --native switch 
  |=================
  
  
  