BGP: Difference between revisions
mw push |
mw push |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:BGP | {{DISPLAYTITLE:BGP}} | ||
{{Term|BGP|Border Gateway Protocol (BGP)}} is how Internet networks exchange routes. With a BGP-announced 44Net subnet, you or your upstream provider advertises your subnet to the global Internet. | |||
ARDC does not provide connectivity or transit. It assigns the address space and authorizes the announcement, but you must arrange a connection to the Internet through an upstream provider and coordinate with them to advertise the route. | |||
== | === Putting your subnet on the Internet === | ||
Your subnet shows up in the global routing table when your upstream provider announces the subnet to its own upstreams and peers. The announcement can be made by your provider on your behalf, or you can run your own BGP router to announce the route yourself. You and your upstream will need to coordinate that. | |||
== | === Getting an ASN === | ||
Depending on what your upstream provider requires, you may not need your own {{Term|ASN|Autonomous System Number (ASN)}} to announce a 44Net subnet. Some providers will announce the route for you using their own ASN, while others require you to have your own ASN. | |||
If you need an ASN, you can request one from a {{Term|RIR|Regional Internet Registry (RIR)}}. There are currently five: [https://www.arin.net/ ARIN], [https://www.ripe.net/ RIPE], [https://www.apnic.net/ APNIC], [https://www.lacnic.net/ LACNIC], and [https://www.afrinic.net/ AFRINIC]. | |||
=== Authorization === | |||
When you are assigned a subnet, the Portal creates a {{Term|LOA|Letter of Authorization (LOA)}} showing the subnet's assignee (you) and your upstream provider. It identifies the prefix, authorized origin ASN or ASNs, and validity dates. Your upstream will want to see this before accepting the route. The LOA is available in the Portal under "Networks > My Networks" and can be downloaded as a PDF. | |||
=== Operation === | |||
You and your provider are responsible for routing, filtering, monitoring, and responding to incidents. Provider requirements vary; check that the provider can accept 44Net's authorization and routing records before ordering service. In particular, some upstreams require RPKI-based route origin validation (ROV), which is not currently supported by 44Net. See [[RPKI and ROAs on 44Net]] for more information. | |||
=== Get started === | |||
For you: follow the [[BGP/Quick Start|BGP Quick Start]] to coordinate with a provider, request address space, and activate the route. | |||
For your provider: share the [[Guide for ISPs]] with the provider for documentation requirements and current limitations. | |||
BGP is not for everyone, and it is not the only way to get your subnet out onto the Internet. If you might prefer not to bother with BGP, consider using [[44Net_Connect]] instead. | |||
[[Category:Explanation]] | |||
[[Category:Participation Methods]] | |||
[[Category:BGP]] | |||
[[Category:Infrastructure]] | |||
[[Category:Routing]] | |||
Latest revision as of 22:28, 28 September 2026
Border Gateway Protocol (BGP) is how Internet networks exchange routes. With a BGP-announced 44Net subnet, you or your upstream provider advertises your subnet to the global Internet.
ARDC does not provide connectivity or transit. It assigns the address space and authorizes the announcement, but you must arrange a connection to the Internet through an upstream provider and coordinate with them to advertise the route.
Putting your subnet on the Internet
Your subnet shows up in the global routing table when your upstream provider announces the subnet to its own upstreams and peers. The announcement can be made by your provider on your behalf, or you can run your own BGP router to announce the route yourself. You and your upstream will need to coordinate that.
Getting an ASN
Depending on what your upstream provider requires, you may not need your own Autonomous System Number (ASN) to announce a 44Net subnet. Some providers will announce the route for you using their own ASN, while others require you to have your own ASN.
If you need an ASN, you can request one from a Regional Internet Registry (RIR). There are currently five: ARIN, RIPE, APNIC, LACNIC, and AFRINIC.
Authorization
When you are assigned a subnet, the Portal creates a Letter of Authorization (LOA) showing the subnet's assignee (you) and your upstream provider. It identifies the prefix, authorized origin ASN or ASNs, and validity dates. Your upstream will want to see this before accepting the route. The LOA is available in the Portal under "Networks > My Networks" and can be downloaded as a PDF.
Operation
You and your provider are responsible for routing, filtering, monitoring, and responding to incidents. Provider requirements vary; check that the provider can accept 44Net's authorization and routing records before ordering service. In particular, some upstreams require RPKI-based route origin validation (ROV), which is not currently supported by 44Net. See RPKI and ROAs on 44Net for more information.
Get started
For you: follow the BGP Quick Start to coordinate with a provider, request address space, and activate the route.
For your provider: share the Guide for ISPs with the provider for documentation requirements and current limitations.
BGP is not for everyone, and it is not the only way to get your subnet out onto the Internet. If you might prefer not to bother with BGP, consider using 44Net_Connect instead.