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/address-policy-wg@ripe.net/
[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck
ripe-lst at eirconnect.net
Mon May 1 19:25:19 CEST 2006
On Monday 01 May 2006 16:43, Gert Doering wrote: > a recurring fee involved shifts the balance a bit away from "PI is > purely convenient for the holder and puts the costs only on everybody > else" to "a portable IP block *does* have some costs attached". Am I completely wrong here, or does a LIR pay for the privilege of assigning IP space to end-users? Which, looking at some "ISP"s insane business models ( €200/year for a /29 - hello?) could be a profitable business in itself. Having said that, there is no technical reason why PA and PI should be different at all - if anyone with routable IPv[46] space would be required to be a RIR member that should appease the "It's unfair that we should pay and have to deal with RIRs and others don't" faction. It would also give them access to the relevant training and tools. The LIR function would then be altogether separate from the IP space request function. I predict some opposition from the RIRs, though... rgds, s.
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]