[governance] Uni.X to Uni.X .NETworking - Length Field Code Points

[Jim Fleming]

Uni.X to Uni.X .NETworking - Length Field Code Points

Because of legacy compatibility, the 10-bit Length field begins at the count
of 20
because it includes the 20 bytes (160 bits) in the Uni.X to Uni.X message
header.
A value of 20 implies a value of 0 for the data portion. The maximum 10-bit
value
of 1,023 includes the 20 bytes which implies the data portion is limited to
1,003
bytes [or octets to be more clear they are 8-bit packages].

The values from 0 to 19 can be used to encode large common fixed length
sizes
and some extended addressing and length information for header chaining.

0 - 8,191+20
1 - 16,383+20
2 - 32,767+20
3 - 65,535+20

Note: The 20 bytes of the Uni.X to Uni.X message header is assumed or
included
in the above lengths. The data after the header is of the maximum buffer
size and
matches up with common large-capacity storage devices. While this could be
made
to work with legacy fragmentation features, the use of the jumbo sizes also
assumes
the complete deprecation of fragmentation, and no added code-bloat is
needed, if
anything, the move to this capability reduces the code-bloat.

The above sizes help to regain some of the lost functionality in migrating
from a 16-bit
length in proof-of-concept research code to a 10-bit length for production
systems.
By havng fixed sizes, common buffer-overflow exploits can be avoided via
more robust code.

The other 16 code-points, 4 to 19 can be used for Maintenance Extended
Addressing,
LAN Party Encapsulation, etc. the next 160 bits determine the real length.
The implied length is 40, this header and the next one.
The addressing is either SSDD or SDSD depending on the routing and
governance policies.

People involved in "Internet Governance" seem to be lost in endless
discussions about
a silly "root zone" of a name-space that may or may not matter. With
millions of low-cost
Uni.X nodes, forming the .NET, in an always-on arrangement, the governance
picture
changes. It would probably be as drastic a change as if millions of space
visitors landed in
a major U.S. city, with the city officials un-prepared to communicate with
the creatures
and unable to even find them. Millions of wireless Uni.X nodes could be very
hard to find.
As they communicate, they may be able to replicate, self-heal, and
re-address themselves.
One has to look at the binary streams they are exchanging to start to
understand the bots.

Bots can help to protect netizens from Internet Governance conjured up in
meat-space.
Meat-space people seem to have no clue how well-developed the bot technolgy
has become.
They could read the code, but they do not appear to understand the code or
have any
interest in the code. One problem is of course there can be many versions of
the code and
also completely different code bases, languages, etc. Governance for some
people may end
up resulting in laws that dictate one code base, one language, one
name-space, one protocol,
etc. which may not be all that bad if people were involved in shaping those
spaces. THE
Big Lie Society of course works to make sure only "the right people(tm)" are
involved.
Meat-space people are easy prey for THE Big Lie Society.

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