Mailing List Archive

[Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21)and ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)]
Good point... I don't see the logic in allocating things that way either...
Maybe someone on the list who is associated with ICANN or IANA can shed some
light on the logic behind this...



-----Original Message-----
From: ipv6-ops-bounces+jimmys=myesn.com@lists.cluenet.de
[mailto:ipv6-ops-bounces+jimmys=myesn.com@lists.cluenet.de] On Behalf Of
Gert Doering
Sent: Tuesday, April 19, 2005 2:42 PM
To: Bernhard Schmidt
Cc: ipv6-ops@lists.cluenet.de
Subject: Re: [.Fwd: New IPv6 allocations from IANA to RIPE NCC (2a00::/21)and
ARIN (2600::/22, 2604::/22, 2608::/22, 260c::/22)]

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




================================================
Jimmy Sadri CISSP, CCSP, CCNP, MCSE, MCSA
Network Engineer
Network Security Analyst
CBK Instructor
Consultant
[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,

> 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).

I hope they get a clue real soon now. What is happening now is realy
annoying :-(

- Sander