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] 2006-05 New Policy Proposal (PI Assignment Size)
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Tue Sep 19 23:22:21 CEST 2006
> Even if you can have a crystal ball that predicts your future addressing > requirements for arbitrary amounts of time into the future, this still > has a 1:1 ratio of end user organization to routing prefix and every > flap of that prefix has to get propagated globally. Then we're stuck with a situation where on the one hand, RIPE membership is pressing for the continuation of a non-scalable addressing policy out of commercial necessity, but on the other, there are no real policy disincentives to discourage end-users from this harmful practice. This is quite an absurd situation, really. This policy inconsistency needs to be fixed urgently. And the most appropriate way of doing it is to apply both an initial and recurring charge to PI assignments. This is a reasonable system which will deal with not only the financial reality that IRRs cost money to run, but will also act as a much-needed disincentive to applying for PI space. Nick
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]