Introduction

This document outlines the peering policy of Kloud Technologies Limited for participation at KTL-IX. The purpose of this policy is to define the guidelines and requirements under which peering arrangements are established and maintained for NIX policy

Peering Requirements

We welcome peering with networks that meet the following conditions:

• Have a valid, public ASN (Autonomous System Number) & IP Block.
• Organization must have recognized legal entity
• Operate a 24/7 NOC (Network Operations Center) with responsive personnel
• Maintain consistent and reliable routing and BGP session stability
• Announce only their own or properly originated customer prefixes (no transit)
• Do not engage in route leaks, hijacks, or default routing over peering sessions
• Routing Device should be capable of running (Border Gateway Protocol Version 4 or above) for NIX-peering.

General Requirements

• Kloud-NIX (KTL-IX) is the neutral meeting point of the ISPs, MNOs, contents providers and government agencies in Bangladesh.
• KTL-IX is not an ISP and will not provide any Internet connections or Transit services to its members.
• Peering members need to provide a 24×7 contact to act upon urgent incidents/outages.
• Each member shall sign a membership form agreeing all terms & policies as per instructions by regulatory authority.
• Connectivity to the KTL-IX will through dedicated leased lines (Fiber Optics Connection preferred) of sufficient capacity. Payments made to carriers for the leased link will be directly between them and the members and KTLIX will not be a party to it.
• Members shall provide their own necessary equipment’s (routers, convertors, modular, connector, cabling etc.) to their networks up to KTL-IX devices.
• Peering members will not be allowed to have KTL-IX facilities as a default route. Further, no member should use KTL-IX to carry traffic between its own two or more routers.
• Members will ensure that their use of NIX (KTL-IX) facilities is not detrimental to other members in any way and that all usage is compliant with the applicable internet standards of IETF.
• KTL-IX reserves the right to temporarily disconnect any member for security reasons or preserving the stability of KTL-IX infrastructure.
• KTL-IX reserves the right to amend the guidelines stated above with approval of the Board.

Peering Type

We support the following peering arrangements:

• Bilateral Peering: Negotiated on a case-by-case basis
• Multilateral Peering: Where applicable, we may join a route server at KTL-IX

Technical Requirements

• Peering must be established over IPv4 and/or IPv6 as agreed
• BGP sessions must use MD5 authentication if requested
• Maximum prefix limits and filtering policies must be respected
• Use of BFD (Bidirectional Forwarding Detection) is encouraged, if supported

Routing Policy

• We will advertise prefixes originating from our ASN only
• We will not advertise default routes or third-party prefixes
• We will enforce strict inbound and outbound route filtering
• Prefixes must be registered in an IRR (Internet Routing Registry)

Traffic Engineering

• We may apply traffic engineering techniques (e.g., MEDs, AS_PATH prepending)
• Peers may request selective advertisements within reason

Contact & Requests

• Peering requests should be sent to: [[email protected]/[email protected]]
• Our Peering-DB entry: [https://www.peeringdb.com/ix/3467 | ASN-134508 | KTL-IX]
• Our apix-membership entry: [https://apix.asia/members/]

Policy Revisions

• KTL-IX reserves the right to update this peering policy at any time without prior notice.