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] Opposing policy 2015-01
- Previous message (by thread): [address-policy-wg] Opposing policy 2015-01
- Next message (by thread): [address-policy-wg] Opposing policy 2015-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Garry Glendown
garry at nethinks.com
Wed Jul 1 06:20:41 CEST 2015
Hi, > I oppose policy 2015-01 because it can affect LIRs which are not new but > they recently have received their /22 from last /8. (For example an LIR > which is registered in 2010 and just received its /22) > the LIR is not established to just receive the /22 but it has to wait for 2 I may misunderstand your reasoning, but that's why 2015-1 was desgined to do ... keep "dummy-LIRs" from being set up just to move the /22 to another LIR. > limitation. As a side effect it makes it harder for IP distribution which is > the main goal of RIPE. Actually, it aids it, as it keeps existing LIRs from going around and grabbing the available IP spaces and thereby keeping new entries from getting any ... please look at the ARIN region - they are down to ~140 /22 (fragmented into /23 and /24), which is still dropping quickly ... in contrast, RIPE's policies habe helped to still have a pool that might still last ~5 years ... -garry
- Previous message (by thread): [address-policy-wg] Opposing policy 2015-01
- Next message (by thread): [address-policy-wg] Opposing policy 2015-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]