Peering & Route-Server Policy

Cambodian Network Exchange (CNX) provides route servers (RS) as the default and most effective way for members to exchange prefixes. This page outlines how we operate the route servers and how members can best benefit from them.

CNX Approach

• RS-first model – All members are encouraged to peer with the CNX route servers for baseline reachability.
• Bilateral optional – Direct peering sessions between members are always possible, but are generally established when there is a clear operational or traffic need.
• Security by default – RS sessions are filtered using IRR and RPKI validation. Bogon and martian prefixes are rejected, and max-prefix limits are enforced.

Member Responsibilities

• Maintain accurate entries in PeeringDB.
• Keep AS-SET / route-set information updated.
• Ensure ROAs are published for announced prefixes.
• Provide a sensible max-prefix value.

These steps help all members benefit from a clean and stable routing environment.

Bilateral Requests

CNX occasionally receives requests from networks that prefer bilateral sessions. Our process is:

1. The requesting network provides details: expected traffic volume, prefix list / AS-SET, and technical contact information.
2. CNX may assist with introductions to relevant members if there is a clear mutual benefit.
3. Members are free to accept or decline bilateral requests based on their own policies.

When to Consider Bilateral

• There is a significant volume of traffic with a specific network.
• Traffic engineering or special BGP community support is required.
• A network’s policy does not allow announcements via RS.