Getting an ASN in ARIN

Mon Jan 6 17:50:55 UTC 2020

If by "strict" you mean that ARIN requires that you follow their published rules, then yes, I suppose this could be called strict. But that's not a bad thing. Getting an ASN only requires that you prove you have contracts with two BGP-capable upstream providers. There is no shortage of ASNs. Other transfers are straigtforward within ARINs rules, one of which being that you're entitled to the space you're trying to transfer, and the other that the recipient qualifies under ARIN's usage requirements.

 -mel
________________________________
From: NANOG <nanog-bounces at nanog.org> on behalf of thomas brenac via NANOG <nanog at nanog.org>
Sent: Friday, January 3, 2020 11:41 AM
To: nanog at nanog.org <nanog at nanog.org>
Subject: Getting an ASN in ARIN

Hi,

Happy new year everyone.

I know ARIN is very strict with IP transfers at least from ARIN to ARIN.
I know they require very detailed information. Curious if someone in the
list know if they are equally strict when issuing an ASN and/or have a
recent experience on the matter ?

Thanks you

--
Thomas BRENAC
https://www.brenac.eu
+33686263575

Certified IPv4 Broker by RIPE NCC, APNIC and LACNIC

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
This message has been sent as a part of discussion between BRENAC EURL and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding.
We puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message is error and virus-free. Unfortunately, full security of the email cannot be ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of this email.
The views and opinions included in this email belong to their author and do not necessarily mirror the views and opinions of the company. Our employees are obliged not to make any defamatory clauses, infringe, or authorize infringement of any legal right. Therefore, the company will not take any liability for such statements included in emails. In case of any damages or other liabilities arising, employees are fully responsible for the content of their emails.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200106/5f9c85d8/attachment.html>