On Sun, Jan 25, 2015 at 12:17 PM, <dpreed@reed.com> wrote:

> There is no reason why one cannot set up an enterprise network to support
> roaming, yet maintaining the property that IP addresses don't change while
> roaming from AP to AP.  Here's a simple concept, that amounts to moving
> what would be in the Ethernet bridging tables up to the IP layer.
>
>
>
> All addresses in the enterprise are assigned from a common prefix (XXX/16
> in IPv4, perhaps).  Routing in each access point is used to decide whether
> to send the packet on its LAN, or to reflect it to another LAN.  A node's
> preferred location would be updated by the endpoint itself, sending its
> current location to its current access point (via ARP or some other
> protocol).   The access point that hears of a new node that it can reach
> tells all the other access points that the node is attached to it.
> Delivery of a packet to a node is done by the access point that receives
> the packet by looking up the destination IP address in its local table, and
> sending it to the access point that currently has the destination IP
> address.
>

I'm not familiar with routing protocols.  Do any of the current ones do
this, or is this an idea for a new protocol?

-Aaron