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/[email protected]/

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

Previous message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?
Next message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?

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

Jeroen Massar jeroen at massar.ch
Mon Dec 11 08:55:55 CET 2023


> On 11 Dec 2023, at 08:49, Eric Vyncke (evyncke) via ipv6-wg <ipv6-wg at 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

Previous message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?
Next message (by thread): [ipv6-wg] Allocating a /16 to a large enterprise ?

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

[ ipv6-wg Archives ]