XPost: alt.winsock.programming, comp.arch, comp.dcom.lans.ethernet   
   XPost: sci.crypt   
   From: IntoTheFuture@hotmail.com   
      
   Another way of looking at this idea is from the point of "address   
   translation" also known as NAT.   
      
   I'm a bit rusty about NAT but as far as I remember NAT works by using public   
   available resources like public ip addresses, and public ports and tries   
   to attach a single public ip address and multiple public ports to multiple   
   local ip addresses.   
      
   NAT is probably based on the idea of "public ip addresses" versus "local ip   
   addresses" and exploits that.   
      
   The difference with my idea is that instead routers exploit the   
   "non-seen-address-space" for translation/privacy.   
      
   As long as a router does not see a real ip/address it can use it as a fake   
   ip/address which will still work because it/the router will take   
   responsibility for the fake/ip address and act upon it when it receives it   
   from other routers which believe those fake ip addresses are real.   
      
   Here may lie a problem though... what if those other routers do see these   
   fake ip addresses which are actually real ip addresses... such routers might   
   start to route the fake ip/address wrongly... I am not sure how much of a   
   problem this is and if it can be solved somehow... maybe by some smart   
   routing/information/bgp tricks or something... but it's definetly something   
   to be aware of and look into... it might put a kink in the cable for this   
   idea ?! ;) :)   
      
   Bye,   
     Skybuck.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)