anchor.diff:  may be configured to emit the zero length messages. If configured so, bridge will
   wait corresponding idle messages too. If not received in configured time, the
   connection is restarted.
  +
  +== General message flow
  +
  +1. TCP/IP Connection is being established
  +
  +2. Each node sends it's local monotonic clock to other node with *TIMESYNC* message 
  +(see <<message-timesync>>) and periodically continues to resynchronize.
  +
  +3. Each at start and later periodically sends service table updates to other node 
  +with *REFRESH* messages (see <<message-refresh>>).
  +
  +4. Nodes start to send XATMI IPC data with *TPCALL* messages (see <<message-tpcall>>)
  +or *TPNOTIF* messages (see <<message-tpnotif>>).
   
   == Message TLV Encoding rules
   
  
positive.code: |TLV TAG | Name | Format | Cond | Default value | Description
  |0x13B1 |vname |STRING0..33 |Mand |N/A | View name. Might be empty string
  For "emtpy" occurrences when embedded in UBF sub-field
  |0x13BB |vflags |UINT1 |Opt |0 |View flags. Not used and must be sent as *0*
  |=========================================================
  
  Following block repeats with each of the view field occurrence:
  
negative.code: - CMDCALL tag 0x1073 (msg_type) is set to *13*
  
  |0x10AF |time |NTIMER |Mand |N/A |Local monotonic time.
  |0x10B0|mode|INT1|Mand|N/A|Following values possible:
  
  *1* - Async clock data, used at connection establishment.
  
  