This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)
- Previous message (by thread): [address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)
- Next message (by thread): [address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Timothy Clarke
timothy.clarke at thecloud.net
Wed Jan 16 14:09:29 CET 2008
michael.dillon at bt.com wrote: >> When a customer comes to an ISP saying I have a PI and here >> is my prefix. >> I'm assuming most ISP's do a DB lookup to confirm those >> details are correct, before advertising, are we saying RIPE >> now need to notify ISP's that a prefix should be withdrawn >> because it hasn't been paid for ? > > Why should RIPE notify anyone when the PI block has already > been removed from the RIPE DB? > >> Depending on the cost / importance of the contract with the >> ISP are they going to pay these fees? Will the fees be part >> of the ISP's contract so avoid the situation above? > > The contract between RIPE and the holder of the PI block does > not involve the ISP at all. I know that IPv4 PIs are currently > acquired through an ISP but I am suggesting that we stop this > practice, and for IPv6 PI allocations, we only do them with > a direct two-party contractual and commercial relationship > between the PI holder and RIPE. > >> As for the whole non-routable question. Would the block then >> be charged at a different rate because there won't be >> additional cost of a route entry in the global table? > > Not at all. Routability is a choice that the PI holder makes. > Nothing that RIPE does has any effect on routability. My whole point (as flawed as it may be) is, If RIPE is going to charge Annual fees for PI is it a) Cheaper if you're never going to have it in the global routing table (that seems to be the idea behind charging for PI)? b) What happens when someone stops paying RIPE but keeps using their PI? > >> The point some are trying to make is there are few LIR's that >> can fully justify IPv6 PA space right now because they don't >> have the customers. > > There is no customer requirement to get IPv6 PA space. > >> Perhaps the policy needs to change for the initial IPv6 PA so >> new & existing LIR's can get IPv6 even if they have no customers. > > They already can do this. I guess I was looking at an out of date document. I've just found. From http://www.ripe.net/ripe/docs/ripe-421.html 5.1.1. Initial allocation criteria To qualify for an initial allocation of IPv6 address space, an organisation must: * a) be an LIR; * b) advertise the allocation that they will receive as a single prefix if the prefix is to be used on the Internet; * c) have a plan for making sub-allocations to other organisations and/or End Site assignments within two years.
- Previous message (by thread): [address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)
- Next message (by thread): [address-policy-wg] 2008-01 New Policy Proposal (Assigning IPv6 PI to Every Inetnum Holder)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]