[arin-ppml] Recommended Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements

John Santos john at egh.com
Mon Jul 29 17:46:14 EDT 2019


In view of your clarification, I support the proposal.

On 7/29/2019 05:22 PM, Chris Woodfield wrote:
> John - this policy proposal does not prevent an organization from receiving resources from the wait list under section 4.1.8 and subsequently doing an 8.2 transfer of other resources afterwards; it only prohibits a 4.1.8 wait list application subsequent to doing an outbound 8.2 transfer.
> 
> It’s also OK per the policy to transfer resources after one has applied to space under 4.1.8, but before receiving that allocation - it only prevents the *application* under 4.1.8, as the actual receipt of resources could (and usually does) happen years afterwards.
> 
> Let me know if this clarification changes your position on the proposal.
> 
> Thanks,
> 
> -Chris
> 
>> On Jul 29, 2019, at 12:35 PM, John Santos <john at egh.com> wrote:
>>
>> I generally support the goal of this proposal, but I wonder if a one-time exception should be carved out for and organization which is switching to IPv6, no longer needs a large IPv4 allocation or assignment, and wishes to replace it with a new, much smaller distribution?  Would they be able to apply for and receive a new IPv4 /24 from the wait list, transfer market or the special IPv6 pool, and then sell their existing space under 8.2?  Or would they run afoul of the timing requirements of the proposed wording?  If they were permitted to do this, then I support.  (They could obviously carve out a /24 from their existing space and sell the rest, but that would greatly increase fragmentation.)




-- 
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539


More information about the ARIN-PPML mailing list