<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>Limited number of mesh nodes in a remote provisioning client</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88350/limited-number-of-mesh-nodes-in-a-remote-provisioning-client</link><description>Hi to everybody. 
 I&amp;#39;m evaluating the possible options to perform self provisioning of nodes in a mesh network starting from the pb_remote client and server examples. 
 I read that the maximum number of nodes in the network, is limited by te memory capacity</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Fri, 03 Jun 2022 06:35:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88350/limited-number-of-mesh-nodes-in-a-remote-provisioning-client" /><item><title>RE: Limited number of mesh nodes in a remote provisioning client</title><link>https://test-devzone.nordicsemi.com/thread/370794?ContentTypeID=1</link><pubDate>Fri, 03 Jun 2022 06:35:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f69baa6-be3f-441a-8abf-687112e6cf9a</guid><dc:creator>user85437</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Joakim!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for the answer.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;My idea is to store only the unique address assigned by the privisioner. I think that key storage is not strictrly necessary for every provisioned devices since they are the same for all devices. I have a doubt regarding the device key: using a unique key for all devices could lead to security problems?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Yes please, if it&amp;#39;s not a problem for you, please ask to your developers.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Br,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Gianluca&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Limited number of mesh nodes in a remote provisioning client</title><link>https://test-devzone.nordicsemi.com/thread/370636?ContentTypeID=1</link><pubDate>Thu, 02 Jun 2022 09:59:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59b823a4-dfcf-4461-b363-cc05421df9ef</guid><dc:creator>user20690</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
[quote user=""]I&amp;#39;m asking if in the scenario described is it still necessary to save provisioning node informations on the provisioning client. [/quote]
&lt;p&gt;Yes, you would still have to store the information of each node. Each node will have at least one unique address and you will have to add and store the provisioning data for each. &lt;/p&gt;
&lt;p&gt;I can ask if our developers have some suggestions to how this can be handled best, if you want?&lt;/p&gt;
&lt;p&gt;Br, &lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>