AS pending · Peering
Peering policy
We operate an open peering policy. We peer with any network that meets the technical requirements below, at any exchange where we are both present.
Summary
- Policy
- Open
- AS number
- Pending assignment
- IRR as-set
- AS-STRATLINE
- Suggested max-prefix
- IPv4: 50 · IPv6: 50
- Route servers
- Yes, at all connected IXPs
- Private interconnects
- Considered above 1 Gbps sustained
- Peering contact
- peering@stratline.net
Requirements
- A publicly routable ASN and an up-to-date PeeringDB record.
- Prefixes registered in a public IRR (RIPE, ARIN, RADB or similar), with an as-set or aut-num we can build filters from.
- Valid RPKI ROAs for announced prefixes are strongly preferred.
- A reachable 24/7 NOC contact for operational issues.
- Sessions over both IPv4 and IPv6 where both are available.
- No static or default routes pointed at us, and no announcing third-party prefixes without authorisation.
Route filtering
We apply the following filters to every BGP session, including route servers:
- RPKI ROV: RPKI-invalid routes are rejected.
- IRR: peer prefixes are filtered against the peer's registered as-set.
- Bogons: reserved and unallocated prefixes and private/reserved ASNs in the AS path are rejected.
- Prefix length: IPv4 longer than /24 and IPv6 longer than /48 are rejected.
- Path sanity: paths longer than 64 ASNs, or not starting with the neighbour's ASN, are rejected.
- We do not accept our own prefixes from peers.
BGP communities
Informational communities are attached to routes we receive. Action communities are available to customers.
| Community | Meaning |
|---|---|
| ASN:100 | Learned from customer |
| ASN:200 | Learned from peer (IX or private) |
| ASN:300 | Learned from upstream / transit |
| ASN:666 | Blackhole (customers only, /32 and /128) |
| ASN:70 | Set local-pref 70 (backup) |
| ASN:0:{peer} | Do not announce to {peer} |
Requesting a session
Email peering@stratline.net with:
- Your ASN and as-set
- The exchange(s) and your IPv4/IPv6 addresses there
- Your expected prefix count
- A NOC contact
We aim to reply within two business days. We may decline or end a session that harms network stability or breaks these terms.