<?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>Observation regarding GATT Bearer &amp;quot;Data OUT&amp;quot; Notifications Re-assembly logic and MTU negotiations</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37724/observation-regarding-gatt-bearer-data-out-notifications-re-assembly-logic-and-mtu-negotiations</link><description>Part 1: A device that is exposing Mesh Provisioning Service[as a unprovisioned device] or the Mesh Proxy Service [as a provisioned device] could under-utilize the negotiated ATT MTU and still transmit a valid mesh GATT Proxy PDUs to the peer Proxy Client</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 24 Aug 2018 07:49:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37724/observation-regarding-gatt-bearer-data-out-notifications-re-assembly-logic-and-mtu-negotiations" /><item><title>RE: Observation regarding GATT Bearer "Data OUT" Notifications Re-assembly logic and MTU negotiations</title><link>https://devzone.nordicsemi.com/thread/145612?ContentTypeID=1</link><pubDate>Fri, 24 Aug 2018 07:49:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f841687-0ee3-4bde-8e6d-dd2cf919f095</guid><dc:creator>Roshan Rajaratnam</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/srikkanth"&gt;Srikkanth&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This is really good observation just like&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/thst"&gt;thst&lt;/a&gt;&amp;nbsp;has mentioned. I would really appreciate if you could send a pull request across to our dev branch. Although, I might not agree on completely on the Part 1, because now I can see more clearly where I can improve when reassembling gatt level segmentations as both your and my solution does not seem to care if the incoming message is a part of a gatt level segmented message before appending them and I only check while trying to remove the segmentation bits and this would be wrong if two invalid messages were appended together. I guess the most correct approach would be to check the pdu type even before appending everything in to one packet, to ensure that they are part of the same message as there could be parallel messages.&lt;/p&gt;
&lt;p&gt;Thanks again for this&lt;/p&gt;
&lt;p&gt;Roshan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Observation regarding GATT Bearer "Data OUT" Notifications Re-assembly logic and MTU negotiations</title><link>https://devzone.nordicsemi.com/thread/145543?ContentTypeID=1</link><pubDate>Thu, 23 Aug 2018 14:36:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efa9218f-654b-48d0-bc06-b2eade24f59f</guid><dc:creator>thst</dc:creator><description>&lt;p&gt;Hi Srikkanth,&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you for digging into the Android-nRF-Mesh-Library, these certainly look like good observations.&amp;nbsp; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;The best way to get your changes into the code base and in front of the eyes of our mobile app developers would be to make a PR on the Github project.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;a href="https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library"&gt;https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thanks again.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Tom&lt;/p&gt;
&lt;p&gt;Mesh Team&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>