[30160] in North American Network Operators' Group
Re: RFC 1918
daemon@ATHENA.MIT.EDU (Stephen Kowalchuk)
Mon Jul 17 12:09:50 2000
Message-ID: <39732EB5.4E50032B@diamonex.com>
Date: Mon, 17 Jul 2000 12:05:09 -0400
From: Stephen Kowalchuk <skowalchuk@diamonex.com>
MIME-Version: 1.0
To: ww@shadowfax.styx.org
Cc: nanog@merit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Public IP address allocation from ARIN is a totally different matter. My point
is that filtering RFC 1918 addresses at your network's borders is the right
thing to do for a number of reasons. IMHO using RFC 1918 addresses on your
backbone routers (or any other public device) for anything other than emergency
or truly temporary use is a recipe for disaster.
My $0.02.
ww@shadowfax.styx.org wrote:
<snip>
> Imagine that you inherit a network where RFC1918 addresses are used ...
</snip>
--
--------------------------------------------------------------------------
Stephen Kowalchuk skowalchuk@diamonex.com
Diamonex, Incorporated
--------------------------------------------------------------------------
