The next generation of networking: A globally-scalable distributed mesh of streams

The TCP/IP Internet has:

  • High and Unbounded Latency
  • Wasteful, Underused Links
  • Limited Node/Switch/Hop Counts (no IoT support)
  • Low Redundancy
  • A Tendency to Centralize Power
  • Choke-point Surveillance and Censorship
  • Disaster Vulnerabilities
  • Tragedy of the Commons

What follows is a free and open proposal for a solution: A new globally-scalable network protocol with a mesh topology. Instead of being limited to traditional address-routed packets, the protocol uses source routing to set up bounded-latency isochronous streams avoiding the problem of congestive collapse. Once a stream is set up, the route is given a numeric name to support routing micro-packets (µPkt) both directions along the route. In order to support isochronous streams across the entire network, the framerate of every link is a power of 2 frequency relative to TCG time, this opens the door to many new scenarios that require precise relative timekeeping. Micro-payments in arbitrary settlement instruments, which are made ‘by simple agreement’ between each neighbor along a route, are used to pay for sending data across the network, avoiding the Tragedy of the Commons. Client endpoints are responsible for building up multi-path redundant link maps through the network, relying on the advertised 3D-Geohash locations of the nodes to track only a subset of nodes within a given area; providing scalability, redundancy, and wider distribution of power. Contrasted with TCP/IP, the new protocol stack’s layering model provides additional options for streams, packets, safety, reliability, robustness, latency, and extensibility. Most importantly, the entire protocol was morally designed with its socioeconomic side-effects as a guide.

IsoGrid Protocol Specification v0.215.


CC0

To the extent possible under law, Travis.Martin has waived all copyright and related or neighboring rights to:
IsoGrid Protocol Specification v0.215.
This work is published from: United States.

This document is an early draft. If you’d like to help improve it, check out the IsoGrid Forum.

uPkt IsoStream and EccFlow Spec Changes

As I previously promised, here are the big updates to the IsoGrid Protocol Spec.

This version includes:

  1. Major uPkt Network Layer updates.
  2. Major IsoStream Transport layer protocol specification using uPkt Network layer.
  3. More complete specification for EccFlow Session layer protocol.
  4. Removal of IsoGrid Headers (not needed anymore).

As always, if you’d like to discuss or contribute, head over to the IsoGrid Forum!

The requirements doc hasn’t been modified:
IsoGrid_Requirements_v1_002

The Spec has been updated:
IsoGrid_Protocol_Specification_v0_210


CC0

To the extent possible under law, Travis.Martin has waived all copyright and related or neighboring rights to:
IsoGrid Protocol Specification v0.210.
This work is published from: United States.