anchor.diff:  API to allocate radio time. The framework will attempt to allocate as much time
   as possible, in order to listen for other nodes' messages.
   
  -All nodes in the mesh share a set of dataslots, addressed by handles. 
  -These handle-value pairs are propagated through the mesh
  -with version numbers, with the objective of synchronizing the same version of
  -the values across all nodes in the mesh. Each time a node overwrites a value, it
  -increments the version number, and all nodes that receive a broadcast message
  -with a version number that is higher than the one in its database, will adapt
  -this new version of the value. 
  +All nodes in the mesh share a set of indexed dataslots. The data contained at each
  +index is propagated through the mesh with version numbers, with the objective of 
  +synchronizing the same version of the data across all nodes in the mesh. Each 
  +time a node overwrites a value, it increments the version number, and all nodes 
  +that receive a broadcast message with a version number that is higher than the 
  +one in its database, will adapt this new version of the value. 
   
   The value propagation is controlled by an implementation of the IETF RFC6206
   "Trickle", a flood control algorithm for lossy, low power networks. The Trickle
  
positive.code: 
  == Basic concepts
  
  The Rebroadcasting Mesh framework (hereby referred to as "the framework" or
  rbc_mesh) provides a connection-less, rebroadcasting infrastructure for
  synchronizing states across a set of BLE enabled nodes. All nodes receive all
  
negative.code: = nRF51-ble-broadcast-mesh
  
  Bluetooth Low Energy based Rebroadcasting mesh implementation on the nRF51.
  Works with Softdevice S110 v7.x with Timeslot API.
  Offers an API for implementing your own mesh enabled application, operating
  concurrently with regular BLE applications.
  
  