ARIN has a policy for Reserved Pool Replentishemnet.

It was ARIN-2019-21;

The basic idea of the policy is to return recovered resources allocated from reserved pools to their respective reserved pool, if they are ever returned, and to have a default action of replenishing the reserved pools when or if they get down to a three-year or less supply. Until then, other recovered resources go to the waiting list. Even then the idea is to only replenish reserved pools to or maintain a running three-year supply in each reserved pool; any resources recovered beyond that would still go to the waiting list.

Without this policy, when or if ARIN's reserved pools get low, they would run out unless we had a consensus for a policy to change things at that time to replenish them. However, with this policy, the default action is to replenish the reserved pools when or if they get low. Unless there is consensus at that time to let them run out, requiring policy action at that time.

Note ARIN policy has two reserved pools defined in sections 4.4 and 4.10

4.4. Micro-allocation (for Critical Infrastructure, including IXPs) and;

4.10. Dedicated IPv4 Block to Facilitate IPv6 Deployment

Also, resources from the reserved pool can only be transferred through M&A and not on the open market since they were reserved for special purposes.

This may or may not be how the RIPE community wishes to do things, but I thought it would be an option worth considering.

Thanks.

===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota  
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================