[arin-ppml] ARIN-prop-174 Policies Apply to All Resources in the Registry

[Owen DeLong]

Let's try and be clear about what is being discussed here.

The placement of addresses on devices, the interconnection of those devices, and the extent to which any person or organization controlling devices actually accepts or denies the forwarding of packets or routing information is entirely outside of the purview of ARIN for all resources.

ARIN runs a registry. When John talks about transferring resources, he is not talking about the movement or use of the numbers themselves, but rather the change of association between those numbers and an ORG and/or group of POC records in the ARIN database.

ARIN has absolute authority over the content of that database and must administer it within the policies set by the community. Legacy holders that have no contract with ARIN receive services from ARIN based on the good will of ARIN and the ARIN membership and within the existing policies by which ARIN runs the registry and maintains the database.

Legacy holders are free to do whatever they want and ARIN has no power over the legacy holders themselves. However, ARIN does have full authority over the content of its database and the full ability to administer that database according to the community developed policies. As such, if ARIN discovers that legacy resources are being utilized by an organization other than the original registrant, policy dictates that ARIN attempt to contact the original registrant with several possible outcomes.
	+	An 8.2 transfer process is completed
	+	An 8.3 transfer process is completed
	+	The original registrant keeps the resources and addresses the issue of the
		current hijacking through whatever mechanism(s) are appropriate.
	+	The original registrant is unreachable or defunct in which case, ARIN should
		remove the registration and after an appropriate time permit a new registration
		to be created.
	+	The original registrant claims to have transferred the addresses to the current
		user, but the current user cannot meet ARIN policy for receipt of the addresses
		under 8.2 or 8.3 in which case, ARIN should advise the current user and remove
		the registration and permit new registration after a time.
	+	etc.

Note that none of these involves ARIN directing anyone to take any particular action. Each is strictly an update to the ARIN database in accordance with ARIN policy.

Owen


Sent from my iPad

On Jun 20, 2012, at 9:06 AM, Milton L Mueller <mueller at syr.edu> wrote:

> 
> 
>> -----Original Message-----
>> 
>> However, if you really do want to do something
>> different with your resources (like transfer them to another party) then
>> you need to get involved in the policy development process.
> 
> [Milton L Mueller] There you go, begging the question again. This is just another unilateral, verbal assertion of authority over an issue that is legally and politically contested. 
> 
> If ARIN has no contractual authority over the legacy holder, then on what basis can it claim that the legacy holder must get its approval before it transfers them to another party? 
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.