anchor.diff:  
   === *Upcomming* TRex scalable TCP support 
   
  -With the new advanced scalable TCP support, TRex will use TCP layer for generating the L7 data this will open new capability 
  +With the new advanced scalable TCP support, TRex will use TCP layer for generating the L7 data. This will open the following new capabilities: 
   
   * Ability to work when the DUT terminates the TCP stack (e.g. compress/uncompress). In this case there is a different TCP session on each side, but L7 data are *almost* the same.
   * Ability to work in either client mode or server mode. This way TRex client side could be installed in one physical location on the network and TRex server in another. 
  
positive.code: * Accurate TCP implementation (at least BSD based)
  * Ability to change fields in the L7 application - for example, change HTTP User-Agent field
  
  more can be seen here link:https://communities.cisco.com/community/developer/trex/blog/2017/06/20/trex-upcoming-stateful-scalable-tcp-support[scalable TCP]
  
  === What it is not
  
  
negative.code: 
  == TRex Low-Cost, High-Speed Stateful Traffic Generator 
  
  TRex is a traffic generator for Stateful and Stateless usecases. 
  
  Traditionally, network infrastructure devices have been tested using commercial traffic generators, while performance was measured using metrics like packets per second (PPS) and No Drop Rate (NDR). As the network infrastructure functionality has become more complex, stateful traffic generators have become necessary in order to test with more realistic application traffic pattern scenarios.
  Realistic and Stateful traffic generators are needed in order to:
  
  