<?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>NRF9160: Any way to persist DTLS Connection-ID (CID)/Session across e.g. socket closing/modem flight mode?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104997/nrf9160-any-way-to-persist-dtls-connection-id-cid-session-across-e-g-socket-closing-modem-flight-mode</link><description>I&amp;#39;m currently evaluating DTLS-CID for our use cases. 
 As far as I understand, the point of CID is to have the connection-identifier be distinct from the port/ip tuple, so that the dlts connection can remain active/you don&amp;#39;t need to do a new handshake</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 26 Oct 2023 14:04:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104997/nrf9160-any-way-to-persist-dtls-connection-id-cid-session-across-e-g-socket-closing-modem-flight-mode" /><item><title>RE: NRF9160: Any way to persist DTLS Connection-ID (CID)/Session across e.g. socket closing/modem flight mode?</title><link>https://devzone.nordicsemi.com/thread/452627?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2023 14:04:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:270cb059-8eeb-4bd5-b7e4-0c3ea09d52b7</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;Your welcome.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF9160: Any way to persist DTLS Connection-ID (CID)/Session across e.g. socket closing/modem flight mode?</title><link>https://devzone.nordicsemi.com/thread/452531?ContentTypeID=1</link><pubDate>Thu, 26 Oct 2023 11:47:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:125bbda6-ab91-45c9-bfb4-f0cd0775eeb7</guid><dc:creator>HFled</dc:creator><description>&lt;p&gt;I played around with CONN_LOAD/SAVE but without success. The documentation also still explicitly states that context is lost on socket close, so I suppose that&amp;#39;s to be expected.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m aware that PSM would solve my issue, but I&amp;#39;m explicitly interested in the non-psm case. Moving the DTLS context out of the modem/into app-space seems to be the obvious/proper solution for that. Though I&amp;#39;ll still need to investigate the Blog post linked by &lt;a href="https://devzone.nordicsemi.com/members/charlie-shao"&gt;Charlie&lt;/a&gt; above.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;PS: Just randomly want to say thanks for all the work and support you&amp;#39;re doing around here and generally speaking in the DTLS/Coap realm. &amp;quot;So I stumbled across this post/answer/project&amp;quot; by Achim has become a bit of a running gag among me and my colleagues (in a positive way ofc. ;) ).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF9160: Any way to persist DTLS Connection-ID (CID)/Session across e.g. socket closing/modem flight mode?</title><link>https://devzone.nordicsemi.com/thread/452359?ContentTypeID=1</link><pubDate>Wed, 25 Oct 2023 18:05:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6538a6bd-a5ab-4d2f-9782-dd73f54ece9c</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;using PSM there is no need to &amp;quot;turn off&amp;quot; the modem. So you don&amp;#39;t need to close the socket.&lt;/p&gt;
&lt;p&gt;AFAIK, there is also a possibility to save (TLS_DTLS_CONN_SAVE) and load (TLS_DTLS_CONN_LOAD) the connection. So in cases, where the modem lose the network and closes the socket on its own, that may help. I didn&amp;#39;t test that.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m using my own implementation (&lt;a id="" href="https://github.com/boaks/zephyr-coaps-client"&gt;https://github.com/boaks/zephyr-coaps-client&lt;/a&gt;), where tinydtls is used and is outside of the socket and so more resilient against &amp;quot;TCP style implementations&amp;quot;, which drops sockets, when the network is temporary lost. That also needs to close and open the UDP socket (that&amp;#39;s caused by the modem), but the DTLS context is not affected.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF9160: Any way to persist DTLS Connection-ID (CID)/Session across e.g. socket closing/modem flight mode?</title><link>https://devzone.nordicsemi.com/thread/452266?ContentTypeID=1</link><pubDate>Wed, 25 Oct 2023 12:26:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:39110f41-bbb1-4224-83ae-eb840ec7f596</guid><dc:creator>Charlie</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;You can refer to&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/extend-your-battery-life-with-nrf-cloud-coap-interface"&gt;(+) Extend your battery life with nRF Cloud&amp;#39;s CoAP interface - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)&lt;/a&gt;&amp;nbsp;for the usage of&amp;nbsp;&lt;span&gt;&amp;nbsp;DTLS 1.2 Connection ID (CID) extension (&lt;/span&gt;&lt;a href="https://datatracker.ietf.org/doc/html/rfc9146"&gt;RFC 9146&lt;/a&gt;&lt;span&gt;) in CoAP.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It needs support from both the client and server side. nRF9160 MFW from v1.3.5 and the current nRF Cloud CoAP API support this extension.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Charlie&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>