Hey! Keep Your Hands Out Of My Abstraction Layer!
Posted: 05-15-2006, 05:37 AM
why so many network standards seem to enjoy transgressing the
boundaries of their abstraction layers. For instance, 802.11 keeps
hinting that they are helping to solve the mobility problem, but also
keeps issuing disclaimers throughout the document saying essentially,
"We don't specifiy how its actually done."
I wonder...is there a more appropriate to look at the networking stack?
Do the wireless options that we have available now do too much in ways
that are inappropriate or misleading? For example, 802.11 has an ESS
feature that implies that its wireless LANs can grow arbitrarily large.
Has anyone use this in this way? Has anyone tried to implement
mobility over a massive interconnection of 802.11 LANs?
Then there is Bluetooth, whose specification I have not read, but had a
glimpse of it a few years ago. It gave me the impression that someone
showed little restraint in feature provision. I was so impressed that
I waited for it to port my luggage off the aircraft.
Zigbee? I got the same impression. Not horrifically complicated, but
not exactly bare-metal.
Perhaps that's the problem. Perhaps we should not be putting so many
"services" in the hardware.
How about a wireless transceiver that does as well as it can at layers
1 & 2, then ***STOPS***. No security (beyond link-access-control).
Power-management facilities available but minimally specified.
Link-layer addresses *only*. No "services". No mention of printers,
PDA's, kiosks, users, clouds, networks. No notion of a world-wide
network. The ideal link-layer device would get data from interface A
to interface B and get out of the way.
I think if each layer were approached with this mindset, we'd actually
do better than we have done so far.
-Le Chaud Lapin-



Linear Mode

