From: rick.jones2@hp.com   
      
   glen herrmannsfeldt  wrote:   
   > Traditionally, browswers start a new TCP connection for each   
   > request, though maybe they don't always do that now.   
      
   They do attempt to use at least persistent (same connection, requests   
   one at a time) if not pipelined (same connection, several requests at   
   once) connections.   
      
   > Many ISPs now assign DHCP addresses for a very long time.   
   > Mine changes every few years or so.  They could change much   
   > more often if there was a reason to do it.  (Most likely   
   > they would still keep logs of the assigned addresses, though.)   
      
   Without either forcing all TCP (and perhaps other) connections to   
   close for the IP address change, it would require keeping the old IP   
   address(es) around until the last connection using that as a source IP   
   closed (or the TCP connections become effectively closed as they   
   become unusable).  I suspect that would tie-up more addresses than   
   ISPs would like their customers to have.  That also implies the IP   
   addresses would have to come from the same subnet, or the ISPs will   
   need rather heftier routing than they might wish to pay for.   
      
   rick jones   
   --   
   No need to believe in either side, or any side. There is no cause.   
   There's only yourself. The belief is in your own precision.  - Joubert   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)