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] IXP pool lower boundary of assignments
- Previous message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
- Next message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Farmer
farmer at umn.edu
Thu Oct 27 23:58:14 CEST 2022
On Thu, Oct 27, 2022 at 4:21 PM Arnold Nipper <arnold.nipper at de-cix.net> wrote: > > I would have expected that you have to add serious content. Looks like > you are getting old, too. > Hopefully, you find this to be a serious comment; if not, my apologies ahead of time. ARIN has a policy for Reserved Pool Replentishemnet. https://www.arin.net/participate/policy/nrpm/#4-1-7-reserved-pool-replenishment It was ARIN-2019-21; https://www.arin.net/participate/policy/drafts/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 https://www.arin.net/participate/policy/nrpm/#4-4-micro-allocation https://www.arin.net/participate/policy/nrpm/#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 at 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 =============================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20221027/9c669172/attachment.html>
- Previous message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
- Next message (by thread): [address-policy-wg] IXP pool lower boundary of assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]