29 lines
No EOL
1.3 KiB
Markdown
29 lines
No EOL
1.3 KiB
Markdown
# BKNIX Peering policy
|
|
|
|
## Our policy is open and simple
|
|
|
|
- Openly for bilateral peering agreement (BLPA). There is no Multilateral peering agreement (MLPA)
|
|
- Participants may not destined of default routes unless you have permission to access participant's resources
|
|
- BGP-4 is acceptably used for peering, may not use any IGP such as RIP, OSPF, IS-IS etc.
|
|
|
|
## Ports Available
|
|
|
|
- 100 Mbit/s ”FE” (100BaseT)
|
|
- 1 Gbit/s “GE” (1000BaseT, 1000BaseSX, 1000BaseLX, 1000BaseLH)
|
|
- 10 Gbit/s “10GE” (10000BaseLR, 10000BaseER)
|
|
- 100Gbit/s "100GE" (100GE-SR10, 100GE-10x10)
|
|
- Link aggregation of the above
|
|
|
|
## Switch Interconnection Policy
|
|
|
|
- Allow single layer-2 MAC address to place a single layer-3 router per port
|
|
- BKNIX delivers a service from the IX Switch port to the patch panel.
|
|
- The customer is responsible for their cable between router and BKNIX switch panel and peering that correct functioning for your own network
|
|
- The customer is responsible to provide the router
|
|
|
|
## Features
|
|
|
|
- IPv4 and/or IPv6 (native)
|
|
- Route Servers, we have both Bird (IP Routing Daemons on UNIX systems) and Cisco Router that support both 2-byte & 4-byte AS number.
|
|
- Private account to Manage your connections, initiate peering agreement, Traffic monitoring etc.
|
|
- Network Operations Centre (NOC) actively monitors the BKNIX infrastructure 24x7. |