Even RFC1918 addresses get connected sometimes through corporate mergers. It would work better if organizations would choose a random set of subnets from 10/8, so the chance of overlap is minimized. Unfortunately, people tend to use 10.0.0.1 and up, or 192.168.0.1, etc. Then they have to internally renumber to connect these networks internally, or else use internal NATs. I don't really see this as a problem to be concerned with. It is unavoidable to some extent and better random subnet selection would tend to minimize the problem. --Dean On Tue, 29 Apr 2003, John Stracke wrote: > Arien Vijn wrote: > > >On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote: > > > > > >>>What is wrong with having addresses available for private use on > >>>networks that do not intend on being connected to the Internet? > >>> > >>> > >>in principle, nothing. but experience has shown that most of those networks > >>do end up being connected to the Internet, while still keeping those addreses, > >>and that applications are expected to cope with that. > >> > >> > >Ehm... What experience? You are referring to experiences with RFC1918 > >addresses in the IPv4-world, aren't you? > > > I think Keith is most likely referring to the experience from before > RFC1597, when isolated networks would use random addresses, and then run > into trouble when they wanted to connect. Even if the networks were > NATted, the users would suffer because they would never be able to > communicate with the legitimate holders of the addresses. > > -- > /=================================================================\ > |John Stracke |jstracke@centive.com | > |Principal Engineer|http://www.centive.com | > |Centive |My opinions are my own. | > |=================================================================| > |Vote for Ron, and nobody gets hurt! --actual campaign poster from| > |Chicago | > \=================================================================/ > > > >