| Effective date of the policy: |
January 2008
|
|
Last updated:
|
January 2008
|
|
Policy owner:
|
Information and Communication Technology Services
|
Table of contents
Purpose
This policy document prescribes the requirements for third party (the peering partner) to establish and operate a network peering link with UCT.
Policy details
| 1. |
Peering requirements
|
|
|
1.1
|
The peering partner shall make use of the BGP-4 routing protocol to exchange routing information with UCT. If the peer does not have an AS number, UCT will allocate one to the peering partner from the private-use AS number range.
|
|
|
1.2
|
All routes advertised by the peering partner should be aggregated to the maximum extent possible.
|
| |
1.3 |
In the absence of a detailed transit agreement negotiated between UCT and the peering partner, the following standard routing requirements will apply: The peering partner: |
| |
|
1.3.1 shall only advertise routes to networks that are local and directly connected to the peering partner, |
| |
|
1.3.2 shall not propagate or advertise routes learned from UCT to any other peering partner, |
| |
|
1.3.3 shall not route traffic toward UCT destined for routes other than those advertised by UCT to the peering partner. |
|
|
1.4
|
Routes advertised by the peering partner shall be globally routable IP address space, not RFC1918 (private-use) address space. Prospective peering partners can obtain Provider Allocated IP space from their ISP or Provider Independent IP space from their RIR.
|
|
2.
|
Responsibilities, ownership and access
|
|
|
2.1
|
The responsibility for the configuration and maintenance of equipment used for the peering link shall be determined by the ownership of the equipment and a demarcation point between the peering partner and UCT's networks shall be agreed upon by both parties.
|
| |
2.2 |
If any of the equipment belonging to the peering partner is hosted at UCT, physical access to such equipment may only be granted by prior arrangement. |
| 3. |
Disclaimer
In the absence of an SLA, any network peering offered by UCT is provided on a best-effort basis with no warranties.
|
| 1. |
Peering requirements
|
|
|
1.1
|
The peering partner shall make use of the BGP-4 routing protocol to exchange routing information with UCT. If the peer does not have an AS number, UCT will allocate one to the peering partner from the private-use AS number range.
|
|
|
1.2
|
All routes advertised by the peering partner should be aggregated to the maximum extent possible.
|
| |
1.3 |
In the absence of a detailed transit agreement negotiated between UCT and the peering partner, the following standard routing requirements will apply: The peering partner: |
| |
|
1.3.1 shall only advertise routes to networks that are local and directly connected to the peering partner, |
| |
|
1.3.2 shall not propagate or advertise routes learned from UCT to any other peering partner, |
| |
|
1.3.3 shall not route traffic toward UCT destined for routes other than those advertised by UCT to the peering partner. |
|
|
1.4
|
Routes advertised by the peering partner shall be globally routable IP address space, not RFC1918 (private-use) address space. Prospective peering partners can obtain Provider Allocated IP space from their ISP or Provider Independent IP space from their RIR.
|
|
2.
|
Responsibilities, ownership and access
|
|
|
2.1
|
The responsibility for the configuration and maintenance of equipment used for the peering link shall be determined by the ownership of the equipment and a demarcation point between the peering partner and UCT's networks shall be agreed upon by both parties.
|
| |
2.2 |
If any of the equipment belonging to the peering partner is hosted at UCT, physical access to such equipment may only be granted by prior arrangement. |
| 3. |
Disclaimer
In the absence of an SLA, any network peering offered by UCT is provided on a best-effort basis with no warranties.
|
