Peering Policy: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
*Peers must keep their IRR data up to date. |
*Peers must keep their IRR data up to date. |
||
*Peers must have a complete and up to date PeeringDB. |
*Peers must have a complete and up to date PeeringDB. |
||
| − | *Prefixes cannot be |
+ | *Prefixes cannot be shorter then /24 (IPv4) or /64 (IPv6) |
*Traffic must abide by the general rules and guidelines of the amateur radio community. |
*Traffic must abide by the general rules and guidelines of the amateur radio community. |
||
*Heavy traffic use will be throttled. We operate a microwave network with limited bandwidth. |
*Heavy traffic use will be throttled. We operate a microwave network with limited bandwidth. |
||
Latest revision as of 20:56, 20 December 2023
- Peers must maintain a publicly routable ASN.
- Peers must only send traffic from their own networks.
- Peers must only send traffic destined for routes we announce.
- Peers must have a reachable NOC email.
- Peers must keep their IRR data up to date.
- Peers must have a complete and up to date PeeringDB.
- Prefixes cannot be shorter then /24 (IPv4) or /64 (IPv6)
- Traffic must abide by the general rules and guidelines of the amateur radio community.
- Heavy traffic use will be throttled. We operate a microwave network with limited bandwidth.
- Abusive peers will be removed without notice.
- No guarantees are provided. Peer at your own risk.
- This policy is subject to change without notice.