<?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>Identity Resolving Key and AAR module</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10700/identity-resolving-key-and-aar-module</link><description>Hi, what for IRK is used and how AAR peripheral module helps us with it?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Dec 2015 14:04:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10700/identity-resolving-key-and-aar-module" /><item><title>RE: Identity Resolving Key and AAR module</title><link>https://devzone.nordicsemi.com/thread/39939?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2015 14:04:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0bd45694-6ae3-4f96-a86c-10c4bc1b4b8f</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;IRK is typically used to generate and resolve device addresses of type &lt;em&gt;Resolvable private addresses&lt;/em&gt; to implement privacy as specified in the Bluetooth core specification 4.1, vol 6, Part B, chapter 6. AAR is to allow addresses of this type to be resolved in HW using IRK as input.&lt;/p&gt;
&lt;p&gt;A &lt;em&gt;Resolvable private addresses&lt;/em&gt; is basically an address that change over time and can only be resolved by with the IRK. Thus, making it harder to track a connection for a passive eavesdropper (sniffer).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>