> On Apr 6, 2016, at 8:11 PM, Gary Buhrmaster <[email protected]> wrote:
>
>> On Tue, Mar 22, 2016 at 4:55 PM, ARIN <[email protected]> wrote:
>> ....
>> Policy statement:
>>
>> Add to Section 8.3 and Section 8.4 under the "Conditions on source of the
>> transfer:"
>>
>> Address resources from a reserved pool (including those designated in
>> Section 4.4 and 4.10) are not eligible for transfer.
>
> I am in favor of the intent, although I would have
> (at first thought) expected that the "resources
> transferred will be subject to ARIN policies"
> would have resulted in a review of the recipients
> planned usage. However, given the possible
> interpretations (which historically any ambiguity
> goes in favor of the requester), I can see that
> some improvements might be valuable. However,
> I would suggest that the proposed language be
> modified to allow for a transfer if the recipient
> would otherwise meet the requirements that could
> be used to approve the resources from the reserved
> block.
>
> What about something like:
>
> "Recipients of resources from a reserved pool ....
> must demonstrate that the recipient would
> qualify for those resources under existing policy,
> and the resources may not be transferred out
> of region".
I like this approach better than the originally proposed text. To prevent
ambiguity around which existing policy applies, perhaps:
> "Recipients of resources from a reserved pool ....
> must demonstrate that the recipient would
> qualify for those resources under the policy criteria for that reserved pool.
> Resources from such reserved pools are not eligible for inter-RIR transfer."
-Scott
_______________________________________________
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:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
