Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for getting OOB data #1860

Closed
zephyrbot opened this issue May 9, 2016 · 9 comments
Closed

Add support for getting OOB data #1860

zephyrbot opened this issue May 9, 2016 · 9 comments
Assignees
Labels
area: Bluetooth Enhancement Changes/Updates/Additions to existing features

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented May 9, 2016

Reported by Szymon Janc:

It should be possible for application to obtain data needed for Out Of Band pairing like currently connectable LE address and (eventually) TK or Hash/Rand. This API should take into consideration not only OOB pairing, but also our testing tools.

(Imported from Jira ZEP-299)

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Gajinder Vij , it seems that this should be a Story and not a Task. Correct?

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Changed from a task to a story because it's coding work.

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Andrei Laperie , just a reminder to check on the status of this.

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Szymon Janc , is this story on track to be implemented and merged before the 1.6 merge window closes on Nov 9th?

@zephyrbot
Copy link
Collaborator Author

by Szymon Janc:

Mark Linkmeyer I divided this into sub-tasks and marked already implemented ones as done so that progress can be easily tracked.
Note that actual OOB algorithms are currently not prio work as those are mostly useful with NFC which is currently not supported in Zephyr.

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Gajinder Vij , given Szymon's comment above it seems that this story will not be fully implemented as planned for 1.6. Are you okay with that? If so, will you please split this story to indicate what is planned for 1.6 and what will come later? If you need it all fully implemented for 1.6, please raise the issue.

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Gajinder Vij , Anas Nashif , please see Szymon's comment above and let me know if you're okay with this not being fully implemented for 1.6. If you are okay with it, I'll split the story into what will be delivered for 1.6 and what will come later.

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Gajinder Vij , please respond to my questions above so we can figure out what needs to happen next on this story. Thx.
Rob Rhoads

@zephyrbot zephyrbot added area: Bluetooth Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
@jhedberg
Copy link
Member

This issue seems to have been forgotten. Nordic already contributed OOB support for SC. I think we can open new issues later if anything more is needed, so I'll just close this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests

3 participants