[147452] in North American Network Operators' Group

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

Re: Sad IPv4 story?

daemon@ATHENA.MIT.EDU (John Curran)
Sun Dec 11 06:53:32 2011

From: John Curran <jcurran@arin.net>
To: Franck Martin <fmartin@linkedin.com>
Date: Sun, 11 Dec 2011 11:52:21 +0000
In-Reply-To: <CB07955B.497B3%fmartin@linkedin.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Dec 9, 2011, at 1:37 PM, Franck Martin wrote:

> I just had a personal email from a brand new ISP in the Asia-Pacific area=
 desperately looking for enough IPv4 to be able to run their business the w=
ay they would like=85
>=20
> This is just a data point.

Franck -=20
=20
  Thanks for the data point - I'm certain there are others folks
  out there with similar experiences that we're not hearing about.

  Of course, the theory was that at this point they'd be able to=20
  use IPv6 to connect customers up to the Internet. Such theory=20
  was predicated on a presumed strong motivation for everyone already
  connected via IPv4 to deploy IPv6 in parallel (i.e. dual-stack) and=20
  some elusive TBD transition mechanisms which were to make IPv6=20
  customers interoperate with those that hadn't yet deployed IPv6 =20
  in parallel. =20

  Reality looks very different, in that existing organizations
  find it difficult to understand why to add IPv6 connectivity to=20
  their existing public-facing servers, and the state of the art in=20
  achieving transparent operation for IPv6 connected systems to the=20
  rest of the Internet running only IPv4 is still effectively a=20
  work-in-progress...

  While your data point may be from the Asia-Pacific region, that
  same story is going to repeated in every region (RIPE NCC will
  be running out shortly, and ARIN has 1 to 2 years depending on
  the actual request rate that materializes)  Service providers in
  the ARIN region need to carefully consider their answer to that
  same situation, because it will be occurring here soon enough.

  There is one thing that everyone can do to reduce the impact of
  this transition, and this is getting in front of their business
  customers (and small business/power users who have public-facing
  content) to explain that the Internet is going be running IPv4
  and IPv6 for quite some time in parallel and that getting their
  public-facing servers connected up also via IPv6 is a very good
  idea (if anyone wants help doing this sort of customer education=20
  ARIN's https://www.arin.net/knowledge, NRO's http://www.nro.net/ipv6,=20
  and APNIC's IPv6 Act Now http://www.ipv6actnow.org web sites are all=20
  good sources on materials for this sort of effort.)

  The sooner we get the content on IPv6 in addition to IPv4, the sooner=20
  that connecting new customers up via IPv6 without additional unique=20
  IPv4 address space becomes viable (and obviously if we had the vast
  majority of content already on IPv6, then connecting new customers=20
  via IPv6 would be simple indeed.)

FYI,
/John

John Curran
President and CEO
ARIN




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