home  wiki

Spelling: architecture

This work overlaps with that of the RFC [1], but approaches from a
different angle.

SCOPE

This document specifies an architecture to support a community
Internet Protocol network that heavily utilises IEEEEIRE, IE, EDEE, REE, EPEE, ERE, EWE, IRE, WEE, EEO, EOE, IVER, BEER, DEER, JEER, LEER, PEER, SEER, VEER, WEER, BEE, DEE, EEC, EEG, ENE, ESE, EDE, EVE, FEE, ICE, IKE, IVE, LEE, SEE, EEK, EEL, EKE, EYE, GEE, NEE, PEE, TEE, E'ER, AILEE, AIMEE, I'VE, IKEY, IVIE, IDEA, ILEA, RHEE, GHEE, KNEE, THEE, WHEE, NE'ER, E'EN 802.11 Wireless
LAN technology for connectivity.

REQUIREMENTS.

Connectivity: need to provide IPIPA, OP, UP, PI, IO, IMP, I, P, AP, KIP, PIP, RIP, VIP, DIP, HIP, LIP, NIP, SIP, TIP, YIP, ZIP, IA, IE, IR, PP, WP, II, DP, GP, HP, ID, IL, IN, IQ, IT, IV, JP, KP, LP, MP connectivity between sparsely
scattered nodes to begin with. Later deal with higher levels of
density. Support subnetssub nets, sub-nets, subunits, sublets, subsets, subunit's, sunbeds, sonnets, signets, submits, subset's, subverts, spinets, sonnet's, signet's, spinet's behind attached clients and single host
clients. Manage network resources in a 'fair' manner that recognises
the investment by infrastructure owners. Support end-to-end security
of selected communications across the network.

Scalability: engineer to support ~ 1000 node. Clear evolution paths
to higher number of nodes.

Performance: provide efficient use of radio resources, shared in a
'fair' manner that is not open to abuse.

Utilise wireless LAN commodity hardware and homebrewhome brew, home-brew, hombre, Hebrew, Homere, hombres, hombre's antenna to
provide infrastructure.

Support ruggedisedruggedest, raggediest, raggedest low cost nodes capable of outside mounting and
feasibly shared to assist in line of sight connectivity in sparse
environs.

Support higher capability nodes (that might for instance be found
within a house) mixed with low cost nodes.

IPIPA, OP, UP, PI, IO, IMP, I, P, AP, KIP, PIP, RIP, VIP, DIP, HIP, LIP, NIP, SIP, TIP, YIP, ZIP, IA, IE, IR, PP, WP, II, DP, GP, HP, ID, IL, IN, IQ, IT, IV, JP, KP, LP, MP NETWORKING TECHNOLOGIES.

* IPsec, CIPECI PE, CI-PE, COPE, CAPE, CINE, CITE, PIPE, RIPE, WIPE, YIPE
* IPv4/IPv6 mix
* OSPF?
* DiffservDiffuser, Diffusers, Differs, Diffusive, Diffuse, Diffs, Diffuser's, Duffers, Diffused, Diffuses, Diffusely, Duffer's
* Secure DNSDANS, DONS, DENS, DINS, DUNS, DNA, NS, D'S, DDS, DOS, DES, DIS, CNS, DPS, INS, ANS, ENS, DAN'S, DEN'S, DON'S, DUN'S, DIN'S, SN'S, DB'S, N'S, ND'S, DE'S, DI'S, DU'S, DY'S, DR'S, IN'S, MN'S, RN'S, ZN'S, EN'S

ISSUES

* Addressing
* Resilience to DDoSDDS, DOS, Dds, Dos, Dodos, Duos, DDTs, Dido's, Dado's, Dodo's, Duo's, Ado's, Odo's
* Security
* Connectivity without requiring too many interfaces at a node.
* Channel plans
* Antenna configuration
* Routing

OUTLINE

Seattle wireless has the concept of (A|B|C)xNodes This is perhaps
required for a longer term network architecture, but the requirements
make it difficult to build minimum expense access points that can link
to the grid initially. The concept described here attempts to present
a peer-to-peer architecture with no initial levels of hierarchy.

THE MINIMAL NODE

The basic node consists of a Linux router with either an 802.11 AP
connected via an ethernetEthernet, ether net, ether-net, eternity, Athene, ethane, otherness, Ethan, Thant, event, Ethelind, Athene's, ethane's, Athena, earned or a directly attached 802.11 interface.
This node has two functions

* to connect to the Melbourne Wireless WAN
* to offer connectivity to local nodes

* that might be wired
* or wireless

The complicating factor with a minimum node is that we attempt to use
the same wireless interface to provide support for both local wireless
clients, and connecting to distant Melbourne Wireless nodes.

