Peering Policy

RAPDODGENET is a small, private network for learning materials and a hobby network. RAPDODGENET has an open peering policy and will peer with networks that have presence on mutual exchange points or tunnel-based.

Requirements

RAPDODGENET uses PeeringDB as a single authoritative source of truth. This means peering partners must have an up-to-date PeeringDB entry before a bilateral peering session can be established.

RAPDODGENET will use industry standards to secure the peering sessions. This includes industry standards and best practices. Both parties should have a well-set-up route-set, or AS-SET, as well as up-to-date prefix maximums defined in PeeringDB. RAPDODGENET will use this data to filter routes received from the network’s BGP sessions.

Important Notices

To ensure the quality of our operations, we reserve the following rights under our peering policy:

To reject your prefix automatically when RPKI and IRR are invalid.
To reject your network when you de-aggregate too many prefixes if your network is not an essential service for us.
To accept or decline a peering request at any time for any reason.
To selectively withdraw prefixes from public IXP fabrics as needed to protect service quality.
To terminate any peering connection at any time without notice.

— RAPDODGENET Network Administrator