Event Wrap: IETF 99, Prague

By on 1 Aug 2017

Category: Events

Tags: ,

Blog home

The Internet Engineering Task Force (IETF) held their 99th meeting in Prague, Czech Republic, from 17 to 21 July 2017.

The IETF is an international community of network designers, operators, engineers, vendors, and researchers concerned with the evolution of the architecture and of the smooth operation of the Internet. This was the second of three conferences it holds each year.

APNIC staff were among the 1,200 people from 61 countries who attended and participated during the week-long conference.


Read Geoff Huston’s report of IETF 99 Working Groups and sessions he attended during the week and more specifically DNS-related discussions.

APNIC activities:

  • Tom, Anton Strydom, and Rafael Cintra shared APNIC’s experience with Kubernetes with colleagues from RIPE NCC who were attending the meeting.
  • Geoff, George, Tom, Anton, Rafael, and Sofía Silva Berenguer participated in a number of sessions, including the:
    • Homenet Working Group, which discussed the current complex state of naming models in Home Networking.
    • IPv6 Operations Working Group, during which Microsoft’s Principal Network Engineer, Marcus Keane, presented on their work switching to IPv6-only in an effort to overcome the ongoing complexities sustaining dual stack, as well as the merit of Unique Local Addresses.
    • 6MAN Working Group, where the hot topic was the /64 boundary and whether it requires proscriptive and hard limits.
    • DNS Operations Working Group, which discussed several new drafts including better signalling from servers about problems and client identities.
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