[124918] in North American Network Operators' Group

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

Re: ARIN IP6 policy for those with legacy IP4 Space

daemon@ATHENA.MIT.EDU (Kevin Stange)
Wed Apr 7 15:48:36 2010

Date: Wed, 07 Apr 2010 14:47:59 -0500
From: Kevin Stange <kevin@steadfast.net>
To: Antonio Querubin <tony@lava.net>
In-Reply-To: <alpine.OSX.2.00.1004070620290.153@cust11794.lava.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1110AAD1B2E057424B493DE2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 04/07/2010 11:26 AM, Antonio Querubin wrote:
> On Wed, 7 Apr 2010, John Palmer \(NANOG Acct\) wrote:
>> Isn't this a disincentive for us to move up to IP6?
>
> Yep.  Just went through this with one organization which I hadn't
> realized at the time was a legacy IPv4 holder.  The fees were a surpris=
e
> (I thought they'd already been paying those fees).  Needless to say,
> their IPv6 plans are on hold indefinitely.

How much IPv6 address space were they expecting?  I have trouble
envisioning any operation that could require more than a /32 immediately
that can't afford to pay $4500 per YEAR.

--=20
Kevin Stange
Chief Technology Officer
Steadfast Networks
http://steadfast.net
Phone: 312-602-2689 ext. 203 | Fax: 312-602-2688 | Cell: 312-320-5867


--------------enig1110AAD1B2E057424B493DE2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAku84XMACgkQkd/BoeKjg0hoDACfanRLU1HJnaX8jVnPLk+rQezB
QpMAoJLZtUNtwB81vpwnU76RXLAGYKnv
=H+Q1
-----END PGP SIGNATURE-----

--------------enig1110AAD1B2E057424B493DE2--


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