Event Wrap: RIPE 79

By on 28 Oct 2019

Category: Events

Tags: , ,

Blog home

APNIC participated at RIPE 79 from 14 to 18 October 2019 in Rotterdam, Netherlands.

Welcoming around 700 participants, including 180 first-time attendees, the five-day RIPE 79 meeting included workshops, plenary and working group (WG) sessions on topics relating to IPv6, routing, and the DNS.

RPKI was a key discussion topic with RIPE NCC staff assisting attendees with signing their ROAs, testing if their networks were dropping invalids, and presenting on the RIPE RPKI Support services.

RIPE 79 marked the 20th anniversary of Axel Pawlik’s appointment as the Managing Director of the RIPE NCC. Upon acknowledging this during the RIPE NCC Services session, Axel announced he would be stepping down from his position at the end of 2019. APNIC wishes him well in his future endeavours.

APNIC activities:

  • Richard Brown provided the APNIC Update during the NRO/RIR reports session.
  • Sofia Silva Berenguer presented during the Plenary session — APNIC – Solving Problems For Our Community — in which she provided an overview and sought feedback on three products under development by APNIC: DASH, NetOx and the Internet Directory.

Read: Help us develop products you need

  • Craig Ng and Robbie Mitchell assisted as independent vote counters during the RIPE NCC General Meeting.
  • Sofia met with the RIPE Stats team to continue inter-RIR collaboration that is working towards developing APNIC NetOx.
  • Following RIPE 79, Robbie attended the AMC IMC 2019 Conference in Amsterdam to meet with meet with guest authors of the APNIC Blog and arrange future articles.
Rate this article

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please answer the math question * Time limit is exhausted. Please click the refresh button next to the equation below to reload the CAPTCHA (Note: your comment will not be deleted).

Top