<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Need clarification on OOB Type field values.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114407/need-clarification-on-oob-type-field-values</link><description>In ncs/v.2.6.1/zephyr/include/zephyr/bluetooth/mesh/main.h there are enums defined under the OOB Type field values as 
 
 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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Sep 2024 15:57:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114407/need-clarification-on-oob-type-field-values" /><item><title>RE: Need clarification on OOB Type field values.</title><link>https://devzone.nordicsemi.com/thread/500832?ContentTypeID=1</link><pubDate>Mon, 02 Sep 2024 15:57:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6659b616-efb3-42a1-8ae8-669a681db524</guid><dc:creator>Utkarsh</dc:creator><description>&lt;p&gt;Thank you !&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need clarification on OOB Type field values.</title><link>https://devzone.nordicsemi.com/thread/500791?ContentTypeID=1</link><pubDate>Mon, 02 Sep 2024 13:15:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2867d956-74e5-4a5d-8602-acca2176c3f2</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Utkarsh,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I would suggest to look into the Bluetooth Mesh Profile specification&amp;nbsp;if you find some terms&amp;nbsp;are not clear.&amp;nbsp;&lt;a href="https://www.bluetooth.com/specifications/specs/mesh-protocol/"&gt;https://www.bluetooth.com/specifications/specs/mesh-protocol/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;You can find the explanation on how static OOB works at 5.4.2.4.5&amp;nbsp;&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/8877.pastedimage1725282847045v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;The description&amp;nbsp;for&amp;nbsp;OOB_AUTH_REQUIRED can be found at 5.4.2.4.3 and 5.4.2.4.4 .&lt;br /&gt;&lt;br /&gt;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.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>