Peering policy

Project NIX is aimed at prefix collection at the Nikhef facilities in Amsterdam. We are mainly interested in peerings with parties that are local to the Nikhef facilities. We maintain an open peering policy with the exception that any peering party must have physical presence at the Nikhef facilities. No written agreement is required from our side, we will however honor peering contracts if joining parties require them.

General Peering requirements

Connected parties

• Are required to have a valid public ASN and valid corresponding public prefixes
• Are encouraged to advertise those prefixes usually associated with a private peering sessions
• Must, unless requested, not announce a full table towards NIX
• Shall not announce a default route towards NIX
• All interconnects are physical, requiring a (low bandwidth) port on the joining party. EBGP multi-hup constructions are not supported as they can conflict with the monitoring functions

Local parties

Local parties are defined such as listed on the customer list on the Nikhef Housing website.

Internet exchanges

Internet exchanges are defined as being a L2 peering VLAN with members attached.

NIX will only connect with route servers offered by the internet exchange. No direct peerings will be made through any internet exchange

Carrier peering requirements

Carriers are defined such a listed on the Nikhef Housing website carrier page.

• All carriers can be requested to announce a full table to our route collector.