TIM: Fri, 26 Apr 2024 06:05:03 +0000 -> Fri, 24 May 2024 01:05:03 +0000 SRC: VIA-Watcher/3.0 --- /home/vwhois/public_html/iana-utils/ipv6-watcher/stable.xml 2024-04-26 08:05:03.715821521 +0200 +++ /home/vwhois/public_html/iana-utils/ipv6-watcher/ipv6-unicast-address-assignments.xml 2024-05-24 03:05:03.332289312 +0200 @@ -0,0 +1,493 @@ + + + + + IPv6 Global Unicast Address Assignments + Internet Protocol version 6 (IPv6) Global Unicast Allocations + 2024-05-23 + + Allocations to RIRs are made in line with the Global Policy published at +. +All other assignments require IETF Review. + The allocation of Internet Protocol version 6 (IPv6) unicast address space is listed +here. References to the various other registries detailing the use of the IPv6 address +space can be found in the IPv6 Address Space registry. + The assignable Global Unicast Address space is defined in as the address block +defined by the prefix 2000::/3. was later obsoleted by . All address +space in this block not listed in the table below is reserved by IANA for future +allocation. + + + 2001:0000::/23 + IANA + whois.iana.org + ALLOCATED + 2001:0000::/23 is reserved for IETF Protocol Assignments . +2001:0000::/32 is reserved for TEREDO . +2001:1::1/128 is reserved for Port Control Protocol Anycast . +2001:1::2/128 is reserved for Traversal Using Relays around NAT Anycast . +2001:1::3/128 is reserved for DNS-SD Service Registration Protocol Anycast . +2001:2::/48 is reserved for Benchmarking . +2001:3::/32 is reserved for AMT . +2001:4:112::/48 is reserved for AS112-v6 . +2001:10::/28 is deprecated (previously ORCHID) . +2001:20::/28 is reserved for ORCHIDv2 . +2001:30::/28 is reserved for Drone Remote ID Protocol Entity Tags (DETs) . +For complete registration details, see . + + + 2001:0200::/23 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2001:0400::/23 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2001:0600::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + + 2001:0800::/22 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + 2001:0800::/23 was allocated on 2002-05-02. The more recent + allocation (2002-11-02) incorporates the previous allocation. + + + 2001:0c00::/23 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + 2001:db8::/32 reserved for Documentation . +For complete registration details, see . + + + 2001:0e00::/23 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2001:1200::/23 + LACNIC + whois.lacnic.net + ALLOCATED + + https://rdap.lacnic.net/rdap/ + + + + + + 2001:1400::/22 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + 2001:1400::/23 was allocated on 2003-02-01. The more recent + allocation (2003-07-01) incorporates the previous allocation. + + + 2001:1800::/23 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2001:1a00::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:1c00::/22 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + + 2001:2000::/19 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + 2001:2000::/20, 2001:3000::/21, and 2001:3800::/22 + were allocated on 2004-05-04. The more recent allocation + (2019-03-12) incorporates all these previous allocations. + + + 2001:4000::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:4200::/23 + AFRINIC + whois.afrinic.net + ALLOCATED + + https://rdap.afrinic.net/rdap/ + http://rdap.afrinic.net/rdap/ + + + + + 2001:4400::/23 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2001:4600::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:4800::/23 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2001:4a00::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:4c00::/23 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:5000::/20 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2001:8000::/19 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2001:a000::/20 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2001:b000::/20 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + + + + 2002:0000::/16 + 6to4 + + ALLOCATED + 2002::/16 is reserved for 6to4 . +For complete registration details, see . + + + 2003:0000::/18 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2400:0000::/12 + APNIC + whois.apnic.net + ALLOCATED + + https://rdap.apnic.net/ + + 2400:0000::/19 was allocated on 2005-05-20. 2400:2000::/19 was allocated on 2005-07-08. 2400:4000::/21 was +allocated on 2005-08-08. 2404:0000::/23 was allocated on 2006-01-19. The more recent allocation (2006-10-03) +incorporates all these previous allocations. + + + 2600:0000::/12 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + 2600:0000::/22, 2604:0000::/22, 2608:0000::/22 and 260c:0000::/22 were allocated on 2005-04-19. The more +recent allocation (2006-10-03) incorporates all these previous allocations. + + + 2610:0000::/23 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2620:0000::/23 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2630:0000::/12 + ARIN + whois.arin.net + ALLOCATED + + https://rdap.arin.net/registry + http://rdap.arin.net/registry + + + + + 2800:0000::/12 + LACNIC + whois.lacnic.net + ALLOCATED + + https://rdap.lacnic.net/rdap/ + + 2800:0000::/23 was allocated on 2005-11-17. The more recent allocation (2006-10-03) incorporates the +previous allocation. + + + 2a00:0000::/12 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + 2a00:0000::/21 was originally allocated on 2005-04-19. 2a01:0000::/23 was allocated on 2005-07-14. +2a01:0000::/16 (incorporating the 2a01:0000::/23) was allocated on 2005-12-15. The more recent allocation +(2006-10-03) incorporates these previous allocations. + + + 2a10:0000::/12 + RIPE NCC + whois.ripe.net + ALLOCATED + + https://rdap.db.ripe.net/ + + + + + 2c00:0000::/12 + AFRINIC + whois.afrinic.net + ALLOCATED + + https://rdap.afrinic.net/rdap/ + http://rdap.afrinic.net/rdap/ + + + + + 2d00:0000::/8 + IANA + + RESERVED + + + + 2e00:0000::/7 + IANA + + RESERVED + + + + 3000:0000::/4 + IANA + + RESERVED + + + + 3ffe::/16 + IANA + + RESERVED + 3ffe:831f::/32 was used for Teredo in some old but widely distributed networking stacks. This usage is +deprecated in favor of 2001::/32, which was allocated for the purpose in . +3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. + + + 5f00::/16 + Segment Routing (SRv6) SIDs + + ALLOCATED + 5f00::/16 is reserved for Segment Routing (SRv6) SIDs . +For complete registration details, see . + + + 5f01::/16 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f02::/15 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f04::/14 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f08::/13 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f10::/12 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + 5f20::/11 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f40::/10 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + + 5f80::/9 + IANA + + RESERVED + 3ffe::/16 and 5f00::/8 were used for the 6bone but were returned. . + + +