[MLB-WIRELESS] Re: Node x is over this way -was- Applications

[Ben Anderson]

Err, not all of it.  It only deals with ip-ip tunneling to allow a user to
roam between networks while still having all their data routed back through
the home network.  This is neither efficient or optimal for our bandwidth
limited use.

and it has no QoS, no scaling, no concept of each node routing traffic for
other nodes...  no broadcast discovery...  The list goes on.

Ben.

> all of this has been addressed. check out Cisco's MobileIP.
>
> routers are set up with a whole other logical addressing layer and
> clients can move between physical networks whilst keeping the same IP
> and hence the same applications/sessions.
>
> -----Original Message-----
> From: Tony Langdon [mailto:tlangdon at atctraining.com.au]
> Sent: Wednesday, 20 March 2002 9:19 AM
> To: 'Clae'; Ben Anderson
> Cc: melbwireless at wireless.org.au; jon at webprophets.com.au
> Subject: RE: [MLB-WIRELESS] Re: Node x is over this way -was-
> Applications
>
>
> > darn those roaming nodes :-)
> > i have a hunch there's a way around that,
>
> Well, I have wondered is it's possible to have an addressing scheme
> that's
> split into two components - the "network location" and the "station ID".
>
> The scheme works like this:
>
> For routing purposes, the network ID is used to decide which node to
> send
> packets to.
>
> For applications, they are only interested in communicating with the
> device,
> so they only talk in terms of the station ID.  However, the network sees
> the
> packet address of having an address of network ID + station ID.
>
> For fixed stations, they are configured with a fixed, non zero network
> ID
> (or can be assigned one by a transform from things like GPS
> coordinates).
> Each AP/routing node would have its own network ID, and the mojo system
> annd
> the rest would still work.
>
> Mobile stations would have a network ID of zero, which means "Get my
> network
> ID from the nearest AP").  Their node ID would be non zero and unique,
> just
> as in the case of routing nodes.
>
> There might be a bit of broadcasting required when nodes move ("Is
> Station
> xxxxxx out there"?), but once a connection is established, and/or nodes
> have
> cached the location information, the routers would automatically attach
> the
> mobile node's temporary network ID to the station ID for routing
> purposes...
>
> Make sense?
>
> Clear as mud?
>
> :)
>
> This correspondence is for the named person's use only. It may contain
> confidential or legally privileged information or both. No
> confidentiality
> or privilege is waived or lost by any mistransmission. If you receive
> this
> correspondence in error, please immediately delete it from your system
> and
> notify the sender. You must not disclose, copy or rely on any part of
> this
> correspondence if you are not the intended recipient.
>
> Any opinions expressed in this message are those of the individual
> sender.
>
>
> --
> To unsubscribe, send mail to minordomo at wireless.org.au with a subject of
> 'unsubscribe melbwireless'
> Archive at:
> http://www.wireless.org.au/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
> IRC at: au.austnet.org #melb-wireless
>
>
> --
> To unsubscribe, send mail to minordomo at wireless.org.au with a subject of
'unsubscribe melbwireless'
> Archive at:
http://www.wireless.org.au/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
> IRC at: au.austnet.org #melb-wireless
>


--
To unsubscribe, send mail to minordomo at wireless.org.au with a subject of 'unsubscribe melbwireless'  
Archive at: http://www.wireless.org.au/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
IRC at: au.austnet.org #melb-wireless