New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Research tomesh AS #20
Comments
Doing some research: https://www.arin.net/resources/fees/fee_schedule/ AS:Initial fee for ASN: $550 IP:IPv4 /24 - $250 yearly First year cost: Yearly cost: Requirements: |
Spoke to some one in nycmesh that owns an ASN
So Initial cost $550 Ongoing costs |
Please update my proposal to Hypha when you know the actual cost we will be aiming for |
👋😃 |
My understanding is as follows Initial cost $550 Ongoing costs (yearly) Once we setup an ARIN account (before we become an ARIN member) we can request a confirmation of costs from them |
@ASoTNetworks can you take this ticket since you're also working on hyphacoop/organizing#329 on Hypha side? |
I have revived the quote from ARIN and have been updating the ticket here hyphacoop/organizing#329 to keep it in one place. |
I guess the next steps are:
@ASoTNetworks @darkdrgn2k what is the timeline for this? |
@dasanchez maybe once we set up open collective you can be our first contributor :) |
Transfer of resource: Source: https://www.arin.net/resources/fees/fee_schedule/
Source: https://www.arin.net/resources/registry/transfers/quickguide/
|
This initial comment is collaborative and open to modification by all.
Task Summary
🎟️ Re-ticketed from: #
📅 Due date: N/A
🎯 Success criteria: Get or Reject a tomesh AS
Summary
ARIN
To gain ownership of an IPv4 or IPv6 Public Internet IP Space you must register with a Regional Internet Registry. The North America registry is called ARIN. Once registered we can apply for a IP address size for both IPv4 and IPv6.
AS number
When applying for a IP range we will also be given an AS number. This AS number is used to announce the location of these IP addresses to the internet.
Reasons for requiring an AS
Multiple Exit Nodes support
When using multiple exit nodes, the ability to announce the same IP address for each one will allow for more resilience on the mesh. Just like outbound connections could use any exit node, inbound connections could also be routed through any exit node.
Possibly not as important when using NAT
Public IP routing inside of mesh
With an assigned AS we can router the IPv4 addresses into our mesh. The means that members can be given a publicly routable IPv4 IP address that lives on the mesh and is reachable from the internet.
Additionally publicly routable IPv6 addresses could also be handed out inside the mesh to every user.
TORIX Peering
To peer with TORIX you require your own IP range to announce. Torix is a "short cut" to many of the larger organizations that have presence in Toronto. This shortcut would lower the dependence on our internet egress.
Easier donate ask
IPv4 are a rare commodity and many transit contacts may not wish to donate theirs. By being able to bring our own IPv4 addresses, it may be easier to ask for service since it would not require depleting their ipv4 pools.
Puts on on the "MAP"
By owning an AS and an IP range we could be seen as more then a few hobbits and serious players in the "internet" game.
To Do
The text was updated successfully, but these errors were encountered: