Open Network Peering Policy for ASN 33083

Introduction
This document outlines the Open Network Peering Policy for Autonomous System Number (ASN) 33083. The purpose of this policy is to establish guidelines and principles for interconnecting with other networks to enable seamless data exchange and enhance network performance.

Peering Requirements
2.1 ASN Eligibility
ASN 33083 welcomes peering requests from other autonomous systems that meet the following eligibility criteria:

a. The requesting ASN must have stable network infrastructure.
b. The requesting ASN must have a valid and globally unique ASN assigned by a recognized Regional Internet Registry (RIR).

2.2 Technical Requirements
ASN 33083 requires the following technical criteria to establish and maintain peering connections:

a. The requesting ASN must adhere to industry-standard routing protocols such as Border Gateway Protocol (BGP).
b. The requesting ASN should operate a network with some traffic passing between each other. 
c. The requesting ASN must have an operational Network Operations Center (NOC) available 24/7 to handle peering-related issues promptly.

Peering Guidelines


3.1 Traffic Exchange

a. The peering relationship should facilitate bi-directional traffic exchange without any artificial restrictions, such as rate limiting or traffic engineering that selectively targets peering traffic.
b. Both parties should strive for an equitable traffic exchange ratio based on the principle of providing balanced connectivity.
c. Each party must maintain accurate and up-to-date routing information and promptly resolve any route leaks or other routing anomalies.

3.2 Route Filtering and Security
a. Both parties must implement robust routing filters to prevent the propagation of incorrect or malicious routes like default route or RFC1918
b. Each party should filter received routes based on legitimate prefix ownership and prevent the advertisement of routes not explicitly authorized by the originating ASN.
c. Both parties should cooperate in addressing and mitigating any security incidents that may affect peering connections.

3.3 Peering Agreement
a. There is no formal agreement required between any peering relationship.

Peering Contact Information
ASN 33083 requires the requesting ASN to designate a primary technical contact responsible for peering-related communications.
The contact information should include:
a. Name and title of the technical contact person
b. Email address
c. Phone number
d. Postal address (optional)

Compliance and Review
This Open Network Peering Policy is subject to periodic review to ensure its effectiveness and alignment with changing industry standards and requirements. ASN 33083 reserves the right to modify or update this policy as deemed necessary. Failure to comply with this policy may result in termination of the peering relationship.

Please note that this peering policy is subject to negotiation and may vary depending on the specific circumstances and requirements of both parties involved in the peering agreement.

For peering inquiries or further information, please contact the peering coordinator at noc-james (at) axcelx.com

Effective Date: 1/1/2020
Last Updated: 1/1/2023