If MaidSafe/SafeNetwork is to be truly separate, free of oppressing forces , rent Spectrum or Fibre to create a backbone and stop using UDP/IP & TCP/IP all together.
The way to do this is design the entire system to function as an OSI Layer 5 Application Network over top of SCTP, which interconnects all Nodes in the Application Network(and is multihomed highly available with UDP like msg capabilities built in)
The secret sauce imo to scale securely in creating such a brave new world is to use upper layer/lower layer “2X Stacked” OSI Layer3 ‘Split Addressing’ that makes use of private addressing in URL form (No more OSI Layer 4), also replacing all routing and DNS functions with a modified Location ID Separator Protocol variant implementation based what would be a MaidSafe developed LISP-DDT-Mapping Service transform ,
This time modifying such FOSS to in parallel, run existing IPv4/IPV6 Mapping as the Control Plane only, yet also run a “ships in the night” instance on the same node which only makes use of ICAF Type of MaidSafe URL LISP Endpoint Resource Locator Path “ELP” Mappings as nextgen form of servicing system or device client GROPE/RIG lookups to the MapReg of LISP-DDT-MS, with MapResolve and connections across the spectrum/fibre suggested. Run all the ERT, IRT and MCast Routers into NamedSpace Zones of LISP as contianerD deployable instances (no need for router iron).
go to Lispers.net to learn more Dino F. who runs lispers.net invented LISP at Cisco in 2006 officially, although as early as 1994 there were heated debates about it at cisco. Dino maintains the most recent form of LISP on gitbub. He invented it as a way at Cisco as a way to replace IP routing Tables with “IP stacked over IP split addressing”, They would not listent at first, hel left went to Porcekt for 5 years, then Cisco bought Procket and they woke the LISP effort bsack up in 2006. LISP has been ready to go imo as early as 2013.
The secret sauce is CXL2.0 running on PCIeGen5/6 in the Colos hosting Safe Network Nodes. the CXL2.0 Logical device connectivity requires a kernel driver build to advertise presences, do Map Service Lookups and act as the ELP actuator, where the Logical block Device to which the App Instance Layer 5 node writes is system /or device agent published to the HOS as a mount point representing a symbolic link block device, essentially a locale device which is mapped to the ELP upper layer address LD destination (Storage, mem, another process/app, etc…) . The Symbolic link/label representing the cxl2.0 LD using the ICAF Type URL+cxl LD hybrid address format is reflected by the NIC IF daemon into the System or SNIC offload Device Linux Host operating System.
This split addressing makes the upper-layer URL+cxl2.0LD hybrid address form latche to the App Network instance Unix Socket or SCTP port at OSI Layer 5 a completely reconfigurable and mobile geo-locatable relationship, where as the system/device client (kernel driver) paired underlayer URL+cxl2.0 LD Address is latched/fixed to the underlying OSI L2 Linklayer MAC address which represents the embedded bonded ETH OSI L1 media
Windows support? Install/Run these instances as Guest OSes in VMs on KVM Hypervisor and install Linux as the Host OS, its what MS Azure does nayway with Windows II in the cloud…
I am glad to discuss the details, with anyone at Maidsafe/SafeNetwork who can grasp what I am presenting here and why its so important, if you truly want to be free, be free of IP.
To go between LISP-DDT-MS NamedSpace Zones hosting DCs or Colos, transform the “Uberlayer” address mapping model of LISP-DDT-MS to make use of a SafeNetwork created ICAF Type URL+Cxl2.0 Hybrid Address EndPoint to ‘external’ IP4/IPv6 RouteLocator Hybrid inter-ELP Mappings to make use of existing multi-provider inter-DC WAN MPLS tunnel services over IP (or possibly VXLAN), or alternatively do same with FlexE for Metro Interconnect.
David, if you Truly want SAFE NETWORK to be free and private get your OSI Layer 3 Split Addressing act together on your or fork of LISP-DDT-MS and design, develop,deploy as above.