[arin-ppml] /20 initial allocation for single-homed server?

Ted Mittelstaedt tedm at ipinc.net
Mon May 24 20:29:27 EDT 2010



On 5/24/2010 4:40 PM, Aaron Wendel wrote:
> ARIN staff have never required technical justification for IP usage.  Your
> suggestion would be a major shift in policy and a MAJOR addition to ARIN's
> mandate.  I would be opposed to ARIN staff telling me how to run my network.
>
> Aaron
>

You may be opposed but your wrong.

One of the FIRST justifications for obtaining IP addressing is that you
MUST have a justification for global uniqueness for your
assignments.  global uniqueness is a TECHNICAL justification.

A second justification is that you can utilize most of those numbers.

You MAY NOT put down that you need a million numbers when you only
have a technical need for a few thousand - this is considered fraud.

Regardless of how utilization is defined, the PERCENTAGE of utilization
is most certainly a technical criteria for justification.

Section 4.2.2 explains this pretty clearly as does 4.2.3

Note also that the amount of initial numbers you may request is
ALSO governed by whether or not you are multi-homed, that IS ALSO
a technical justification - since if you ARE multihomed you may
obtain numbers at a lower utilization threshold.

So ARIN staff IS DEFINITELY telling you how to run your network.


Ted

>
> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of James Hess
> Sent: Monday, May 24, 2010 6:27 PM
> To: Ted Mittelstaedt
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] /20 initial allocation for single-homed server?
>
> On Mon, May 24, 2010 at 3:29 PM, Ted Mittelstaedt<tedm at ipinc.net>  wrote:
>>
> [snip]
>
> Well,   I would suggest then that  technical justifications have some
> artificial restrictions imposed,  above and beyond policy, so that...
>
> (1)  Additional IP addresses 'needed' solely to evade IP-based blocks,
> blacklists, or rate limits     should be rejected
> and
> (2) Additional IP addresses to be used to  reduce  per-IP
> transaction request  rates,  average, or load-balance requests  among
> a large number of IP addresses    should also be rejected
>
> Both should be considered unacceptable  technical justifications.
>
> And  each IP  address  must be used by some distinct resource  or customer,
> that cannot be a resource shared with the other IPs.
>
> (In other words, the IP address has to actually identify something unique)
>
> Resource being...  separate physical device, DNS second level domain
> name,  or some other thing  that  cannot be  expanded  infinitely,
> based on the applicant's  arbitrary wishes.
>
> --
> -J
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.819 / Virus Database: 271.1.1/2870 - Release Date: 05/24/10
> 01:26:00
>



More information about the ARIN-PPML mailing list