Peering Policy
This page sets out the peering policy of DODO K.K. (AS45691). Effective August 23, 2025.
Policy
- Open peering policy.
- We welcome settlement-free interconnection with any network that meets the technical requirements below and is present at a mutual Internet Exchange in Tokyo.
- No contract is required.
Requirements
- A globally routable, unique Autonomous System Number (ASN)
- A complete and current PeeringDB record
- Routes registered in an Internet Routing Registry (IRR) under an AS-SET
- 24/7 NOC contact reachable by e-mail
- Compliance with each Internet Exchange's technical requirements
- Only send traffic to destinations we advertise (no static or default routes towards us)
BGP sessions
- Address families: IPv4 and IPv6. Please establish both where possible.
- MD5 authentication: supported (optional)
- Max-prefix limits: enforced, taken from PeeringDB
- Route servers: we peer with the route servers at every IX we attend
- Use multiple sessions for redundancy where possible.
Optional features (on request)
- RFC 2385 BGP MD5 authentication
- RFC 7999 BLACKHOLE community
- RFC 8326 Graceful BGP Session Shutdown
Traffic
- No minimum traffic volume
- No traffic ratio requirement
Private peering (PNI)
- Available above 10 Gbps of sustained traffic at Equinix TY8.
- Interfaces: 10G-LR or 100G-LR4
- BGP over both IPv4 and IPv6 recommended
- We can provide IPv4 /30 and IPv6 /64 point-to-point addressing
Advertised prefix counts and AS-SET
- IPv4: 1000
- IPv6: 100
- AS-SET: JPIRR::AS-DODO-CORE
Other conditions
- We may decline requests for operational reasons.
Contact
- NOC / Peering: noc[a]biz.dodo.ad.jp / peering[a]biz.dodo.ad.jp