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] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] can deadbeat LIRs reverse IPv4 exhaustion?
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Wed Feb 6 11:40:41 CET 2019
> On 6 Feb 2019, at 09:39, Daniel Karrenberg <dfk at ripe.net> wrote: > > d) The length of the waiting list and other practicalities should be > secondary considerations after these principles above. For instance, the > RIPE NCC can always recover the costs incurred by the process from those > using it. That could be awkward Daniel. For instance fair and equitable treatment. Or raising barriers to entry. Then there are the overheads of all that extra bean counting. Passing these costs along is all very well, but why go to the trouble of creating them in the first place? This would also be the start of a slippery slope. Once the NCC introduces hypothecated fees for specific services, it’ll have to do that for everything it does. Which would lead to the membership micromanaging budgets and declining to pay for the stuff they don’t want/support.
- Previous message (by thread): [address-policy-wg] can deadbeat LIRs reverse IPv4 exhaustion?
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]