Best Common Practices

ripe-431: This document presents practical recommendations for the implementation of anti-spoofing mechanisms at the critical points of the network infrastructure of carriers and/or ISPs.

ripe-409: This document outlines best practices for minimising email abuse.

ripe-399: Aggregation is a necessary activity for network operators participating in today's Internet. What was taken for granted following the migration to the classless Internet in the early 90s no longer seems to be a standard activity for most network operators.

ripe-378: This document discusses Route-flap Damping and recommends acceptable practices for ISPs who are considering deploying Route-flap Damping.

ripe-351: This document describes an improvement to the notification process for new blocks of address space being distributed by the Regional Internet Registries (RIRs).

ripe-206: The provisions of this BCP document are to be applied to all customers. However, some customers will have customers of their own. The ISP will conform to Best Practice by ensuring that such customers adopt this BCP themselves, and thereby apply Best Practice procedures in turn to their own customers.

ripe-203: This document gives recommendations on which values to use for the SOA resource record of small, stable DNS zones to aid novice administrators and to contribute to DNS stability and efficiency.

ripe-192: Simple DNS Configuration Example

ripe-114: This document tries to show how important it is to have DNS properly managed, including what is already in place to help administrators taking better care of their domains.

ripe-063: The purpose of this recommendation is to give guidance to the RIPE member organisations on how to exchange contact information and network status information in a way which is easy to implement and which provides enough redundancy to function when network connectivity is not guaranteed.