From: Szymon Janc <szymon.janc@tieto.com>
To: Mike Tsai <Mike.Tsai@atheros.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCHv4 0/7] Support for out of band association model
Date: Mon, 6 Dec 2010 10:46:09 +0100 [thread overview]
Message-ID: <201012061046.09668.szymon.janc@tieto.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F98406D68D125@SC1EXMB-MBCL.global.atheros.com>
Hi,
> [Mtsai correction]
> The local OOB data present is set when host send HCI command "Read Local OOB
> Data". And this "OOB data present" flag is sent over the air to peer device
> during pairing.
I think you confused local and remote OOB data.
This flag is about "OOB authentication data from remote device present".
Please see Vol.2 Part E. 7.1.29 "IO Capability Request Reply Command".
--
Szymon Janc
on behalf of ST-Ericsson
prev parent reply other threads:[~2010-12-06 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 10:53 [PATCHv4 0/7] Support for out of band association model Szymon Janc
2010-11-23 10:53 ` [PATCHv4 1/7] Add support for Out of Band (OOB) " Szymon Janc
2010-11-23 10:53 ` [PATCHv4 2/7] Add D-Bus OOB plugin Szymon Janc
2010-11-23 10:53 ` [PATCHv4 3/7] Add D-Bus OOB API documentation Szymon Janc
2010-11-23 10:53 ` [PATCHv4 4/7] Add simple-oobprovider for testing Szymon Janc
2010-11-23 10:53 ` [PATCHv4 5/7] Add request for accepting incoming pairing requests with OOB mechanism Szymon Janc
2010-11-23 10:53 ` [PATCHv4 6/7] Update D-Bus OOB API with RequestPairing method Szymon Janc
2010-11-23 11:05 ` Szymon Janc
2010-11-23 10:53 ` [PATCHv4 7/7] Add RequestPairing method in simple-agent for accepting incoming OOB pairing requests Szymon Janc
2010-11-30 16:02 ` [PATCHv4 0/7] Support for out of band association model Mike Tsai
2010-11-30 21:26 ` Mike Tsai
2010-12-06 9:46 ` Szymon Janc [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012061046.09668.szymon.janc@tieto.com \
--to=szymon.janc@tieto.com \
--cc=Mike.Tsai@atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox