AnchorForMobile Pattern

I’m spending most of my spare time working on updates to the spec, here’s a preview of some of what I’ve been working on:

AnchorForMobile Pattern

It doesn’t seem possible to have scalable route determination with a mesh of switches that relies heavily on dynamic links. As such, long-distance data transport will mostly occur over switches with reasonably persistent links, or at least predictable links (like satellites). A cell tower or a Wi-Fi router are typical examples of switches with highly transient links, and as such, endpoints with highly transient links are generally just called mobile nodes. Fortunately, relying on highly transient links for only a few hops can be scalable. A simple way to achieve scalability is to allow for layers of indirection, where data flowing to and from a mobile node is routed through one or more persistent link tunnel(s) with stationary anchor nodes.

Each anchor node MAY:

  1. Answer the question: “Where is the mobile endpoint?”
    1. Which IsoGrid nodes is the mobile endpoint near?
    2. What are the best routes to get to the mobile endpoint?
  2. Provide credit payments as needed to sustain the mobile node’s outbound streams
  3. Provide a link tunnel to, from, or through the mobile node

In this AnchorForMobile pattern, the anchor node and the mobile node maintain an Session layer ‘flow’ between each other and use it as the link layer underlying an IsoGrid network link. This is only a suggested pattern, and the specific protocol does not need to be universally supported: The only requirement is that the mobile and anchor nodes MUST agree to use the same protocol.