TG
The steps we take with regards to de-registration and quarantine are also described in:
https://www.ripe.net/manage-ips-and-asns/resource-management/quarantine-for-returned-internet-number-resources
The resources are held in quarantine long enough to allow interested parties to notice the de-registration and remove potential blacklisting records. Furthermore, we only re-use address space that is not routed.
We'd like to note that in April 2018, we finished allocating IPv4 blocks from the previously-unused 185.0.0.0/8.
https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations
Since then, we issued more than 9,000 /22 IPv4 allocations - all of them were from address blocks that were already issued in the past and then de-registered and re-used. Sometimes we receive questions about incorrect geo-location for such address blocks (which are still pointing to the previous resource holders). In a few recent cases, we have seen reports about newly issued blocks being blacklisted.
When requested, we contact relevant blacklisting providers to clarify the situation about resources being re-used and ask them to remove existing listings related to previous resource holders.
We are currently reviewing our procedures to see if we could pro-actively provide blacklisting providers with information on address blocks returned to our free pools. This could help to reduce the possibility of re-issued blocks being blacklisted.
https://www.ripe.net/manage-ips-and-asns/resource-management/quarantine-for-returned-internet-number-resources
The resources are held in quarantine long enough to allow interested parties to notice the de-registration and remove potential blacklisting records. Furthermore, we only re-use address space that is not routed.
We'd like to note that in April 2018, we finished allocating IPv4 blocks from the previously-unused 185.0.0.0/8.
https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations
Since then, we issued more than 9,000 /22 IPv4 allocations - all of them were from address blocks that were already issued in the past and then de-registered and re-used. Sometimes we receive questions about incorrect geo-location for such address blocks (which are still pointing to the previous resource holders). In a few recent cases, we have seen reports about newly issued blocks being blacklisted.
When requested, we contact relevant blacklisting providers to clarify the situation about resources being re-used and ask them to remove existing listings related to previous resource holders.
We are currently reviewing our procedures to see if we could pro-actively provide blacklisting providers with information on address blocks returned to our free pools. This could help to reduce the possibility of re-issued blocks being blacklisted.
