JUPITER System

The JUPITER system stands for

**JU**st **P**roviding **I**nternet **T**hrough **E**ternal **R**elays.

JUPITER replaced the 802.xx internet standards in 2037, after replacing the undersea cable structure with its proprietary structure. JUPITER is primarily built with redundancy in mind, where the undersea cables no longer just travel in a straight line. Instead, imagine the lines on a soccer ball, where each vertex is a switchboard. Each switchboard is at least several hundred miles apart from eachother. In the event of one of those switches having issues, or the cable between two nodes being severed, the JUPITER system is designed to use OSPF (Open Shortest Path First) protocols in order to efficiently route traffic around the severed line. The JUPITER system allowed for terabit fiber speeds to travel through its cables, primarily due to the specifications of JUPITER's main investor, CrypTon.

CrypTon had these specifications for their own WAN subnet, CPTN:x:x:x, which is used primarily for transactions. The second octave is for a country, third for a specific region, where it is then assigned its own local subnet. The last octave will dictate whether it is for individual, private, or internal use. The main address for a city will have its own local WAN server that supplies a certain region. For example, the CrypTon Distribution Centre (CTDC) host in Seaoko has the address of

```
CPTN:USOA:SOKO:CTDC

```

Notice how a JUPITER address does not rely on numbers or hexadecimal like the old IPv4 or IPv6 standards, rather it has 512 bits which allows for it to translate an address. Simple as it may seem initially, that address is only available to a human's comprehension. The actual address can reach sizes of up to 2056 bits, because each address is translated into its own unique address when it is forwarded to a distribution frame. That address is not comprehensible to a human, and can only be calculated by a computer. That unique address goes to each and every device, which can both act like a MAC address and a public IP address.

There are numerous security flaws with this approach, most notably that the JUPITER switches do not act like a NAT, which means that a local address is public. Normally, sending a message through a gateway would have the local address be replaced by the gateway's address, which would obscure the local host's address, because its implementation was created out of necessity from IPv4's rather limited pool of available addresses of roughly 4 billion. However, a routed WAN connection to a hub will then serve as the connecting address to a device or network, which is then appended to the address of the hub. Connecting to a terminal inside a facility in Amsterdam would look like

```
TPRK:NTLD:AMDM:HEDQ//2871:ff13:p8u6:DOLE

```

Note that the last octave inside the device's address is in letters. This serves as the OUI for a vendor, in this case the terminal was manufactured by Dole Computers. JUPITER has more assignable addresses than IPv6 did, and IPv6 was never fully rolled out before JUPITER's inception. There are less stars in the known universe than the amount of addresses that JUPITER can assign. 2^512 is approximately 1.340781e+154 possible addresses, which we would never have to worry about filling out before the universe ends.

Oh, and don't worry, unless if you're an IT monkey like I am and is subjugated to deal with this mess of numbers and letters every waking moment of my existence, DNS servers still exist.

1. ↑ *"We've waited 42 YEARS for IPv6 to become widely adopted, and then strolls along THIS MONSTROSITY!?"* - Jake Kormak