Event Wrap: RIPE 69

By on 13 Nov 2014

Category: Events

Tags: , , ,

Blog home

APNIC staff recently attended and participated at RIPE 69, held in London from 3 to 7 November 2014.

RIPE meetings are a five-day events where Internet Service Providers (ISPs), network operators, and other interested parties gather to discuss issues of interest to the Internet community. Attended by over 600 people, the week’s agenda included technical plenary sessions such as an exploration of network capacity with SDN vs L3 MPLS and “Name Collision Controlled Interruption”, Lightning Talks featuring DNSSEC and IPv6, and the RIPE Working Group sessions. The week ended with the RIPE NCC updates to the community and the Closing Plenary.

APNIC Activities:

  • George Michaelson presented “Please Don’t Pick the ECDSA-ies” in the DNS Working Group Session. Here he outlined the work that APNIC Labs is doing on measuring DNSSEC capability to handle a newer crypto algorithm (EC-DSA), which is faster to run, and shorter to use – both of which are useful properties for future scaling of the DNS. This work is beneficial in informing the community of the risks in key rollover and new algorithm deployment. APNIC Labs will continue to do work in this area.
  • Geoff Huston presented an update of “Who’s Watching” about digital stalking and the various ways a user’s behaviour on the Internet can be tracked at the Closing Plenary session on Friday, 7 November.
  • George Kuo provided the APNIC update on Friday, 7 November, outlining the various service updates from the APNIC Secretariat.
  • Guangliang Pan attended the Resource Services Coordination Group meeting, which is a regular meeting of all the RIR Resource Services Managers. The one and half day meeting included discussion on maintenance of registry data and resource management.
  • Guangliang and George Kuo also met with RIPE NCC staff to discuss collaboration on various projects.

Ripe 70 will be held in Amsterdam, Netherlands from 11 to 15 May 2015.

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 *