1 · Overview
Tahoma Radioelectric operates an open peering policy. We will exchange routes with any autonomous system that meets the baseline technical requirements below — without regard to traffic ratio, geography, or commercial relationship. All peering is informal: no contract, no SLA, no fees in either direction.
2 · Eligibility
- A current, maintained record in PeeringDB (asn, prefixes, contacts, MD5 policy).
- Authoritative IRR objects in RADB, ALTDB, or an RIR-operated registry.
- Signed RPKI ROAs for every announced prefix. We drop RPKI-invalids.
- A 24 × 7 NOC contact reachable within 30 minutes.
- Commitment to MANRS principles for network operators.
3 · Technical requirements
| parameter | requirement |
|---|---|
| Sessions | IPv4 and IPv6 route-server by default; bilateral on request. |
| Next-hop | Strictly on-switch. No next-hop-self. |
| MD5 | Not required. Accepted if mandated by peer. |
| BFD | Not required. Supported on bilateral sessions. |
| Max prefix | 850 000 (v4), 400 000 (v6). Alerts at 85%. |
| AS-PATH | Strict filtering via AS-SET. Updates processed nightly. |
| Communities | 65400:XXX informational set — see Annex A. |
| Graceful SD | Supported (RFC 8326). |
4 · What we will not do
- Announce prefixes for which we lack authorisation.
- Accept default routes from peers.
- Transit traffic between two peers (non-transit peering).
- Deprioritise peering traffic in favour of paid transit.
5 · Requesting peering
Mail peering@tahoma.net with your ASN, PeeringDB URL, and preferred session type. We respond within two business days.