[governance] Setting up Your Uni.X to Uni.X Lab for Protection and Learning

Jim Fleming JimFleming at Ameritech.NET
Mon Oct 10 23:18:45 EDT 2005


Setting up Your Uni.X to Uni.X Lab for Protection and Learning

One of the problems with Uni.X to Uni.X communication technology is that you
need at least TWO Uni.X systems to test your protocols and system software.
In the old days, setting up a lab required millions of dollars and tens of
millions if you wanted your own PSTN digital voice switch. Some of us were
fortunate enough to have companies fund those labs in the 70s and 80s.
Regulatory changes helped to destroy those labs and distribute them not only
in the US but also off-shore. Government-funded insiders also tried to
destroy the Uni.X network technology by renaming it and focusing users on
regulatory discussions that lack technical content and enrich nations with
meat-space meetings. Despite all of those forces, Uni.X to Uni.X
communication technology is alive and well.

Not only is Uni.X to Uni.X communication technology alive and well, it is
now more affordable and available off-the-shelf at popular retailers, at
least in the USA. For those people who want to explore Uni.X to Uni.X
communication technology, you can now set up a TWO processor system (node)
for under $120. It is ironic that the hardware for your lab would come via
Cisco who purchased the technology via an aquisition of Linksys. It is more
ironic that the software for your Uni.X to Uni.X lab will come from the net,
and not Cisco or Linksys. This is a similar to the old days in Uni.X land
where hardware from DEC was purchased and reprogrammed with Uni.X code from
scratch. In Uni.X land, DEC was never viewed as producing software of any
use and it is interesting that much of the current code bloat and Internet
software problems as well as so-called governance problems appear to descend
directly from a DEC heritage. Historians who seem inclined to study the net
governance may want to study that coincidence.

For people who want to learn something and move forward, the Uni.X to Uni.X
communication technology can offer a path and you can participate. Now that
telcos are operating the core transports and BGP blackholers are being
quietly de-peered from the core transport, you can set up your Uni.X to
Uni.X lab almost any place, without fear of having it destroyed by members
of THE Big Lie Society or the thugs they direct.

Using the Cisco/Linksys WRT54G as an sample component, your arrangement
would be:

PSTN--------PE Uni.x $60 Firewall----------CE Uni.X $60 Firewall--------PC

The Uni.X to Uni.X communication occurs between the PE (Provider Edge) and
CE (Customer Edge) devices. You can change (and program) 100% of the
software in the PE and CE devices and become familiar with how Uni.X to
Uni.X communication technology works. You can learn how all of the 160 bits
are processed in the messages that flow between the devices. With the PE
device re-programmed as a WIFI Client, and the CE device re-programmed as a
WIFI Access Point, you can even test both ends of WIFI sessions. You can
also learn about the hundreds of modules that are being developed and
downloaded for the PE and CE devices. Contrary to some of the
mis-information spread around, you can also learn that NAT is only run in
the PE device. Your view of the net is of course two steps removed as you
work from your PC. With the dual-firewall arrangement, you can deploy many
levels of protection and learn more about how software continues to be
developed to help protect adults as well as children but still provide a
better on-line experience.

With the above arrangement, you can also learn how the CE device begins to
develop a view created by the PE device. As the software changes in the PE
device that view can change. Likewise, the view from the PC can remain
somewhat fixed because the CE device can represent the PC to the PE device.
The PE device does not have to communicate directly with the PC. The CE
device can present a view to the PE device of the PC.

With your $120 Uni.X to Uni.X communication lab, you can begin to explore
what really happens in that zone between the PE and CE devices. You can also
begin to explore what happens when those zones start to mesh together in
either wireline or wireless scenarios. You can remove the complexity that
sometimes comes from the mysteries of a PC and focus on pure Uni.X to Uni.X
communication. If you do that, you may begin to see why most Uni.X to Uni.X
communication technology developers have little interest in the so-called
Internet governance distractions which seem to lack any technical content
and produce no results.

Once you get your Uni.X to Uni.X communication lab set-up, you can study and
review what all 160 bits in the Uni.X to Unix.X messages contain. You might
also discover that content only available via Uni.X to Uni.X communication
is now at your finger tips. You might also be able to hold your own in
forums where people debate how the 16 bits that some people think encode
length are divided into 10 bits for the length and 6 bits for other uses.
You might also see how the 8 bit protocol field, is divided into 2 bits for
the main protocols ICMP, UDP, TCP with a 4th code-point to indicate other
and a 6 bit map to encode the 64 other protocols. You can also see how the 8
bit TTL or Hop-Count field is divided for more Source and Destination
addressing while remaining backward compatible yet encouraging a move to a
maximum of 7 hops for the domestic PSTN core network and 15 hops for the
international transports where settlement fees and governance are handled
differently. There are a wide range of areas you can explore in that 160 bit
field. Beyond that, you can see how DHT technology is used to allow you to
store up to 1024 bytes under a 160 bit key for up to one week. You can also
discover how a 5-bit symbolic alphabet, with 32 symbols, can be used to
encode the 160 bit DHT key resulting in a 32 character name which looks a
lot like a domain name or email address. The list of areas to explore go on
and on. The source code is open and free and becoming SMALLER as code bloat
is removed. That makes the PE and CE nodes more reliable, stable and secure.
Being able to update the software to a new version often also increases the
stability and security. You might want to compare that approach to the
approach of THE Big Lie Society which can not tolerate any change,
especially any change that impacts their funding sources.

In summary, you and/or your children can set up a Uni.X to Uni.X
communication lab for $120 and help to evolve the net. In doing so, it may
give you another view of how other people on Planet.Earth view the net and
have viewed it since the 70s, when PCs were constructed from 8008 processors
and loaded with audio cassettes, which came from the same retailers who now
carry the components you need to build your Uni.X to Uni.X communication
lab. In 30 years, it will be interesting to see what the retailers are
offering. One thing for sure, 1s will still probably be ones and 0s will
still probably be zeroes. Classic concepts and structures seem to survive,
despite many human's attempts to rewrite the laws of physics.


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



More information about the Governance mailing list