netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hong Liu <hong.liu@intel.com>
To: Jouni Malinen <jkm@devicescape.com>
Cc: Jiri Benc <jbenc@suse.cz>, netdev <netdev@vger.kernel.org>
Subject: Re: about 802.11i IBSS support
Date: Thu, 26 Oct 2006 10:47:24 +0800	[thread overview]
Message-ID: <1161830844.9670.13.camel@devlinux-hong> (raw)
In-Reply-To: <20061025154815.GA15348@instant802.com>

On Wed, 2006-10-25 at 23:48, Jouni Malinen wrote:
> On Wed, Oct 25, 2006 at 04:54:41PM +0800, Hong Liu wrote:
> 
> > I am reading the 802.11i IBSS spec and
> > trying to find if it is OK to add patches to d80211 to support this feature.
> 
> Large parts of this will be outside d80211, but yes, I think d80211
> should be made ready to support this (mainly in the multiple group keys
> area).
> 
> > When a STA (say S1) joins in an IBSS network with N STAs,
> > it must negotiate keys with all N STAs.
> 
> I don't think it is required to negotiate keys with all STAs of the
> network unless it actually needs to communicate with them, i.e., there
> may be cases where it is not needed to send or receive data from some of
> the nodes.

This may add complexity to the implementation.

If the STA wants to send broadcast data, it must distribute its group
key to all other STAs, and then it can send out the packet.

For RX, if it receives data from other STA it needs to find out whether it
has finished key negotiation with that STA. And it can not decrypt the data
until key negotiation is finished.

If we negotiate keys at the beginning, things will be simple.
But the cost is we may negotiating keys with STAs we may not communicate with.

Thanks,
Hong

  parent reply	other threads:[~2006-10-26  2:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25  8:54 about 802.11i IBSS support Hong Liu
2006-10-25 13:05 ` Michael Buesch
2006-10-25 15:48 ` Jouni Malinen
2006-10-25 19:59   ` Simon Barber
2006-10-25 21:46   ` Johannes Berg
2006-10-26  2:47   ` Hong Liu [this message]
2006-10-26  3:26     ` Simon Barber

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=1161830844.9670.13.camel@devlinux-hong \
    --to=hong.liu@intel.com \
    --cc=jbenc@suse.cz \
    --cc=jkm@devicescape.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).