WIRELESS INTERFACE MODE OF OPERATION

Two choices: we can run it in IBSSIBIS, IBIS'S, INS'S, IBO'S, ABS'S, IBM'S or BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S mode. If we run in IBSSIBIS, IBIS'S, INS'S, IBO'S, ABS'S, IBM'S
mode

* can connect to remote instances of this same type of node
* local clients must also run in IBSSIBIS, IBIS'S, INS'S, IBO'S, ABS'S, IBM'S mode
* cannot really support a normal access point on the end of an
ethernetEthernet, ether net, ether-net, eternity, Athene, ethane, otherness, Ethan, Thant, event, Ethelind, Athene's, ethane's, Athena, earned - although the OpenAPOpen AP, Open-AP, Opens, Open, Opener, Opened, Openly, Apnea, Openers, Opening, Opine, Oping, Pinup, Upend, Apnea's, Opener's [2] is a different matter.

If it is run in BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S mode

* cannot connect to remote instances of this type of node in an
ad-hoc fashion; instead the node most be configured to 'bridge' to
other nodes on a node-by-node basis (if it is even possible
* local clients can run in the normal BSSBSA, BASS, BESS, BOSS, BUSS, BS, BSD, SS, BSDS, B'S, BBS, BIS, BUS, SSS, BPS, BXS, USS, ASS, BA'S, BUS'S, S'S, SB'S, BE'S, BI'S, BO'S, ABS'S, BK'S, BR'S, OS'S, CS'S mode as found in normal
enterprise installations of wireless LAN (less fuss in configuring
wireless clients)
* can support access points on the end of an ethernetEthernet, ether net, ether-net, eternity, Athene, ethane, otherness, Ethan, Thant, event, Ethelind, Athene's, ethane's, Athena, earned connected to
the router box

TO BE CONTINUED..

* Using whoiswho is, who-is, who's, whoso, whirs, whose, woos, Wis, whiz, whys, woes, wows, whops, whees, whews, whips, whoops, Wise, wise, Whigs, whims, whisk, whist, whits, whoa, WHO, Wei's, Weiss, weirs, whizz, who, woe's, worse, his, hos, wholes, whores, whorls, Wes, was, whey's, whir, wogs, woks, wops, Ho's, Wu's, Wis's, wog's, Hi's, Whig's, Whit's, whim's, whit's, Vi's, weir's, wok's, wop's, whore's, whorl's as a network information repository like APNICPANIC, ANICA, PUNIC, APING, IONIC, EPIC, APNEA, OPTIC, INC, PANICKY, UNPICK, PANG, PINK, ANGIE, UPC, ENC, OPINE, OPING et. al.
* Benefit of (globally unique) IPv6 based services when
interconnecting community WANsWains, Wanes, Warns, Weans, Awns, Wands, Wanks, Wants, Wand, Wan, Was, Ans, Vans, Wens, Wins, Swans, Wane, Wars, Ways, Dans, Hans, Kans, WATS, Wacs, Wang, Bans, Cans, Fans, Mans, Nans, Pans, Sans, Tans, Wads, Wags, Wank, Want, Wain's, Awn's, Van's, Win's, Wen's, Ewan's, Wang's, Swan's, Wand's, Way's, Wyn's with NAT and Internet wormholes
* Benefit of IPv6 A6 chain records for hierarchical reverse DNSDANS, DONS, DENS, DINS, DUNS, DNA, NS, D'S, DDS, DOS, DES, DIS, CNS, DPS, INS, ANS, ENS, DAN'S, DEN'S, DON'S, DUN'S, DIN'S, SN'S, DB'S, N'S, ND'S, DE'S, DI'S, DU'S, DY'S, DR'S, IN'S, MN'S, RN'S, ZN'S, EN'S and
renumbering
* Conversely the problem of allocating out /28s and inverse DNSDANS, DONS, DENS, DINS, DUNS, DNA, NS, D'S, DDS, DOS, DES, DIS, CNS, DPS, INS, ANS, ENS, DAN'S, DEN'S, DON'S, DUN'S, DIN'S, SN'S, DB'S, N'S, ND'S, DE'S, DI'S, DU'S, DY'S, DR'S, IN'S, MN'S, RN'S, ZN'S, EN'S
delegation



Links:
------
[1] http://melbourne.wireless.org.au/?RFC
[2] http://melbourne.wireless.org.au/?OpenAP

[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]

> home> about> events> files> members> maps> wiki board   > home   > categories   > search   > changes   > formatting   > extras> site map

Username
Password

 Remember me.
>

> forgotten password?
> register?
currently 0 users online
Node Statistics
building130
gathering193
interested492
operational241
testing205