[address-policy-wg] IPv6 access to K-root

On Fri, 25 Feb 2005 21:00:05 +0100, Jeroen Massar wrote:

>If you say they are lying, then complain to RIPE NCC that they are doing
>their jobs wrongly. Apparently everybody who has gotten an allocation up
>to now have been able to reason that they need the allocation under the
>current policies. If you are not able to do so, though luck, you most
>likely don't need it in the first place then.

Sure they lie. I went on a BGP course a couple of years ago, and the instructor said that in his experience most people did because that's the only way to get what you need from RIPE. Current policies certainly don't fit us, for example. Looking in ripe-267, I see that in 5.1.1 there are four criteria for getting v6 space:

1) be an LIR - OK fine, we're an LIR.

2) not be an End Site - OK we're not.

3) plan to provide IPv6 connectivity to organisations - yes, we will certainly do that - to which it will assign /48s etc etc - no, we will never do that as all our customers are LIRs.

4) have a plan for making at least 200 /48 assignments to other organisations etc etc - no, we will never assign such space as all our customers have their own already.

We manage one network (GEANT) for which we have a /32. There is another network (EUMEDCONNECT) which we manage at present, but in two years we are expecting that the connected NRENs will set up their own managing entity, and the infrastructure (including address space) will be handed over to them. I managed to get PI v4 space last year for this but it seems there is no such thing as PI v6 space so unless I fib and say that we have connected 50k end users to GEANT, I don't see how I can obtain separate, routeable v6 space for EUMEDCONNECT.

We're an LIR, and an ISP, but we don't fit into the nice hierarchical tree that everyone assumes exists. For v4 we have an essentially similar problem. When GEANT's predecessor network, TEN-155, was being replaced we had to argue with RIPE about getting another /21 for GEANT. Well, now we have handed back the old /21 that we used for TEN-155. But the process should be easier than that.

In short, I would advocate relaxing the rules about PI space. 

-- Tim