prev. article next article

centralized vs decentralized infrastructures

6 Jun 2009

today i thought about wireless lan an the upcoming wlan standard 802.11s [1] with the newcomer technology called ‘mesh networking’ [2], [3]. i just then realized that before you can deploy a decentralized infrastructure you have to first specify the solution using a centralized infrastructure. i give you some examples:

what might be new for most users out there is the 802.11s draft for wireless lan since it is the transformation of a centralized network into a decentralized one.

let’s recover: in an infrastructure network two client nodes relay on a access point (ap) and all the communication is going trough that ap. client a pings client b then means: a sends the ping to client b to the ap. the ap sends the ping to client b. b then creates a ping reply to client a and sends it to the ap. the ap then relays the reply to client a. this mode has its advantages as well since it is easier to implement than what has been done in 802.11s called ad-hoc.

in ad-hoc mode two clients can now communicate directly. but again they can also use the access point which is running in ad-hoc mode as well (not in infrastructure mode), to relay their data. the decision what route to take is done by a routing algorithm. as far as i know a lot of effort to get that standard working was made by the olpc developers.

i’m very happy to see this standard emerging. this topology is an urgent requirement. why?

still i see security issues since there is no pki (public key interface) for 802.11s yet. still one could use a radius server but this voids the idea of a decentralized network.

summary: before a problem can be decentralized there must be one instance or solution of the problem in a centralized fashion.

if you find any pattern which breaks this, please let me know!

#links * [1] * [2] * [3]