Guidelines

ripe-464: This document has been produced by the RIPE Enhanced Cooperation Task Force to explain how the existing structures of Internet governance evolved and why these structures are uniquely suited to facilitate ongoing development and innovation in the Internet

ripe-400: A survey carried out in March 2006 revealed that around 11-13% of the nameservers listed in delegations from IANA to the RIPE NCC are 'lame', meaning they are not responding correctly. This document provides more information on the subject.

ripe-393: The DNS root nameservers are a critical part of the Internet’s infrastructure, and anycasting is increasingly being used in their deployment.

ripe-379: At RIPE 52 in Istanbul, RIPE established a task force that promotes deployment of ingress filtering at the network edge by raising awareness and provide indirect incentives for deployment.

ripe-359: This document describes our policy for serving secured DNS data and key exchange. It does not cover deployment of DNSSEC by Local Internet Registries (LIRs) or others in our service region.

ripe-353: In this paper, we look at Autonomous System Number (ASN) assignments by the Regional Internet Registries (RIRs) and the number of unique ASNs seen by routers on the Internet.

ripe-352: We measured the effects of deploying DNSSEC on CPU, memory and bandwidth consumption of authoritative name servers. We did this by replaying query traces captured from ns-pri.ripe.net and k.root-servers.net in a controlled lab environment.

ripe-271: This memo proposes a new direction for how the RIPE NCC collects data and published statistics.

ripe-001 laid out the terms of reference for the establishment of RIPE.