Hosting a Sponsored RIPE NCC Test Traffic Measurement (TTM) node

Document ID: ripe-430
Date: 29 April 2008

The TTM service relies on the support of paying customers to ensure that there are a large number of nodes on the network. In order for TTM to be useful for a wide range of users, it is sometimes necessary to place nodes in locations where there is no customer to fund an installation. In these instances, and at its discretion, the RIPE NCC will sponsor TTM nodes, either fully or partially. For more information about the RIPE NCC TTM Service, please see:
http://www.ripe.net/ttm

Practicalities

All sponsored hosts are responsible for the provision of:

• Space in a data centre for the TTM equipment
• Sufficient power and cooling
• All of the infrastructure that is required to connect the node to the Internet
• Remote hands support.

The RIPE NCC will provide TTM equipment for fully sponsored hosts. Partially sponsored hosts will need to provide server hardware. The RIPE NCC will provide the necessary Global Positioning System (GPS) antenna equipment to all sponsored hosts. No TTM service fees will be charged to any sponsored host.

Sponsorship Criteria

This document lays out the criteria used to select a site for sponsorship. Although these guidelines cover a range of site/host requirements, fulfilling all these requirements does not automatically entitle the host/site to receive a sponsored node. Similarly, those hosts/sites not meeting all the requirements are not automatically excluded.

Preference will be given to neutral and independent bodies, such as academic or not-for-profit organisations, and to those organisations that work to support and promote the development of the Internet. Commercial organisations are not normally considered as candidates for sponsorship.

Requirements

1. TTM nodes should be located:

• Within a major Autonomous System (AS) or;
• At a point where a large number of ASs peer, such as a major Internet Exchange or;
• At any other point of significant interest, such in proximity to a root DNS server

This is to ensure that the node serves as a good reference point and so any conditions, such as bottlenecks, which might distort the general connectivity overview, can be avoided.