title: What exactly is the 'proximity profile' with respect to the Bluetooth Low-Energy APIs?
body: <p>I am currently developing an iOS app for a BLE device which will implement the <code>Proximity Profile</code> (which I currently don't have access to yet), but I am at a loss as to <em>what</em> that actually means. </p>
  
  <p>I have read <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;ved=0CC0QFjAA&amp;url=https%3A%2F%2Fwww.bluetooth.org%2Fdocman%2Fhandlers%2Fdownloaddoc.ashx%3Fdoc_id%3D239392&amp;ei=7dqvUa6BDeWCiAKn74HoAg&amp;usg=AFQjCNFEqeNKjXxDQzB7e9pJ2pcTnYEYKg&amp;bvm=bv.47534661,d.cGE" rel="nofollow">the pdf document from bluetooth</a>, and know that the BLE device would be the <code>proximity reporter</code> and the application the <code>proximity monitor</code>, but what does that mean in terms of the <code>CoreBluetooth</code> framework?</p>
  
  <p>After connecting to a BLE device, the method I am currently using to measure proximity is through calls to <code>readRSSI</code> on the peripheral device. Does a device which implements the proximity profile behave differently so that I don't need to make that call? There isn't much documentation around to give a better idea.</p>