[governance] Uni.X to Uni.X .NETworking 64-bit Address Naming

[Jim Fleming]

Given the 160 bit message format:
0101.0101.SSSSDDDD.000000.LLLLLLLLLL
SSSSSSSDDDDDDD.SD.DDSS.SSSSSSDDDDDD
SD11GTTT.PPSSSDDD.CCCCCCCCCCCCCCCC
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

The 0101.0101 can evolve to SSDD.SSDD.
The 000000 can evolve to SSSDDD.
The SD11 group evolves to SDSD.

Eventually the bits end up in a 64-bit string with some as PREFIX and some
as a SUFFIX for the 32-bit field. With 16 bits as a PREFIX and 16 bits as a
SUFFIX, the 32-bits will be on a 4-bit
boundary.

In order to obtain your FREE 64-bit address space prefix, all you have to do
is select a UNIque 16 letter domain name. The 16 letters include the DOT (.)
The 16 letters are selected from the following 16-symbol set.
.CDEIMNOPRTUV389

Since .COM and .NET are part of the symbol set, many names can be selected.
You can place a .COM or .NET in any 16-bit field. You could have it as a
PREFIX
on the left or a SUFFIX on the right. Many other symbolic fields that look
like TLDs
are possible.

The 0101 pattern would map to the letter M below. The 0000 pattern to a DOT.
There could be several DOTs next to each other for a long string of 0s. The
mapping
to letters can allow you to more easily remember a unique name and address
and
also to register it in a dynamic or static registry. One can also take a
64-bit value and
determine the name it maps to. The name may look like a domain name because
of
the DOT and the .COM and/or .NET. It is just a symbolic name for a free
address
space allocation. You can toss in an R with a circle around it to make it
look official.

0000 0 .
0001 1 C
0010 2 D
0011 3 E
0100 4 I
0101 5 M
0110 6 N
0111 7 O
1000 8 P
1001 9 (R)
1010 A T
1011 B U
1100 C V
1101 D 3
1110 E 8
1111 F 9

Note: In the object-oriented system that will eventually be released, the
64-bit addresses
are addresses of nodes and the 160-bit key values are object handles. A 5
bit symbol set
for naming the 160-bit keys allows for 32 letter names. A Key @ Node
arrangement
results in a 160-bit key used @ a node with a 64-bit address. It is sort of
like virtual
memory (or virtual object store) with a 224 bit address.

Uni.X to Uni.X .NETworking may look at little like IP packet communication
but it is part
of a much larger and more complete system of communicating processes and
objects
with messages (methods) and a language that ties it all together.
Communicating objects
are essentially "smart data". It is handy to be able to name the objects.
The names can be
free and the data can take on a life of its own. Who knows, maybe the
objects can be
programmed to govern themselves. Removing the human element from the process
may
make things run more smoothly. The low-cost Uni.X nodes could be solar
powered and
run and run and run with wireless connections. Documents could be stored
there that are
censored by THE Big Lie Society or re-written and claimed to be their work.
Uni.X is
sort of interesting, it pre-dates many of the people who now claim to have
invented things
that existed in the 70s and 80s. Historians seem to have major blind spots,
thanks partly
to THE Big Lie Society. That will likely get worse as THE Big Lie Society
rolls out the
next level of censorship and layering to obscur their activities as they
lock-down the .NET.

_______________________________________________
governance mailing list
governance at lists.cpsr.org
https://ssl.cpsr.org/mailman/listinfo/governance