During its recent meeting held on 23 August 2016, the ARIN Board of
Trustees considered a change to the fee schedule as it pertains to both
Number Resource Policy Manual (NRPM) section 8.3 and 8.4 transfers
(https://www.arin.net/policy/nrpm.html#eight3).

Currently about 25% of ARIN transfer request processing results in an
unsuccessful outcome, i.e. in 1 out of 4 requests, the transfer is
either abandoned or not approved. When transfer requests are
unsuccessful, ARIN incurs essentially the same processing costs as it
does for successful transfers.

To appropriately recover these costs, ARIN proposes collecting the
present $500 Resource Transfer fee at the beginning of the transfer
process as a non-refundable transfer processing fee. This fee would be
only be applicable to source organizations which do not have a
Registration Services Agreement (RSA) or Legacy Registration Services
Agreement (LRSA) when an 8.3 or 8.4 transfer request is submitted. This
fee change would replace the $500 Resource Transfer fee
(https://www.arin.net/fees/fee_schedule.html) that is currently
collected at the end of the transfer process for approved requests.

We are seeking community feedback on this modification to ARIN’s Fee
schedule.

This consultation will remain open for (30) days, after which a summary
will be provided to the Board of Trustees for their consideration.

Please provide comments to [email protected]. You can subscribe to
this mailing list at:
http://lists.arin.net/mailman/listinfo/arin-consult.

Discussion on [email protected] will close on 30 September 2016.

If you have any questions, please contact us at [email protected].

Regards,

John Curran
President and CEO
American Registry for Internet Numbers (ARIN)



_______________________________________________
ARIN-Announce
You are receiving this message because you are subscribed to
the ARIN Announce Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-announce
Please contact [email protected] if you experience any issues.

Reply via email to