nanog mailing list archives
RE: rfc 1918?
From: Mark Borchers <mborchers () splitrock net>
Date: Fri, 23 Feb 2001 08:46:00 -0600
This is not an issue of paranoia (except for those who actually use PRIVATE addresses internally and have properly configured their gateways to be paranoid about even seeing such packets, let alone routing them).
Unless I'm mistaken, a prime reason for the evolution of RFC 1918 addresses was that it was once common practice for people to help themselves to PUBLIC address space to use on PRIVATE networks. As the world got more connected, these addresses occasionally got leaked and caused address conflicts. Using RFC 1918 addresses prevents conflicts with public/registered space. Obviously the possibility of leakage still exists, but with RFC 1918 the havoc potential is diminished to a mere irritant level. Which is what the incident that started this thread appeared to be.
Current thread:
- Re: rfc 1918?, (continued)
- Re: rfc 1918? Shawn McMahon (Feb 24)
- Re: rfc 1918? Richard A. Steenbergen (Feb 24)
- Re: rfc 1918? Eric A. Hall (Feb 24)
- Re: rfc 1918? Adrian Chadd (Feb 24)
- Re: rfc 1918? Greg A. Woods (Feb 24)
- Re: rfc 1918? Ariel Biener (Feb 24)
- Re: rfc 1918? Eric A. Hall (Feb 24)
- Re: rfc 1918? SMcGrath (Feb 24)
- Re: rfc 1918? Rancken (Feb 24)
- Re: rfc 1918? SMcGrath (Feb 24)
- Re: rfc 1918? bill manning (Feb 24)
- RE: rfc 1918? Mark Borchers (Feb 24)
- RE: rfc 1918? Greg A. Woods (Feb 24)
- Re: rfc 1918? Scott Francis (Feb 24)
- RE: rfc 1918? Greg A. Woods (Feb 24)
- RE: rfc 1918? Chris Davis (Feb 24)
- Re: rfc 1918? Ron Buchalski (Feb 24)
- Re: rfc 1918? SMcGrath (Feb 24)
- Re: rfc 1918? bill manning (Feb 25)