[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
De-bogon not possible via arin policy.
- Subject: De-bogon not possible via arin policy.
- From: matthew at matthew.at (Matthew Kaufman)
- Date: Thu, 15 Dec 2011 08:53:04 -0800
- In-reply-to: <[email protected]>
- References: <CAD6AjGSiJiLj3itb1EARVpNn-xF5hMnrk97pYYjLrw=X_-XfhA@mail.gmail.com> <CAAAwwbU_t0yaxYhKZrnD+9+1V=CgRBEW6vSsvZC7zYszinGj9w@mail.gmail.com> <[email protected]> <CAAAwwbXnmQ=L7YsLoEfQ-bq8EMQa6q32SMVhqa9PT5s+TF=JZQ@mail.gmail.com> <[email protected]> <[email protected]>
On 12/15/2011 8:05 AM, Valdis.Kletnieks at 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