Just to be clear what market incentives we are affecting with these waiting list considerations.
These considerations apply to non-fraudsters. Defunct orgs will keep paying the ARIN bill if it is profitable to do so, in order to maintain the ability to sell/lease later. Orgs will wait out any period, sitting with unused addresses until they reach the resale date. Not efficient use. People will lease unused addresses to others and Whois accuracy will suffer if they can’t resell them. Not accurate registration. Each of these is likely to occur with the increase in waiting period and/or the prevention of resale. Prevent fraud by all reasonable means, but realize this is a balancing act, and my post was in reference to where on the scale we place the fulcrum. I think we should give everybody currently on the list up to a /19 and then restrict new entries to a /22. I think a 5 year resale wait is too long, based on the paltry resales of prior waiting-list subnets smaller than /19. I think we are over-reacting to a single miscreant and are in danger of throwing the baby out with the bathwater. The list was working pretty well in my estimation, if we can erect simple mechanisms to prevent future fraud, then we should try them first instead of a more complex, multi-aspect solution involving size caps AND resale restrictions. I support a /22 restriction for new entrants, a /19 max for current list members, and maintenance of the 12 month wait for simplicity’s sake. Remember, in RIPE and APNIC, the “special” blocks all begin with 185 or 103. Not so with these blocks, which are indistinguishable from other blocks. A small thing, but why go that extra step of creating a new address class in ARIN if we can avoid it? Regards, Mike From: ARIN-PPML <[email protected]> On Behalf Of Fernando Frediani Sent: Wednesday, May 29, 2019 8:51 AM To: [email protected] Subject: Re: [arin-ppml] Waiting List IPv4 blocks transferred after issuance +1 On 28/05/2019 23:52, Owen DeLong wrote: Mike, Yes and no. I believe that the lack of legacy holders for any blocks issued under 4.1.8 reduces the need for the market. Defunct organizations can easily be reclaimed in this space because they stop paying their ARIN bill. Eliminating the resale value of these addresses won’t really encourage squatting on them and limiting the size of organization and size of block that can benefit from 4.1.8 further helps to reduce the potential for hoarding. I realize that as a broker, any address that can’t be monetized is a lost opportunity for your organization, but I think there’s plenty of addresses out there that haven’t been processed through 4.1.8, so I don’t think limiting the resale potential of such blocks to reduce fraud is a bad idea. Owen On May 28, 2019, at 12:46 , Mike Burns <[email protected] <mailto:[email protected]> > wrote: The percentages of blocks transferred takes a significant leap at the /19 size. Below that, the percentages are all below 7%. At /19 and above, the percentages are all above 21%. Seems like a natural demarcation for maximum block size, but prices do continue to rise. While we want to fight fraud, we should still remember the underlying reasons for the Ipv4 transfer market apply to these addresses as well. That is, the market provides incentives for efficient use and accurate registration. Regards, Mike From: ARIN-PPML < <mailto:[email protected]> [email protected]> On Behalf Of John Curran Sent: Tuesday, May 28, 2019 1:53 PM To: ARIN-PPML List < <mailto:[email protected]> [email protected]> Subject: [arin-ppml] Waiting List IPv4 blocks transferred after issuance Importance: High Folks - It occurred to me that it might be useful to have a quick summary of waiting list blocks issued and subsequently transferred. Attached is the distribution (count per prefix size) of all blocks that have been issued via ARIN's waiting list policy and subsequently transferred via NRPM 8.2/8.3/8.4 policy. FYI, /John John Curran President and CEO American Registry for Internet Numbers <image001.png> _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ( <mailto:[email protected]> [email protected]). Unsubscribe or manage your mailing list subscription at: <https://lists.arin.net/mailman/listinfo/arin-ppml> https://lists.arin.net/mailman/listinfo/arin-ppml Please contact <mailto:[email protected]> [email protected] if you experience any issues. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected] <mailto:[email protected]> ). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] <mailto:[email protected]> if you experience any issues.
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
