Regarding the IPv6 Request Form for Internet Exchange Points
Hello, The robot at hostmaster@ seems to mistake the IPv6 form for IXPs as an IPv4 form? When you others on this list applied for your address space, did you just send it directly as NO AUTO? And additionally, as there is no published IPv4 procedure for exchanges, how have you handled this situation? (Any other words of experience that might help me? ;-) -- Aleksi Suhonen / +358 45 6702048 TREX Tampere Region Exchange Oy www.trextampereregionexchange.fi
Hello, Quote from Aleksi Suhonen: } And additionally, as there is no published IPv4 procedure for } exchanges, how have you handled this situation? I gather that the NCC would like to assign a /27 or a /26 as the peering mesh of a startup exchange point unless we claim that in two years we will grow to the size other exchanges have taken five or ten years to grow to... This doesn't seem right to me. -- Aleksi Suhonen / TREX Tampere Region Exchange Oy
Hi Aleksi, I'm sorry the robot is not functioning correctly for IPv6 IXP requests. Work to replace the system is almost complete. You mentioned the size of address space that can be assigned to an IXP. The current policy only allows us to assign address space to meet a network's expected needs over a period of two years: "Assignment criteria for both kinds of address space will be exactly identical with regards to the amount of address space assigned, the registration requirements, etc. This also implies that assigning PI space prefixes longer than 24 bits is perfectly acceptable if the request does not merit 8 bits of address space to be assigned." "Provider Independent versus Provider Aggregatable Address Space" http://www.ripe.net/ripe/docs/pi-pa.html#toc6 The PI Task Force has been reviewing the policy for assigning portable address space. I have just posted a summary of the PI Task Force's recent discussions on the Address Policy WG mailing list. This may be of interest. http://www.ripe.net/ripe/mail-archives/address-policy-wg/2003/msg00030.ht ml Regards, -- leo vegoda RIPE NCC Registration Services Manager
participants (2)
-
Aleksi Suhonen -
leo vegoda