Peering Policy: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Our peering policy is a work in progress.") |
No edit summary |
||
| Line 1: | Line 1: | ||
| + | * Peers must maintain a publicly routable ASN. |
||
| − | Our peering policy is a work in progress. |
||
| + | |||
| + | * 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 sorted then /24 (IPv4) or /64 (IPv6) |
||
| + | * Traffic must abide by the general rules and guidelines of the amateur radio community. |
||
| + | * Abusive peers will be removed without notice. |
||
| + | * No guarantees are provided. Peer at your own risk. |
||
| + | * This policy is subject to change without notice. |
||
Revision as of 11:50, 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 sorted then /24 (IPv4) or /64 (IPv6)
- Traffic must abide by the general rules and guidelines of the amateur radio community.
- Abusive peers will be removed without notice.
- No guarantees are provided. Peer at your own risk.
- This policy is subject to change without notice.