Allocating a /16 to a large enterprise ?
[This is about ARIN, but curious to see if anybody has any insight...] A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3). If anyone has any insight, then I will welcome this insight in this specific case. Regards -éric
On 11 Dec 2023, at 08:49, Eric Vyncke (evyncke) via ipv6-wg <ipv6-wg@ripe.net> wrote:
[This is about ARIN, but curious to see if anybody has any insight...] A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3). If anyone has any insight, then I will welcome this insight in this specific case.
See the long thread on IETF v6ops: https://mailarchive.ietf.org/arch/msg/v6ops/ThaSy_hNlx1GP59EFAJ9NkBXP5A/ Noting, as I did there, the US DoD got a /13 (14x /22) around 2008.... so a /16 is peanuts ;) Greets, Jeroen
Hi, On Mon, Dec 11, 2023 at 07:49:37AM +0000, Eric Vyncke (evyncke) via ipv6-wg wrote:
[This is about ARIN, but curious to see if anybody has any insight...]
A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank).
Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3).
If anyone has any insight, then I will welcome this insight in this specific case.
I have done maths, and the result is impressive - like, 1+ billion /48 end-sites (assuming less-than optimal utilization)... I do not have any backgrounds beyond "ARIN does nibble boundaries", so if the network in question managed to argue for a /19, they would receive a /16 instead - which I find questionable. Nibbles are nice for ease of handling in the 32-28-24 range, but "beyond 24", maybe they are note exactly good stewardship. Still, a /19 would require a huge network, 100+ million /48 end-sites, and for a "financial market" company, there must be something we can't see for it to make sense... (and no, "get lots of IP addresses because they might turn out to be valuable assets" does not make sense either). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
On 2023 Dec 11 (Mon) at 07:49:37 +0000 (+0000), Eric Vyncke (evyncke) via ipv6-wg wrote: :[This is about ARIN, but curious to see if anybody has any insight...] : :A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). : :Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3). : :If anyone has any insight, then I will welcome this insight in this specific case. : :Regards : :-éric : Interestingly, they already had a /48 and a /36 allocation before receving this /16. https://bgp.tools/rir-owner/ARIN-CAPITA-120 -- If God had intended Man to Watch TV, He would have given him Rabbit Ears.
Wow, it is crazy to me that a company(not a network operator even) can get such a huge address space. Especially they have so many /19, /24 prefixes already. AFAIK, a TOP 3 Network operator serving more than 1B subscribers may only have a /18 or /17 IPv6 prefix. What kind of company can have more customers then 1B? Interesting. Thanks, C -----Original Message----- From: ipv6-wg <ipv6-wg-bounces@ripe.net> On Behalf Of Peter Hessler Sent: Monday, December 11, 2023 10:24 AM To: ipv6-wg@ripe.net Subject: Re: [ipv6-wg] Allocating a /16 to a large enterprise ? On 2023 Dec 11 (Mon) at 07:49:37 +0000 (+0000), Eric Vyncke (evyncke) via ipv6-wg wrote: :[This is about ARIN, but curious to see if anybody has any insight...] : :A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank). : :Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3). : :If anyone has any insight, then I will welcome this insight in this specific case. : :Regards : :-éric : Interestingly, they already had a /48 and a /36 allocation before receving this /16. https://bgp.tools/rir-owner/ARIN-CAPITA-120 -- If God had intended Man to Watch TV, He would have given him Rabbit Ears. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
On 11. 12. 23 08:49, Eric Vyncke (evyncke) via ipv6-wg wrote:
A colleague of mine showed me https://whois.arin.net/rest/net/NET6-2630-2 <https://whois.arin.net/rest/net/NET6-2630-2>, i.e., a /16 allocated by ARIN to Capital One (AFAIK a US bank).
Of course, this may be a tool bug, or a human encoding mistake, else I will start to fear an IPv6 addresses exhaustion in the future (only 2**13 of /16 out of 2000::/3).
We just had this discussion at APWG session at RIPE87 meeting in Roma - we could start doing allocations just on the nibble boundaries, therefore if they can prove that they have 512 million *connected* customers to which they plan to delegate a prefix of /48 - then they can have /16 :) But I doubt that a bank will ever have that number of connected customers (not just customers with the bank account ;) )... Cheers, Jan
participants (6)
-
Cheng Li -
Eric Vyncke (evyncke) -
Gert Doering -
Jan Zorz - Go6 -
Jeroen Massar -
Peter Hessler