Best Common Practices
This page regroups all documents proposing mutually accepted norms on the best way to carry out specific operations. This process is often led by the community at the initiative of Task Forces.
-
DNS Resolver Recommendations
ripe-823: DNS Resolver Recommendations
RipeDocument -
Requirements For IPv6 in ICT Equipment
ripe-772: Requirements For IPv6 in ICT Equipment
RipeDocument • ipv6 bcop -
Architectural Considerations for IoT Device Security in the Home
ripe-759: Architectural Considerations for IoT Device Security in the Home
RipeDocument • iot -
Mutually Agreed Norms for Routing Security (MANRS) Implementation Guide
ripe-706: Mutually Agreed Norms for Routing Security (MANRS) Implementation Guide
RipeDocument • bcop -
Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose
ripe-690: Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose
RipeDocument • ipv6 bcop -
IPv6 Troubleshooting for Residential ISP Helpdesks
RIPE-631: IPv6 Troubleshooting for Residential ISP Helpdesks
RipeDocument • ipv6 bcop -
RIPE Routing Working Group Recommendations on Route Flap Damping
ripe-580: RIPE Routing Working Group Recommendations on Route Flap Damping
RipeDocument -
Requirements for IPv6 in ICT Equipment
ripe-554: Requirements for IPv6 in ICT Equipment
RipeDocument • ipv6 bcop -
Requirements For IPv6 in ICT Equipment
ripe-501: Formulating requirements for IPv6 support can be done in several ways. In this document we look at three different options.
RipeDocument • ipv6 -
Network Hygiene Pays Off - The Business Case for IP Source Address Verification
ripe-432: IP source address verification completely prevents a class of prevalent reflector-type DDoS attacks, helps to track down attacking hosts and simplifies some network management tasks.
RipeDocument