Hi Gert, Because in my opinion, we should not make today any distinction in what the ISP is committing to (in terms of number of customers) to deploy IPv6, same way we don't have this rational with IPv4. Is just IP !, and moreover, we should facilitate the move to IPv6. Furthermore, if an IPv4 LIR/ISP (not end user) is requesting IPv6, not ANY more questions should be asked. If he doesn't route it within a "normal" time frame (5 years, whatever years, or what the market trend self-defines), then RIPE can always claim back the prefix, exactly the same as for IPv4. Right ? As I commented already in one of my previous emails, I will just give a /32 to every LIR/ISP (not end user) unless: 1) He explicitly states "I'm not going to use it" or 2) He request something bigger and properly justify it. I agree that if a bigger than /32 prefix is requested, then we should make sure if this make sense. Regards, Jordi ----- Original Message ----- From: "Gert Doering" <gert@space.net> To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> Cc: <address-policy-wg@ripe.net> Sent: Monday, June 21, 2004 9:04 PM Subject: Re: [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Hi,
On Mon, Jun 21, 2004 at 08:09:14PM +0200, JORDI PALET MARTINEZ wrote:
Why not compare with the IPv4 allocations ?
Why *do*? What relevance has IPv4 to IPv6 policy?
(But actually, the current size of an ISPs network *is* taken into account when considering larger-than-/32 allocations)
Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 60210 (58081)
SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
********************************** Madrid 2003 Global IPv6 Summit Presentations and videos on line at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.