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] Policy/practice on holding back space before reallocation?
- Previous message (by thread): [address-policy-wg] 2011-04 Implementation: Extension of the Minimum Size for IPv6 Initial Allocation
- Next message (by thread): [address-policy-wg] RIPE65 - Agenda, first draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Heather Schiller
heather.skanks at gmail.com
Mon Aug 13 21:15:19 CEST 2012
I have not been able to find this info on RIPE's website. Does anyone know the amount of time RIPE holds back a 'deregistered number resource' before allocating it? I found this document that describes the deregistration process for a resource holder: https://www.ripe.net/ripe/docs/ripe-517 In general it gives the resource holder 4 weeks to object and 3 months to remediate. It does not describe how long RIPE will hold back deregistered IP's before allocating them out again. For example, ARIN used to hold back for one year.. they recently announced they were preparing to drop from 6 months hold to 3 months hold - here is the announcement: https://www.arin.net/announcements/2012/20120717.html It's way down 3rd paragraph from the end. "One last change relates to the amount of time that ARIN will hold recovered IPv4 resources prior to reissuance. The hold time for all returned, reclaimed and revoked IPv4 resources will be reduced from six to three months." Does RIPE have a similar practice. Thanks, --Heather
- Previous message (by thread): [address-policy-wg] 2011-04 Implementation: Extension of the Minimum Size for IPv6 Initial Allocation
- Next message (by thread): [address-policy-wg] RIPE65 - Agenda, first draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]