Design Geneaology and Methodology

All computer networking protocols involve, at their core, a connection
between at least two computers. The internet works by passing data
packets between computers, such that a chain of links are utilized to
transport data far from its origin. The internet is intended to function
as close to real-time as possible, and thus the networking systems are
built upon a very lightweight packet protocol. The weight of the
technical understanding required to properly implement these protocols
is in the eye of the beholder, however.

For two computers to connect, electrical signals must be transmitted
between them. The computers of the world are connectable by wires, for
the most part. But these wires are under the control of telecommunications
companies, and not only must a subscriber pay a fee, but this centralized
control is subject to sabotage by rogue agents. Long range wireless
communications are strongly restricted and curtailed by regulatory
agencies. There are very few open frequencies available to unlicensed
users. And as such, long range wireless communications are generally
unavailable for free, failsafe usage.

Due to the aforementioned circumstances, direct long distance real-time
networking that is legally permissible and overcomes these obstacles is an
impossibility. Short range real-time networking is possible due to private
wires, a few unrestricted frequency bands, and other special technologies.
With these restrictions in mind, it is the author's intent to make the most of
what is available to create an effective long range networking system, while
maintaining his personal computery philosophies.

These philosophies will require that:

1. The system cannot discriminate. It must be suitable for actual
application upon any computing device, regardless of how old or how new.
This means that it must be useful regardless of speed or interface, and
that it must run on all platforms. While the preferred implementation
will rely upon well-proven technologies such as TCP/IP, interfaces and
engines can be implemented to directly translate the data for the most
primitive of needs.

2. Upgrades will never be required, yet users are not required to use
the protocol in its original form. Those who decide to use drastically
modified implementations will be choosing to restrict themselves as to
who can receive their transmissions.

3. There must be astoundingly simple principles applied for the creation
of the system. Complexities just make a mess, particularly in technology.

4. Any possible means of transmitting data are to be useable. Even to the
extreme extent of physically transporting a disk from one location to another.

5. It doesn't matter if it has already been done at some point, as it is
not readily available for instant application.

This implies that the system will seem more like a methodology than what
usually passes as a networking protocol.


In the early networking days, a modem could be used to connect to a BBS.
E-mail was then available to those who chose to connect to such a system.
Long distance e-mailing was available with a short-distance telephone call
by utilizing a BBS that participated in a system like FidoNet. A BBS
that participated in this system would generally make a call to the next
area code in the night to transport a package of e-mails that were headed
in that direction. The next BBS would then relay those e-mails, so on and
so forth, until the e-mail crossed the country.

This protocol will use a similar system, excepting that modems are not
required (though they can be used!) and BBSes will be unnecessary.

High level protocols and systems will serve as the backbone of the
system, though they are not necessary to its survival. The methodology
itself is what is guaranteed to be "lightweight", and the author does
not care if eggheads choose to claim that it is trivial.

Data shall spread like a disease.


Return to the main page.

Hermann L. Johnson. January 2019. Free for unmodified redistribution and non-commercial use.