RIPE Task Forces
RIPE tasks are structured in two ways: time frame and task group. The task groups will be assigned to task forces, which are groups of individuals having a vital interest to achieve the tasks. The task forces designate a coordinator who is responsibile for making sure that progress is made and that results will be achieved within the time frame that the task force has agreed.
The outcome of a task force is a report with recommendations. The recommendations will be discussed by the RIPE community, and implemented when consensus is reached.
The ripe-list mailing list carries general announcements and discussions about RIPE.
| Active RIPE Task Forces | |
|
This new task force will examine recent policy proposals around the issue of managing the abuse contact field in the RIPE Database and provide feedback to the community. |
|
|
Following discussions at RIPE 54 in Tallinn, the DNS Working Group agreed to form a Task Force to discuss issues around finding a global DNSSEC trust anchor. |
|
| Inactive RIPE Task Forces | |
|
A task force was established at RIPE 53 in Amsterdam to advise, review, and provide feedback about a certification system |
|
| Data Protection Task Force |
At RIPE 52 in Istanbul, RIPE established a task force to work with the RIPE NCC data protection team. |
| RIPE Task Force on Enhanced Cooperation |
At RIPE 54 in Tallinn, the RIPE Task Force on Enhanced Cooperation was formed to advise on issues of enhanced cooperation between the RIPE community and relevant stakeholders, particularly governments and regulators. |
| IP Anti-Spoofing Task Force |
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. |
