IETF Administrative Director <> Fri, 25 May 2018 16:38 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 3739212704A for <>; Fri, 25 May 2018 09:38:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <>
To: IETF Announcement List <>
Subject: IETF and GDPR
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Fri, 25 May 2018 09:38:49 -0700
Archived-At: <>
X-Mailman-Version: 2.1.22
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 25 May 2018 16:38:49 -0000


This note provides a brief summary of work undertaken to ensure systems and policies the IETF community relies upon to conform to the requirements of the European Union's General Data Protection Regulation (GDPR), which is scheduled to begin taking effect on 25 May 2018. The work has been overseen by the IAOC and guided by input from legal counsel. We expect no significant changes in how most of the day-to-day work of the IETF community is conducted. 

The items reviewed for GDPR compliance have been the IETF Datatracker, the IETF meeting registration system, IETF meeting records, IETF email lists and archives, ARO for Area Directors, IANA Domains, and IETF vendor contracts. Necessary updates--largely in how data is handled rather than user interfaces--have been made to each of these. Additional work may be undertaken to ensure due consideration for personal data protection issues, even if it is not needed for immediate GDPR compliance.

The IAOC have updated policies and processes related to data protection. For example, the recently published privacy statement has been modified slightly on advise of counsel; it's available at Similarly, an Information Security Incident Response Plan is being reviewed and will be presented to the IAOC for adoption.  The plan must also be in compliance with ISOC and not conflict with their established policies.

This work provides additional assurance that data shared in the course of IETF work will be handled appropriately. Please feel free to share any comments or questions to 


Portia Wenze-Danley
IETF Administrative Director (IAD)	
Internet Engineering Task Force (IETF)