>  >> We need to find our own solution to the new TLD problem, and the
>>>  cooperative maintenance of the Virtual Inclusive Root.
>>
>>Burying your head in the sand and wishing the problem away won't make it
>>so.
>>
>>Ignore ICANN to your own detriment.
>
>Perhaps, but saying "these ISO protocols suck and should not be used"
>was not effective. Making TCP/IP work, was.
>

and as stef just taught me yesterday as part of a discussion of end to end
was that by having TCP stacks on both our machines that we control we 
can pass ip datagrams across the network in such a way that a central 
administrator can not control them.  my stack does a checksum on what 
you sent me and if the sum checks i know that the IP bit stream you 
sent is what i received.

the lesson here is that the tools for control reside on the edge 
machine on my desktop and the one on your desktop....and the pipe 
connecting our desktops is empty.....it is just like one of those old 
air blown pneumatic tubes.

forget laws ken, laws give someone the ability to insert a box in the 
middle to interfere with our ip datagrams.....

read lessig on laws and cyberspace if you wanna know what laws are worth

or read the legend of the grands inquisitor from the brothers karamazov
ICANN is the inquisitor sent to rule over us

the inquisitor  explains to christ why he will burn him at the stake. 
christ routes around the inquisitor by kissing him on the cheek and 
sending him out from the dungeon in  seville into the night 
air....effectively ignoring the threat....
-- 
****************************************************************
The COOK Report on Internet, 431 Greenway Ave, Ewing, NJ 08618 USA
(609) 882-2572 (phone & fax) [EMAIL PROTECTED]   Index to 9 years
  of the COOK  Report at http://cookreport.com         From now 
through Sept 15th
half price sale on university library site license and access to ALL 
back issues.
Site license $575 and all back  issues $300.  http://cookreport.com/sale.shtml
****************************************************************

Reply via email to