[governance] Uni.X to Uni.X .NETworking - Be Careful With the SDSDGTTT Bits

[Jim Fleming]

SSDD.SSDD.SSSSDDDD.SSSDDD.LLBBBBBBBB
SSSSSSSDDDDDDD.SD.DDSS.SSSSSSDDDDDD
SDSDGTTT.00SSSDDD.CCCCCCCCCCCCCCCC
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

Contrary to what some people think or have been told, messages can
change as they move from the Source to the Destination. They also take
time to move.

Two major changes occur in messages as they move from S to D.
The hop-count is reduced and because it changes the check-sum has
to be updated. The second change once was expensive for software to
do, it can now be done in hardware or with clever algorithms.

When setting the SDSDGTTT bits when a message is created to 00110111
you are hoping the message will arrive before the hop-count of 7 (111) is
reduced to 0 and the message disappears.

If you are on an old legacy 32-bit research system, you might find that your
message burns thru the G bit, the Guard Bit (or Global) bit and when the
message arrives it will not have the SD set to 11. The addressing has been
automatically changed, in-transit, depending on the distance traveled.

Even though the SD bits look like they could be 00, 01, 10, and 11, there is
merit in making the assumption that they can only be 00 or 11. That allows
the
destination node to better deduce if old legacy systems were in the middle
and used to transport the messages.

The left-most SD bits will always start and end as 00 because the old legacy
systems will not touch them in their de-powered state. They can be very
carefully
used in local systems and closed walled-gardens where routing policies and
the
nodes can all be 100% aware of the contents. They are part of the 64-bit
addressing
to make them easy to control, but for most applications will be 0.

When the G bit is set to 1, you boost the power in the message. It can
travel
farther, but the G bit may still be 1 when received at the end. That can be
viewed
as a waste, especially if G=1 messages cost more than G=0. Nodes can reduce
G to 0 as long as they have a strong signal and connection. In a crisis
mode, the
G bits may pop up set to 1 and the wireless radios may also increase their
power
despite regulatory agencies frowning on that.

There are many many corner cases that people can explore and observe as
nodes
send messages and the environment changes. Now that Uni.X nodes with WIFI
are $50, you can explore that on your own with several nodes. Not long ago,
in
meat-space time, such nodes would likely have cost $20,000. Most people
would
not have 8 or 10 of those in their house and car. Times have changed, the
always-on
24x7 wireless .NET composed of low-cost intelligent Uni.X nodes is here and
has
been here for a long time. The barrier to entry is now lower and anyone can
explore
the new .NET space. Out-dated governance regimes no longer apply with
architectures
based on million dollar main-frames and $3,000 per month T1 connections
between
well-funded insiders living off various governments. People can now buy
their own
nodes and pay for their own power and their own .NET. Obviously, there are
some
people who do not like to see that happening. They tried to stop it in the
90s and they
continue to try to stop it or regulate it.

All people can do is educate themselves and attempt to route around the
damage
THE Big Lie Society has done. Hopefully, with a larger address space that is
more possible.
As people already see, THE Big Lie Society is adding to their bureaucracies
in the
address space arena. They will tax you and continue to expand. Big
government is
like that. A big address space should bring little government or governance,
that does
not seem to be the case. One hope is that big government will go off and
chase the
128-bit solutions. Bigger is better ? Right ? Sounds like a good lie to add
to the list.


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