Is pairing necessary for Resolvable Private Address feature?

RE: Is pairing necessary for Resolvable Private Address feature?

Justin — Mon, 14 Aug 2023 19:56:23 GMT

Thank you haakonsh for the clarification.

RE: Is pairing necessary for Resolvable Private Address feature?

haakonsh — Mon, 14 Aug 2023 19:52:46 GMT

Yes, the private resolvable address is random, and that is what I've described earlier. The private resolvable address can be decrypted(resolved) if you have its Identity Resolving Key.

RE: Is pairing necessary for Resolvable Private Address feature?

Justin — Mon, 14 Aug 2023 14:42:22 GMT

Yes I am looking for Random Private Address Feature. can it be resolvable?

RE: Is pairing necessary for Resolvable Private Address feature?

haakonsh — Fri, 11 Aug 2023 08:35:05 GMT

Private Resolvable Address, perhaps we've been miscommunicating.
Do you mean Random Private Address(non-resolvable)?

If so then you only need to call sd_ble_gap_privacy_set.

RE: Is pairing necessary for Resolvable Private Address feature?

Justin — Thu, 10 Aug 2023 19:17:04 GMT

Thank you for your reply.

I do not plan to pair or bond the device. I was under impression that RPA needs pairing or bonding.

But I guess you clarified that it doesn't and having a private resolvable key is sufficient.

May I know what does PRA stand for in your message?

RE: Is pairing necessary for Resolvable Private Address feature?

haakonsh — Thu, 10 Aug 2023 13:59:41 GMT

[quote user=""]Is pairing always necessary for RPA feature?[/quote]

Technically no, but the wast majority of use-cases that include devices using PRA's in a connection also include device authentication and encryption (pairing).

If you want two devices to establish a connection using PRAs then both devices needs to know each other's Private Resolvable Key. And at that point you might as well include the rest of the pairing info as well.

Why do you not want to pair or bond your devices?

See also examples\ble_peripheral\ble_app_hrs and examples\ble_central_and_peripheral\experimental\ble_app_interactive.