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] IPv4 waiting list policy
- Previous message (by thread): [address-policy-wg] IPv4 waiting list policy
- Next message (by thread): [address-policy-wg] IPv4 waiting list policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Dec 7 18:43:52 CET 2021
> On 7 Dec 2021, at 17:25, denis walker <ripedenis at gmail.com> wrote: > > I am sure some back door dealings can be arranged to keep > the LIRs active that have the allocations registered and obfuscate the > fee payments to confuse the RIPE NCC. Have companies developed some > sense of morality in recent years? Unlikely. Especially for pretendy new LIRs that are hoping for a quick buck. However, we have to face facts. No v4 allocation scheme will ever be perfect. Some gaming and scams are inevitable. They always were. There will always be bad actors trying to find a loophole or two. In our post v4 world, we just have to suck it up. IMO here are the questions to consider: how much effort should this WG spend (waste?) tweaking policies for the last few drops of v4? how much time and money should the NCC spend on its address police? are those costs worth the benefit(s)? is any of this a productive and worthwhile thing to do? The least-worst option IMO would be to stop transfers of the final /24s from some date in the very near future. [We can’t impose that retroactively.] And have some agreed course of action for these blocks whenever it turns out they later change hands.
- Previous message (by thread): [address-policy-wg] IPv4 waiting list policy
- Next message (by thread): [address-policy-wg] IPv4 waiting list policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]