[governance] Uni.X to Uni.X Communication in 160 bits

[Jim Fleming]

Uni.X to Uni.X Communication 160 bits

Even a novice Computer Professional with some Social Responsibility should
be
able to see that, in theory, with 64-bit addressing in two directions, you
need 128 bits.
With a 160 bit storage area or sequence of bits on a wire or channel, you
have 160-128=32
bits remaining. Because of legacy hardware and mind-sets, it can be very
hard to change
16 of those bits that carry a changing Check-Sum used to attempt to detect
corruption of
the bits during an interchange. If you assume those 16 checksum bits can not
be touched,
then 32-16=16 bits remain to use to create a wrapper for the TWO 64-bit
address blocks
and the 16-bit checksum. If 10 of those bits are used for a length [0 to
1023], then you are
down to 6 bits. If 3 or 4 of those bits are used for a modern hop-count of 7
or 15 hops
for local and global services, then you still have 2 bits remaining, 6-4=2.
With 2 bits
you can encode 4 Protocol values which could be called ICMP, UDP, TCP and
NOP.
The NOP No-Protocol could indicate that there is no more to the message than
the 160
bits and the 10 length bits and 16 checksum bits can be combined into a
2+24=26 bit field
with 2 bits for the length and up to 3 bytes of data in the 24 bit field
which may not be in
a contiguous area.

Revisiting that legacy packet layout from early research efforts, one can
start bit by bit and
determine a mapping of the above into the 160 bits. There are some mappings
that seem
logical to make it easier to remember. As an example, the 10 bit length
above can be stored
in the right-most 10 bits of the 16 bit length field. That frees up 6 bits
for 3+3 extended addressing.
The 2 bits for the Protocol can be stored in the 8 bit Protocol field
freeing up 6 bits which can be add 3+3 to the extended addressing. The old
8-bit TTL field can contain the 3 or 4 bits for the hop-count. That frees up
4 bits for another 2+2 bits for extended addressing. The first 4 bits, the
old Version number can be divided into 2+2 for extended addressing. The 0101
(value 5) from the removed options code can be cosidered to be a 2+2
extended addressing field, currently frozen to 01+01. The 8 bits from the
old TOS can add a 4+4 extended addressing field. Since the length has been
reduced to 10 bits, there is less need for fragmentation which frees up a
16+16 extended
addressing field. Adding up the extended addressing one has,
16+4+2+2+2+3+3=32

If one is careful in their selection of which of the 32 extended addresses
they need, they can
tunnel some of the extended address bits thru existing hardware. If one
considers the theoretical
maximum of 32 extended addressing bits in their planning, they can start
taking steps now to
deprecate certain fields. One example is to reduce all packets in size to
fit in the 10 bit length.
Another example is to adjust the default TTL from 64 to 63 to better match
up with the smaller
hop-count field. That then appears as a 0011 in the extended addressing bits
SDSD. Another
example is to consider an environment with 4 essential protocols as opposed
to up to 256.
Some people may be able to live with one essential protocol, UDP. Having 4
can be viewed as
a luxury.

Speaking of a luxury, if you happen to have a lot more bandwidth and room
for 320 bits vs.
160 bits, the above packets can easily be mapped with their 64-bit
addresses. If you keep the
data portion small (as with voice applications), you can encode the data in
the right-most
address bits not used in 128-bit address fields. As people talk, it looks
like packets are going
to many different locations, when it is really the speech in the unused
bloated address fields.
The 64-bit addressing is backward and forward compatible in 160-bit and
320-bit packets.

With 64-bit addressing, it turns out that 32 bits is handy as a throw-away
and assumed to come
from some telco or government infrastructure. The other 32 bits are yours to
manage. That
is an address space as large as the legacy boot-strap research transport,
and it has not come
close to being used up, even with years of gross mis-management and
corruption.

Given that you see your limit is going to be 32 bits, and you can manage the
entire space,
your digital island can begin using large pieces of that space knowing you
will not collide
with the legacy transport and also knowing that 4+ billion other digital
islands will have the
same size and an EQUAL size space. Note: THE Big Lie Society does not
believe in notions
like fair and equal. If they ran the olympics their track lane would be
twice as wide and half
as long and the referee would declare them the winner without even running
the race. The only
way they can compete is to lie and cheat and game the system. Stay tuned for
their announcements
of how they use 320 bits and dupe the U.S. Government. If you educate
yourself, and write
code for the Uni.X to Uni.X communication systems, you will not be fooled by
THE Big Lie
Society. You will know what each bit does, why it is there, etc.

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