Mailing List Archive

[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)]
Hi,

since it also has operational relevance (BGP filters, whois updates and
so on), does anyone actually know the new allocation policy IANA follows
starting with those allocations?

It is obviosly not the old /12 per RIR proposal, looking at the blocks
allocated it looks like an /7 or /8 per RIR. Can anyone comment and also
provide the blocks for APNIC, LACNIC and AfriNIC (if already known)?

Thanks
Bernhard

-------- original message --------
Subject: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN
(2600::/22, 2604::/22, 2608::/22, 260c::/22)
Date: Tue, 19 Apr 2005 16:30:55 -0400
From: Doug Barton <barton@iana.org>
To: doug.barton@icann.org


Greetings,

This is to inform you that the IANA has allocated the following one (1)
IPv6 /21 block to RIPE NCC:

2A00:0000::/21 RIPE NCC


And, the IANA has allocated the following four (4)
IPv6 /22 blocks to ARIN:

2600:0000::/22 ARIN
2604:0000::/22 ARIN
2608:0000::/22 ARIN
260C:0000::/22 ARIN

For a full list of IANA IPv6 allocations please see:
<http://www.iana.org/assignments/ipv6-unicast-address-assignments>

--
Doug Barton
General Manager, The Internet Assigned Numbers Authority
[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)] [ In reply to ]
Hi,

On Tue, Apr 19, 2005 at 11:08:27PM +0200, Bernhard Schmidt wrote:
> From: Doug Barton <barton@iana.org>
> To: doug.barton@icann.org
>
>
> And, the IANA has allocated the following four (4)
> IPv6 /22 blocks to ARIN:
>
> 2600:0000::/22 ARIN
> 2604:0000::/22 ARIN
> 2608:0000::/22 ARIN
> 260C:0000::/22 ARIN

Does anyone know what they are smoking?

<politically correct>
What is happening here? How do these allocations ICANN->ARIN come
to be? Why are they allocating /22s at /14 (!) boundaries?

This sort of looks like "ICANN is sticking to the classic /21 allocations,
but four BIG requests have been made, been granted a /22, and ICANN is
trying to reserve room for growth".
</politically correct>

Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 71007 (66629)

SpaceNet AG Mail: netmaster@Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)] [ In reply to ]
On Tue, Apr 19, 2005 at 11:41:47PM +0200, Gert Doering wrote:
> This sort of looks like "ICANN is sticking to the classic /21 allocations,
> but four BIG requests have been made, been granted a /22, and ICANN is
> trying to reserve room for growth".

Should'nt this be a matter of the RIRs, instead of IANA/ICANN?

--
http://www.ukeer.de/about.html

<many> kinder sind live immer suess. :)
<aphro> selber machen macht gluecklich :-P
[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)] [ In reply to ]
Hi,

On Wed, Apr 20, 2005 at 10:07:25AM +0200, Rico -mc- Gloeckner wrote:
> On Tue, Apr 19, 2005 at 11:41:47PM +0200, Gert Doering wrote:
> > This sort of looks like "ICANN is sticking to the classic /21 allocations,
> > but four BIG requests have been made, been granted a /22, and ICANN is
> > trying to reserve room for growth".
>
> Should'nt this be a matter of the RIRs, instead of IANA/ICANN?

"this" being "what"?

The allocation to the LIR is made by the RIRs, of course, but if the
RIR only has a /23 (not /21, that was a typo) for itself, and LIRs
are granted a /22, the corresponding RIR needs space from ICANN/IANA...

This has happened a number of times already in the past (Telia and C&W
allocations, for example), and clearly demonstrates that "/23s from ICANN
to RIR" doesn't work.

Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 71007 (66629)

SpaceNet AG Mail: netmaster@Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)] [ In reply to ]
On Wed, Apr 20, 2005 at 10:34:19AM +0200, Gert Doering wrote:
> Hi,
>
> On Wed, Apr 20, 2005 at 10:07:25AM +0200, Rico -mc- Gloeckner wrote:
> > On Tue, Apr 19, 2005 at 11:41:47PM +0200, Gert Doering wrote:
> > > This sort of looks like "ICANN is sticking to the classic /21 allocations,
> > > but four BIG requests have been made, been granted a /22, and ICANN is
> > > trying to reserve room for growth".
> >
> > Should'nt this be a matter of the RIRs, instead of IANA/ICANN?
>
> "this" being "what"?

I blindly assumed that "reserving room for growth" means growth of an
LIR. IMVHO this should be left for the RIR to be done and IANA/ICANN
should give them enough space for the RIR to make plans about that.


--
http://www.ukeer.de/about.html

<many> kinder sind live immer suess. :)
<aphro> selber machen macht gluecklich :-P
[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21) and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)] [ In reply to ]
hi,

On Wed, Apr 20, 2005 at 10:43:02AM +0200, Rico -mc- Gloeckner wrote:
> > "this" being "what"?
>
> I blindly assumed that "reserving room for growth" means growth of an
> LIR. IMVHO this should be left for the RIR to be done and IANA/ICANN
> should give them enough space for the RIR to make plans about that.

Yes.

Would you please take a big cluestick and explain that to ICANN/IANA?

My efforts are failing... (but there *are* rumors that some sort of
reasonable new policy compromise will be achieved "real soon now", but
I have no details yet).

Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 71007 (66629)

SpaceNet AG Mail: netmaster@Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234