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] Next steps for new LIRs
- Previous message (by thread): [address-policy-wg] Next steps for new LIRs
- Next message (by thread): [address-policy-wg] Next steps for new LIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Wiesinger
sebastian at karotte.org
Thu Jun 11 16:41:28 CEST 2015
* David Huberman <David.Huberman at microsoft.com> [2015-06-11 16:03]: > Hello, > > I think it is time to consider the next step for dealing with the > problem of a few individuals opening up dozens of LIRs for the > exclusive purpose of selling the /22s. Such activity is outright > fraud, and something the NCC should tackle with the assistance of > the APWG. I agree but currently I don't have a good idea what else to do that will not interfer with normal LIR operation(s). One thing that came to my mind was to reinstate IPv4 requirements for that last /8? Perhaps require a specific use for the /22? I can already hear people shouting that this is not worth it. But the situation will probably get worse before it gets better. When ARIN runs out (hard) it might get worse even more so. It's impossible to see what the state of the system will be in 10 years but I'm still thinking we should preserve addresses for newcomers instead of letting people make money off of it (which they will probably NOT spend on IPv6 deployments). My hope is that the IPv4 market will get smaller in the same way that IPv6 grows and there are signs that IPv6 adoption is finally increasing in speed. So perhaps this problem will solve itself in the next few years. > Obvious point 2: The NCC staff likely know when a request is a > duplicate of previous requests. (Or at least, in many cases they > do.) > > We had discussed in Amsterdam that perhaps it was best to empower > the staff to stop the activity when it is clear to them that such > activity is taking place. So how about a policy sentence that reads > something like: > > "When RIPE NCC staff have reason to believe a LIR is being opened > for the purposes of selling the IPv4 block allocation, such a > request may be denied." The question is how would it be clear? I'm not so sure that this is something the NCC staff would be comfortable to decide. But perhaps we should ask the NCC if there are cases where they could be reasonably sure that a new LIR tries to game the system. (Like having ExampleCorp1-20 which are owned by the same person open 20 LIRs) Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 581 bytes Desc: Digital signature URL: </ripe/mail/archives/address-policy-wg/attachments/20150611/39e69917/attachment.sig>
- Previous message (by thread): [address-policy-wg] Next steps for new LIRs
- Next message (by thread): [address-policy-wg] Next steps for new LIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]