Need clarification on OOB Type field values.

[Utkarsh]

In ncs/v.2.6.1/zephyr/include/zephyr/bluetooth/mesh/main.h there are enums defined under the OOB Type field values as 

/** OOB Type field values. */
enum {
	BT_MESH_STATIC_OOB_AVAILABLE = BIT(0), /**< Static OOB information available */
	BT_MESH_OOB_AUTH_REQUIRED    = BIT(1)  /**< OOB authentication required */
};

What is the difference between the two? I am not able to understand what the comments are trying to mean.

My end goal is to use certificate based provisioning. Implementation vise can it be considered as a subset of Static OOB authentication? 

[Hung Bui]

Hi Utkarsh, 

I would suggest to look into the Bluetooth Mesh Profile specification if you find some terms are not clear. https://www.bluetooth.com/specifications/specs/mesh-protocol/

You can find the explanation on how static OOB works at 5.4.2.4.5 

The description for OOB_AUTH_REQUIRED can be found at 5.4.2.4.3 and 5.4.2.4.4 .

Basically static OOB mean the same OOB data is stored on the provisioner and the provisionee prior to the provisioning process. When provisioning they simply use the data already stored instead of displaying and inputting to the peer. 

[Utkarsh]

Thank you !