Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Luis Carlos Cobo <luisca@cozybit.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Javier Cardona <javier@cozybit.com>
Subject: Re: mesh beaconing questions
Date: Tue, 26 Feb 2008 16:54:19 +0100	[thread overview]
Message-ID: <1204041259.13162.247.camel@johannes.berg> (raw)
In-Reply-To: <1204040528.30146.44.camel@localhost.localdomain> (sfid-20080226_154432_804140_8257168D)

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]


> > 2. The Draft states to use either procedures 11.1.2.2 (IBSS) or 11.1.2.1
> > (infrastructure). It is easy to "port" 11.1.2.1 to mesh, but 11.1.2.2
> > reads like this:
> 
> Next question, more relevant to how this affects the user:
> 
> What's the meaningful difference between these two choices?  When would
> you use one and when would you use the other?  Should the user (ie, a
> user of something like NetworkManager) care whether a particular node is
> doing IBSS or infrastructure beacons?

Good point. I guess the relevance is that the IBSS mode requires less
power because you don't have to transmit every beacon? There's a *lot*
of text in the Draft about beaconing/synchronization and not having
TBTTs at the same time between different STAs and whatever though so
maybe there's more to it.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-02-26 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 14:07 mesh beaconing questions Johannes Berg
2008-02-26 15:42 ` Dan Williams
2008-02-26 15:54   ` Johannes Berg [this message]
2008-03-05  5:37 ` Javier Cardona
2008-03-05  9:35   ` Johannes Berg

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=1204041259.13162.247.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=javier@cozybit.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luisca@cozybit.com \
    /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