[147614] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: De-bogon not possible via arin policy.

daemon@ATHENA.MIT.EDU (Matthew Kaufman)
Thu Dec 15 11:53:55 2011

Date: Thu, 15 Dec 2011 08:53:04 -0800
From: Matthew Kaufman <matthew@matthew.at>
To: Valdis.Kletnieks@vt.edu
In-Reply-To: <27530.1323965127@turing-police.cc.vt.edu>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Reply-To: matthew@matthew.at
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 12/15/2011 8:05 AM, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 15 Dec 2011 07:42:40 PST, Matthew Kaufman said:
>
>> Here's a simple one involving "squat" space: You have a network that
>> internally is using *all* of 10.0.0.0/8 *and* 5.0.0.0/8 (because you
>> have enough customers to fill two /8s).
>>
>> Now that 5.0.0.0/8 is being allocated, you need to move out of it (so
>> that your users can reach the real 5.0.0.0/8 sites).
>>
>> Why wouldn't this be sufficient justification for a new /8 from ARIN?
> Because you can probably use the other two 10/8's you already have.
> And if thiose run out, a third 10/8 is cheap even on the secondary market.
>

You're assuming a network architecture which is not required by policy.

Matthew Kaufman


home help back first fref pref prev next nref lref last post