Public policy
Peering
The policy is open. No contract, no ratio requirement, no invoice. The session runs over a physical link, in a facility where we already are.
Open
policy
None
contract required
IPv4 + IPv6
on the same session
4
facilities in Paris
The policy
- General policy
- Open
- Contract
- Not required
- Traffic ratio
- Not enforced
- Locations
- No requirement beyond physical presence
- AS-SET
- AS215599:AS-ZKILLUSAS
- IPv6
- Yes, over the same physical link
- Internet exchanges
- None to date, direct sessions only
- Digital Realty Paris PAR1
- Digital Realty Paris PAR2
- Digital Realty Paris PAR3
- Digital Realty Paris PAR5
The requirements
- Presence in one of the four listed facilities, or the ability to run a cross-connect there.
- An up-to-date AS-SET, or route and route6 objects published in a recognised IRR.
- Valid ROAs for the prefixes you announce.
- IPv4 and IPv6 sessions brought up together.
- A reachable NOC contact, and an abuse address that answers.
What we do not do
- Peering over tunnels (GRE, VXLAN, L2TP, WireGuard) between two distant networks.
- Remote peering resold by a third party.
- Sessions with no IRR object or ROA on the other side.
Requesting a session
One email is enough. Here is what lets us bring the session up quickly.
- 01 Your ASN and your AS-SET.
- 02 Expected IPv4 and IPv6 prefix counts, so we can set max-prefix.
- 03 Facility, rack and cross-connect reference.
- 04 NOC contact and abuse address.
- 05 Whether you want MD5 authentication.