[
https://issues.apache.org/jira/browse/MYNEWT-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Collins updated MYNEWT-842:
---------------------------------------
Description:
If an attempt to add a peer's IRK to the resolving list fails, the failure is
not reported, and the operation is not reattempted. Adding to the resolving
list fails if the host is scanning or advertising at the time, so this is a
common occurrence.
I am not sure what the best solution is to this problem. I have a few ideas
(order of increasing complexity):
1. The host passes the necessary information up to the application. It is then
up to the application to populate the resolving list when possible, if desired.
2. The host remembers the failed attempt and retries when in a suitable state
(i.e., when advertising, scanning, and connecting has stopped).
3. The host temporarily suspends all GAP activity, adds the entry to the
resolving list, and resumes GAP activity.
was:
If an attempt to add a peer's IRK to the resolving list fails, the failure is
not reported, and the operation is not reattempted. Adding to the resolving
list fails if the host is scanning or advertising at the time, so this is a
common occurrence.
I am not sure what the best solution is to this problem. I have a few ideas:
1. The host should pass the necessary information up to the application. It is
up to the application to populate the resolving list when possible.
2. The host should remember the failed attempt and retry when it is in a
suitable state (i.e., when advertising, scanning, and connecting has stopped).
> BLE Host - Handle failure to add entry to resolving list
> --------------------------------------------------------
>
> Key: MYNEWT-842
> URL: https://issues.apache.org/jira/browse/MYNEWT-842
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Nimble
> Reporter: Christopher Collins
>
> If an attempt to add a peer's IRK to the resolving list fails, the failure is
> not reported, and the operation is not reattempted. Adding to the resolving
> list fails if the host is scanning or advertising at the time, so this is a
> common occurrence.
> I am not sure what the best solution is to this problem. I have a few ideas
> (order of increasing complexity):
> 1. The host passes the necessary information up to the application. It is
> then up to the application to populate the resolving list when possible, if
> desired.
> 2. The host remembers the failed attempt and retries when in a suitable state
> (i.e., when advertising, scanning, and connecting has stopped).
> 3. The host temporarily suspends all GAP activity, adds the entry to the
> resolving list, and resumes GAP activity.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
