ARIN-prop-194 [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
ARIN-prop-194 Improving 8.4 Anti-Flip Language
Proposal Originator: David Huberman
Date: 6 January 2014
Problem Statement:
8.4 anti-flipping language states:
“Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include M&A transfers.”
This accidentally prevents anyone who receives BLOCK A in 2014 from transferring to another RIR a different block, BLOCK B, which was issued 5, 10, 15, 20 years ago. In my company, we needed to move a block being used in Asia over to APNIC. The block was legacy. But because we had gotten a new block in 2013, we were prevented from moving the old block to a different RIR.
With exhaustion imminent, I think we should remove this policy statement to:
- Stop the unintentional road blocks of real network situations
- Recognize that policy must adapt to post-exhaustion, so text like this will only cover very corner cases, and in those corner cases, may unintended bad consequences.
Policy statement:
Remove the language:
“Source entities within the ARIN region must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request. This restriction does not include M&A transfers.”
Comments:
a.Timetable for implementation: Immediate
b.Anything else:
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.