BGP Peering Policy Active

1. Overview

Our selective peering policy aims to enhance network performance, security, and resilience through controlled connectivity.

2. Requirements

2.1 Technical

• ASN: Public and unique
• IP: Publicly routable IPv4/IPv6
• BGP: BGPv4 with IPv6 support
• Filtering: Prefix filtering required
• Communities: BGP Communities support
• Optional: BFD, multi-session BGP for IPv4/IPv6

2.2 Routing

• No Leaks: Only agreed prefixes exchanged
• Aggregation: Prefix aggregation where possible
• AS Path Filtering: Required
• Traffic Balance: Max 2:1 ratio

2.3 Security

• RPKI Validation: Required
• MANRS: Compliance mandatory
• Anti-Spoofing: Must be implemented

3. Locations

• LONAP Coming Soon

4. Traffic Requirements

• Min Volume: 100Mbps traffic between networks
• Capacity: Plan for 100% spare capacity during peak traffic

5. Process

5.1 Request

Email your ASN, traffic stats, and contact info to: oliver.reid@r3ido101.network

5.2 Approval & Configuration

Requests evaluated based on traffic and alignment. After approval, BGP session parameters will be configured.

6. Termination

Peering may be terminated for violations, route leaks, prolonged traffic imbalance, or if there is a lack of traffic or no traffic exchanged between networks.

7. Contact

For inquiries, contact our NOC: oliver.reid@r3ido101.network