(3) In the case, one RINEX member is already providing transit to another RINEX
member, the exchange of regional routes mentioned in (ii) above, may also
happen using a separate private connection between the ISPs.
(4) ISPs shall announce only those routes that belong to their AS, i.e their own
network, and their customer routes at the RINEX. An ISP in any region can
aggregate traffic from other ISPs in the region and connect to the RINEX through
a single connection.
(5) The RINEX router shall only exchange information but not carry any transit
traffic.
(6) All RINEX members must ensure that they suitably and proactively upgrade
capacity from time-to-time so that they do not end up dropping traffic that other
peers are exchanging with them.
(7) The routing policy here also applies to "large" content providers to directly peer
at any of the RINEX nodes. They will be treated like stand-alone Data Centers.
For this they need to adhere to the following criteria:
a. They must have their own AS number
b. The content hosted by them should be in accordance with Rwandan laws
(i.e they should not be hosting obscene content or promoting gambling or
anti-national content, or any other content that violates either the ISP
license condition or any other Rwandan Law)
2.4 Quality of Services
(1)

All critical components of RINEX should be up for 99.00 % of time in a
quarter. These critical components are RINEX routers/Switches, interface
module on which the links of the ISPs are terminated and any other
equipment which affects the RINEX traffic. Non critical faults which do not
affect RINEX traffic like failure of one power supply module should be rectified
by RINEX within 48 hours.

(2)

Switching Architecture of RINEX shall be non-blocking, so that it does not
introduce any delay.

(3)

Uninterrupted power shall be ensured to the equipment of the ISP and RINEX
router itself in the RINEX node. Power availability can be 99.00% in a quarter.

(4)

RINEX shall ensure proper environment (Proper Air conditioning with
Humidity control) for housing equipments of RINEX and its member ISPs

(5)

Augmentation of ISPs Bandwidth to RINEX: - ISP shall augment its bandwidth
to RINEX, if the utilization of the existing link exceeds 80% of the capacity for
4 hrs in a day and for 7 days. Such capacity management shall be through
increase of capacity and not through reduction routes announced. The
augmentation should normally be completed within a period of one month
after RINEX reported to the concerned ISP. This time should be extendable

RINEX GUIDELINES 2009

Page 6

Select target paragraph3