Day 3 of RIPE 72 kicked off with RIPE Working Group sessions and 627 attendees checked in so far.

The highlights of the first Address Policy Working Group session included:

  • Co-Chair Sander Steffann’s term renewed as there were no other candidates standing.
  • A discussion on Erik Bais’ “RIPE Resource Transfer Policies” which aimed to combine all of the various transfer-related policy text into one single policy document.
  • A discussion on two policy proposals about what to do with the remaining IPv4 pool — each proposal taking opposing approaches, which prompted a lengthy discussion among attendees at the microphones.

In the second Address Policy Working Group session, the highlights included:

  • A presentation on the research into IPv4 transfer market concentration, including noted differences in the transfer data published by the various RIRs.

The Connect Working Group highlights included:

  • Interesting presentations by DE-CIX on route servers at IXPs, followed by lively discussion around RPKI invalids and trust anchors.
  • Updates from Peering DB 2.0, EURO-IX, and data centre optics trends.
  • Lightning talks on the RIPE Atlas Hackathon project about IXPs and the nature of statistics at route servers.
A view of the main room from behind the tech desk

A view of the main room from behind the tech desk

The MAT Working Group highlights included:

  • A well-received singing and juggling act by Vesna Manojlovic during her update on RIPE Atlas.
  • A question about whether an actual RIPE Atlas Working Group should be formed, which was generally decided was not needed but which led to an interesting discussion about the purpose of the MAT Working Group and RIPE Atlas.
  • A presentation by the RIPE Atlas Hackathon winners Shane Kerr and Desiree Miloshevic on their winning project, RIPE Atlas Halo, which allows users to search for information about network outages by date or within a given network (and is available on GitHub).

The IPv6 Working Group’s highlights included:

  • Geoff Huston’s talk about large packets in IPv6 and why one should set the “Don’t Fragment bit” to always ON. You can also read this on RIPE Labs.
  • John Brzozowski presented a new way for community Wi-Fi and IPv6 by giving a /64 to each device; people thought this was a great idea.
  • Jen Linkova presented on how using tricks in the DNS can help validating clients behind NAT64. This created quite some discussion: many people thought this was a bad idea, but it might help to promote IPv6 in the end.
  • Enno Rey talked about RFC 7404 and how this can help enterprises to adopt IPv6. In the following discussion, people commented that the proposed solution is not applicable to all network architectures, but might be a good solution for specific cases.

In the RIPE NCC Services Working Group, highlights included:

  • A preview of the RIPE NCC Survey 2016 which opens during the Closing Plenary. The survey will be shorter and focused on improvements. Oh, and there are five iPads up for grabs for those that participate in the survey.
  • An in-depth look at the RIPE NCC’s outreach efforts, including regional challenges in Europe, Russia and Central Asia and the impact that IoT will have for the RIPE NCC and the RIPE community.
  • Alexander Isavnin shared his views on RIPE NCC’s outreach in the Russian and CIS region with criticism that it wasn’t enough. There was a healthy debate with commenters at the microphones that the RIPE NCC has made great efforts to cover that region in particular. Kurtis asked that the conversation be brought to the mailing list because of time constraints.
  • An update from RIPE NCC Managing Director Axel Pawlik on RIPE NCC activities.
  • A request from IETF management for increased funding from the RIPE community and a plea from Nigel Titley, Chairman of the RIPE NCC Executive Board, for guidance from RIPE NCC members on how the RIPE NCC should proceed here.
  • An explanation from Erik Bais on his policy proposal 2016-02 Resource Authentication Key (RAK) Code for Third Party Authentication.