anchor.diff:  node, depending on configuration parameters provided to the `rbc_mesh_init()`
   function at runtime. Each mesh value will operate with their own instance of
   the Trickle algorithm, meaning that they will be rebroadcasted independently.
  -The handles addressing the values are stored as standard Bluetooth SIG
  -namespace descriptors, where the enumeration of each value is used as
  -mesh-global handles for this value. This descriptor may be read by external
  -nodes.
  +The handles addressing the values are stored as standard https://developer.bluetooth.org/gatt/Pages/GattNamespaceDescriptors.aspx[Bluetooth SIG
  +namespace descriptors], where the enumeration of each value is used as
  +a mesh-global handle.
  +
  +_NOTE:_ Because the Bluetooth SIG has defined namespace descriptor 0 as
  +"unknown", the handles start at 1, and trying to access handle 0 returns an
  +NRF_ERROR_INVALID_ADDR error.
   
   ==== Mesh metadata
   For ease of use, the service also provides a Metadata characteristic, providing
  
positive.code: 
  
  === Trickle Algorithm
  === Timeslots
  === Resource allocation
  
  == Forum
  http://devzone.nordicsemi.com/[Nordic Developer Zone]
  
negative.code: classic BLE Softdevice connection, implemented in application space. The "BLE
  Gateway example" displays a way to achieve such behavior.
  
  == Usage
  In addition to the two provided examples, there is a template project under
  _examples/_. This may be used as a basis for your own applications, or you
  could choose to do it yourself from scratch. In theory, the framework should be
  compatible with most Softdevice based projects, but some restrictions to
  hardware and software modules apply, see <<Resource allocation>> for details.
  The framework adds a Mesh GATT service to the Softdevice GATT server which
  contain all mesh-global states. This service may be accessed by external nodes,
  just as any other GATT service, through a connection established via the
  Softdevice. See section <<GATT Service>> for details about structure and
  access. 
  
  == Structure
  The project is split into two parts: _rbc_mesh/_ (the framework), and a folder with
  examples. The framework is interfaced through a set of API functions,
  exclusively contained in the _rbc_mesh.h_ file. 
  
  === Framework Modules
  The framework is split into several separate modules, each of which is
  