AS9002 peering policy
RETN owns and operates an IP network identified as Autonomous System 9002 with AS-RETN as-set (IPv4) and AS-RETN6 (IPv6).
Our IP network is directly interconnected with multiple ISPs, NSPs and CSPs. New private peering connections are established when they are beneficial for RETN and its customers. RETN sticks to a selective peering policy and consider each peering request individually. Thus we reserve the right to reject a peering request or terminate existing peering relationships if their advantages are not evident to us.
Below you can find some policy statements describing main principles, though not all of them, that determine RETN’s decision regarding the benefits and appropriateness of establishing relationships with eventual peering partners.
Existing peering relations may be terminated when:
– Current bandwidth is not enough for traffic volumes and causes packet loss, and Peering Partner refuses to cooperate or is not able to increase the bandwidth and provide sufficient capacity;
– Peering Partner violates at least one of the basic requirements listed below.
Those who request private peering with RETN should:
• maintain “full BGP view” at the edge router by means of BGPv4;
• announce only its own routes and the routes of its customers to AS9002, but not the routes received from other peers or upstreams;
• not announce “martian” routes or the default route (0.0.0.0/0) to AS9002;
• manage a fully staffed 24×7 Network Operational Centre;
• provide its escalation matrix upon request in order to be able to quickly resolve possible network issues;
• be able to react quickly to establish additional capacity to meet traffic growth;
• secure at least 10Gbps bandwidth at each interconnection point.
Main IPv4 / IPv6 exchange points
Internet Exchange Point
|Espanix, Madrid||184.108.40.206/25 220.127.116.11/25||2001:7f8:f::68/64|
|DE-CIX, New York||18.104.22.168||2001:504:36::232a:0:1|
|NYIIX, New York||22.214.171.124||2001:504:1::a500:9002:1|
If you wish to peer with AS9002, send us your request to firstname.lastname@example.org or via online Peering Contact Form.
Please, provide your network description and technical details including:
– as-set (as macro), if available
– type of traffic carried through your network
Depending on the traffic levels expected, peering interconnections can be set up as Private Network Interconnections (PNIs) or over public Internet Exchange Points (IXPs).
In case you do not meet the requirements of RETN’s peering policy, but take a strong interest in RETN’s IP transit service, please drop us an email at email@example.com.