Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr>,
	make-wifi-fast@lists.bufferbloat.net,
	"babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [Babel-users] perverse powersave bug with sta/ap mode
Date: Thu, 28 Apr 2016 10:16:48 -0400 (EDT)	[thread overview]
Message-ID: <1461853008.891910506@apps.rackspace.com> (raw)
In-Reply-To: <878tzx4zno.fsf@toke.dk>

Discovery is a special case, that is not quite multicast. Discovery is "noticing".  A node wishing to be discovered must be noticed by one (or maybe more) already existent stations in a group (groups are noticed by any member being noticed by a member of another group).

So you don't need any facility to "reach all" in one message.  It's sufficient to "reach any". From that point on, it's a higher level problem of "association management" (tracking members and their reachability).  I use these general terms in quotes to step outside the frame limited to 802.11 and its rigid culture.

So the key to discovery is *anycast* not multicast.

So for example, a station that is not yet associated could follow some predictable sequence of transmissions, using a variety of MI transmissions (multiple input, i.e. multiple antennas transmitting simultaneously) with a variety of waveforms, where that sequence was determined to have a high probability of being noticed by at least one member of the group to be joined. A station noticing such a signal could then use the signal's form itself to respond and begin to bring that station into the group of stations that can hear each other, discovering further information (like mutual propagation characteristics (multipath/MIMO coefficients, attenuation (for equalization), noise)).

By conflating discovery with multicast, one loses design options for discovery and cooperative transmission. So yes, the "normative" centralized access point discovery now practiced in 802.11 nets assumes a sort of "multicast", but that is because we have "centralized" architectures, not mesh at the phy level.

On Thursday, April 28, 2016 9:43am, "Toke Høiland-Jørgensen" <toke@toke.dk> said:

> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> writes:
> 
>> For discovery, multicast is unavoidable -- there's simply no way you're
>> going to send a unicast to a node that you haven't discovered yet.
> 
> Presumably the access point could transparently turn IP-level multicast
> into a unicast frame to each associated station? Not sure how that would
> work in an IBSS network, though... Does the driver (or mac80211 stack)
> maintain a list of neighbours at the mac/phy level?
> 
> -Toke
> 



  reply	other threads:[~2016-04-28 14:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 23:18 [Cerowrt-devel] " Dave Taht
2016-04-26 23:27 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
2016-04-26 23:32   ` David Lang
2016-04-28 13:10   ` dpreed
2016-04-28 13:37     ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:43       ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] " Toke Høiland-Jørgensen
2016-04-28 14:16         ` dpreed [this message]
2016-04-28 14:59           ` Juliusz Chroboczek
2016-04-28 15:44             ` Dave Taht
2016-04-28 16:09               ` Dave Taht
2016-04-28 17:10               ` [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Juliusz Chroboczek
2016-04-28 17:46                 ` Dave Taht
2016-04-28 17:53                   ` [Cerowrt-devel] [Babel-users] " Henning Rogge
2016-04-28 18:46                   ` [Cerowrt-devel] Multicast IHUs Juliusz Chroboczek
2016-04-28 18:04                 ` [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Dave Taht
2016-04-28 17:28               ` [Cerowrt-devel] Layering " Juliusz Chroboczek
2016-04-28 15:04         ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] perverse powersave bug with sta/ap mode moeller0
2016-04-28 16:05           ` [Cerowrt-devel] [Babel-users] [Make-wifi-fast] " Henning Rogge
2016-04-28 16:52             ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] " Dave Taht
2016-04-28 16:59               ` Henning Rogge
2016-04-28 18:54           ` Juliusz Chroboczek
2016-04-28 19:12             ` [Cerowrt-devel] [Babel-users] [Make-wifi-fast] " Henning Rogge
2016-04-28 19:29               ` Juliusz Chroboczek
2016-04-28 19:33                 ` Henning Rogge
2016-04-28 19:55                   ` Juliusz Chroboczek
2016-04-28 13:33   ` Juliusz Chroboczek
2016-04-28 13:32 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-05-12  0:28 ` [Cerowrt-devel] " Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1461853008.891910506@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jch@pps.univ-paris-diderot.fr \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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