This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] Allocating a /16 to a large enterprise ?

• Previous message (by thread): [ipv6-wg] follow up on the IPv6-wg session at RIPE 87
• Next message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Eric Vyncke (evyncke) evyncke at cisco.com
Mon Dec 11 08:49:37 CET 2023

[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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ipv6-wg/attachments/20231211/84b1087c/attachment.html>

• Previous message (by thread): [ipv6-wg] follow up on the IPv6-wg session at RIPE 87
• Next message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]