1 · Overview
Tahoma Radioelectric operates an open peering policy for AS402465. We exchange routes with networks that can keep clean routing data, maintain operational contacts, and meet the baseline technical requirements below. Peering is settlement-free unless otherwise agreed in writing.
2 · Eligibility
- A current PeeringDB record with ASN, prefixes, contacts, and MD5 policy.
- Current IRR objects in RADB or an RIR-operated registry.
- Signed RPKI ROAs for every announced prefix.
- A reachable NOC contact for operational issues.
- No default-only peers, route leaks, or traffic exchange between third-party peers.
3 · Technical requirements
| parameter | requirement |
|---|---|
| Sessions | IPv4 and IPv6 route-server sessions by default; bilateral on request. |
| Next-hop | Strictly on-switch. No third-party next-hop without coordination. |
| MD5 | Accepted if required by the peer. |
| BFD | Supported where the peer and platform both support it. |
| Max prefix | Negotiated per peer. We alarm before session teardown. |
| AS-PATH | Filtered using peer AS-SET and RPKI validation. |
| Graceful SD | Supported when the peer signals it. |
4 · Announcements
| prefix | origin | purpose |
|---|---|---|
| 156.239.23.0/24 | AS402465 | public IPv4 services and edge reachability |
| 2620:19:c000::/48 | AS402465 | public IPv6 aggregate |
5 · Requesting peering
Mail peering@tahoma.network with your ASN, PeeringDB URL, desired session type, and maintenance contact. We normally respond within two business days.