Draft and Discussion Documents

In its final report, the 2020 RIPE Nominating Committee recommended to document a consensus on the relationship between RIPE and the RIPE NCC and, in particular, how RIPE NCC staff can participate in RIPE.

In its final report, the 2020 RIPE Nominating Committee recommended to document a consensus on the relationship between RIPE and the RIPE NCC and, in particular, how RIPE NCC staff can participate in RIPE.

This document serves to describe existing processes and lay out additional processes related to the election of representatives from the RIPE community to the Number Resource Organization (NRO) Numbering Council (NC).

This document describes the process for handling reports that someone has breached the RIPE Code of Conduct.

This document describes the process for handling reports that someone has breached the RIPE Code of Conduct.

Scope This document describes the selection of the RIPE Chair and the RIPE Vice Chair. This is an invoking RIPE Document for the purpose of ripe-728. The role of RIPE Chair is described in ripe-714. Background The first Chair of RIPE, Rob Blokzijl, was selected informally. Until the time of writing

IETF Copyright This document is a derivative work of RFC7437. It is created and published under a copyright license agreement between the RIPE NCC and the IETF Trust and any further use of it is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date

This document describes how people are appointed to the Code of Conduct (CoC) Team, along with the team’s composition and responsibilities.

This document describes the process for handling reports that someone has breached the RIPE Code of Conduct.

This document outlines the definition, appointment, composition and responsibilities of RIPE task forces.