[ARIN-consult] Consultation on Transfer Fees Now Open
Rob Seastrom
rs at seastrom.com
Sun Sep 11 22:22:47 EDT 2016
> On Sep 11, 2016, at 9:22 PM, John Curran <jcurran at arin.net> wrote:
>
> On Sep 11, 2016, at 5:20 PM, David R Huberman <daveid at panix.com> wrote:
>>
>> John,
>>
>> Two comments:
>>
>> 1) Would the proposed change -- moving transfer fees to the beginning of the process -- assist ARIN staff in stemming significant amount of possibly fradulent transfer requests?
>
> David -
>
> Definitely - we presently have a sizable number of requests made at no cost to the requester
> which do not appear to be legitimate, but are initiated speculatively and/or optimistically (i.e.
> in the hope that ARIN won’t detect the attempt at hijacking) The proposed change is unlikely
> to deter bona fide requests (as it does not change the cost of a successful transfer) but could
> easily change the economics for ones not made in good faith.
>
>> 2) Instead of assuming the source entity is going to be invoiced, please understand that in a 8.3 transfer, there are often 4 parties (source, recipient, broker, ARIN), and in a 8.4 transfer, there are at least 5 parties. Can ARIN please *ask* the submitter of the transfer request to identify the party who will pay the transfer fee, and create an invoice accordingly?
>
> Interesting point - I believe this can be done (and will confirm shortly.)
It seems to me that in order for this to be maximally effective at eliminating the workload associated speculative filings, ARIN would need to not only create an invoice, but delay moving forward with checking the provenance of the number resources in question until after the invoice was paid. This exercise is reminiscent of the tradeoffs in TCP fast open vs. syn cookies with an eye towards attack surface minimization.
regards,
-r
More information about the ARIN-consult
mailing list