[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Purchasing IPv4 space - due diligence homework
Do you have sources for the ~90% T-Mobile IPv6? Not arguing, but to use that as a source myself when spreading the IPv6 good word.
Intelligent Computing Solutions
----- Original Message -----
From: "Jared Mauch" <jared at puck.nether.net>
To: "Matt Torres" <Matt.Torres at state.or.us>
Cc: nanog at nanog.org
Sent: Wednesday, April 3, 2019 10:58:23 AM
Subject: Re: Purchasing IPv4 space - due diligence homework
> On Apr 3, 2019, at 11:20 AM, Torres, Matt via NANOG <nanog at nanog.org> wrote:
> Side stepping a migration to IPv6 debateâ?¦. Iâ??d like to hear advise from the group about performing due diligence research on an IPv4 block before purchasing it on the secondary market (on behalf of an end-user company). My research has branched into two questions: a) What â??checksâ?? should I perform?, and b) what results from those checks should cause us to walk away?
> My current list is:
> â?¢ Check BGP looking glass for route. It should not show up in the Internet routing table. If it does, walk away.
> â?¢ Check the ARIN registry. The longer history without recent transfers or changes is better. I donâ??t know what explicit results should cause me to walk away here.
> â?¢ Check SORBS blacklisting. It should not show up except maybe the DUHL list(?). If it does, walk away.
> Anything else? Advise?
Iâ??d like to ask a related question (Iâ??m not questioning why you need IPv4 space) but are you also deploying IPv6 as well? If not, is there a reason? In my copious spare time Iâ??m doing a small FTTH network and many services do work well with IPv6 while others (banks are a an example) perhaps donâ??t.
We have T-Mobile USA saying with their network most bits go out as v6, so Iâ??m guessing thereâ??s that 5-10% you need v4 for if you deploy as aggressively as they do.
Mostly curious if you are doing IPv6 if you see that slowing your need for v4 or if they are growing at the same rate.
-------------- next part --------------
An HTML attachment was scrubbed...