[30162] in North American Network Operators' Group
Re: RFC 1918
daemon@ATHENA.MIT.EDU (ww@shadowfax.styx.org)
Mon Jul 17 12:26:56 2000
From: ww@shadowfax.styx.org
To: Stephen Kowalchuk <skowalchuk@diamonex.com>
Cc: nanog@merit.edu
In-Reply-To: Your message of "Mon, 17 Jul 2000 12:05:09 EDT."
<39732EB5.4E50032B@diamonex.com>
Date: Mon, 17 Jul 2000 12:11:58 -0400
Message-Id: <20000717161158.8A43D745F@shadowfax>
Errors-To: owner-nanog-outgoing@merit.edu
>>>>> "Stephen" == Stephen Kowalchuk <skowalchuk@diamonex.com> writes:
Stephen> Public IP address allocation from ARIN is a totally
Stephen> different matter.
If people need assign addresses to things, they're going to do it. If
certain bureaucracies prevent them from doing it the correct way,
they'll do it the incorrect way, which is what we're discussing here.
Stephen> My point is that filtering RFC 1918
Stephen> addresses at your network's borders is the right thing to
Stephen> do for a number of reasons.
Which is good in theory, but sometimes is not possible. Up untill very
recently a router did not exist that could actually do this when a
significant amount of traffic is being pushed through it.
Cheers,
-w
--
Will Waites \________
ww@shadowfax.styx.org\____________________________
Idiosyntactix Ministry of Research and Development\
