[arin-discuss] Food for thought: IPv4 accountability.

Tony Valenti tony.valenti at powerdnn.com
Wed Jul 22 09:44:09 EDT 2009


Danny - I think the better question to ask is "Does anybody from ARIN care?"

On Wed, Jul 22, 2009 at 8:40 AM, John Curran <jcurran at arin.net> wrote:

> Nathaniel -
>
>     While ARIN is being diligent in verifying IPv4 address requests, the
> outstanding
>     size of the IPv4 free pool is not creating an "strain" on meeting the
> needs of ISP's
>     for IPv4 addresses.
>
>     What most smaller ISP's are experiencing in difficulty obtaining IPv4
> address space
>     is due to the requirements to show existing utilization of upstream
> ISP's assignment
>     and/or to show that they are multi-homed.  These requirements in the
> IPv4 policy
>     stem from the communities concern that having every ISP today
> immediately get
>     an IPv4 address block would result in some assignments going unused,
> and further
>     would result in a rapidly growing IPv4 routing table.
>
>     I acknowledge it can be challenging for a smaller ISP to obtain their
> own IPv4
>
>     address block, but want to be clear that the reason for this is the current policy
>
>     and concerns about routing, not per se any result of the pending depletion of
>     the IPv4 available pool.
>
> /John
>
> John Curran
> President and CEO
> ARIN
>
> p.s.  As always, the ARIN policy in this area can be changed if the
> community reaches
>         consensus on improvements.   Information on the policy development
> process can
>         be found at  <https://www.arin.net/policy/pdp.html>
>
>
> On Jul 21, 2009, at 5:27 PM, Nathaniel B. Lyon wrote:
>
> Shon,
>
> I couldn't have said this any better myself.  We are a small/medium WISP
> based out of Northfield Minnesota and we have been trying to get an IPv4
> block ourselves for some time now and actually found that it might be easier
> robbing a bank than getting an IPv4 block assigned to us.  We recently threw
> up our hands and went after an IPv6 block, easiest thing in the world to
> obtain.  We were handed a /32 of IPv6 addresses literally in a 1 day.  Don't
> get me wrong, that is great, but we are most likely not going to see IPv6
> fully utilized across the board for 5 years.  So in the meantime, what are
> we to do?
>
> Long story a little shorter, my organization feels like the big guys have
> pretty much wrecked it for everyone mid-sized and below.  For us to even get
> our foot in the door with our own IPv4 pool is a pipe dream.  To make
> matters worse, we are sitting here with this nice pool of IPv6 addresses and
> we can't even start testing these IP's because our upstream isn't capable
> yet of allowing these to transport across their network.
>
> I don't know if we are the only organization that is feeling the strain of
> the "lack" of IPv4 addresses, but something needs to give between now and
> when IPv6 is the standard.  IPv6 is not going to be the standard over night,
> so handing every ISP a /32 in IPv6 world is NOT the fix either.  Smaller
> organizations need to be looked at and given a *fair chance* at the IPv4
> world.  Not having a shot in the dark at an IPv4 pool is greatly straining
> some ISP’s.
>
> It’s nice to hear others are feeling like their IPv4 needs are not ever
> going to be met, which is sad to say the least.  I urge others to come out
> and share their opinions.  Unwired Broadband and NorthfieldWiFi can’t be the
> only two ISP’s getting the short end of the stick in the IPv4 world.
>
> Nathaniel B. Lyon
> Owner, NorthfieldWiFi
> (612) 991-4260
> www.northfieldwifi.com
> nate.lyon at nfldwifi.net
>
>
>
> _______________________________________________
> ARIN-Discuss
> You are receiving this message because you are subscribed to
> the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-discuss
> Please contact info at arin.net if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-discuss/attachments/20090722/45af2a5f/attachment.html>


More information about the ARIN-discuss mailing list