From: "Tim Monahan-Mitchell" <tmonahan@codeaurora.org>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ mailing list" <linux-bluetooth@vger.kernel.org>
Subject: AMP Key Management Simplification?
Date: Tue, 9 Mar 2010 23:06:15 -0600 (CST) [thread overview]
Message-ID: <e8dc052360dd27d2ac7460d359e7645c.squirrel@www.codeaurora.org> (raw)
Hi Marcel,
A discussion was missing from our original posting ("QuIC's AMP + eL2CAP
Technical Plans"), regarding AMP Keys.
We would like to defer the ability to work with more than one AMP device
type initially, since doing so would necessitate having to persist the
Dedicated AMP Keys for each AMP device type. Is this approach acceptable?
Limiting the initial design to a single AMP device, the Dedicated AMP key
can be generated any time from the associated link key.
I can provide more details as to why if needed (refer to 8.1 & 8.2 in the
Core spec).
Thanks,
Tim Monahan-Mitchell
Qualcomm Innovation Center, Inc.,
A member of the Code Aurora Forum
reply other threads:[~2010-03-10 5:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e8dc052360dd27d2ac7460d359e7645c.squirrel@www.codeaurora.org \
--to=tmonahan@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).