[arin-ppml] ARIN-prop-152 RSA Modification Limits

Owen DeLong owen at delong.com
Fri May 27 20:05:12 EDT 2011


On May 27, 2011, at 4:37 PM, William Herrin wrote:

> On Fri, May 27, 2011 at 5:40 PM, Owen DeLong <owen at delong.com> wrote:
>> On May 27, 2011, at 1:57 PM, William Herrin wrote:
>>> For another, this language is needlessly verbose. "The recipient of an
>>> 8.3 transfer shall sign and adhere to the same RSA as a recipient of
>>> number resources under NRPM section 4." Nothing more needs be said.
>> 
>> We've been advised by staff that such a restriction will be viewed as
>> operational and not a policy matter and that we need to address the
>> specific RSA aspects that are a policy concern.
>> 
>> So, while I agree with you about it, the reality we are faced with is that
>> such a requirement has been deemed a non-policy matter by staff
>> and we need to do what we can within the bounds of policy.
> 
> No problem.
> 
> Old:
> 
> 8.3. Transfers to Specified Recipients
> 
> In addition to transfers under section 8.2, IPv4 number resources
> within the ARIN region may be released to ARIN by the authorized
> resource holder, in whole or in part, for transfer to another
> specified organizational recipient. Such transferred number resources
> may only be received under RSA by organizations that are within the
> ARIN region and can demonstrate the need for such resources, as a
> single aggregate, in the exact amount which they can justify under
> current ARIN policies.
> 
> 
> New:
> 
> 8.3. Transfers to Specified Recipients
> 
> In addition to transfers under section 8.2, IPv4 number resources
> within the ARIN region may be released to ARIN by the authorized
> resource holder, in whole or in part, for transfer to another
> specified organizational recipient. Receipt of the released number
> resources to the designated organization shall occur pursuant to the
> ordinary policies and procedures applied in and for section 4.
> 

I actually rather like that.

However, I'd still like to place some limitations on the ability to preserve
legacy status across an M&A transfer as well.

Owen




More information about the ARIN-PPML mailing list