IETF Logo Mail Archive

Re: [Add] meeting hum: should the IETF take up this work?

Andrew Campling <andrew.campling@419.consulting> Thu, 25 July 2019 16:02 UTC

Return-Path: <andrew.campling@419.consulting>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEC8412035C for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 09:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft5189650.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FE5zFxzx0bjJ for <add@ietfa.amsl.com>; Thu, 25 Jul 2019 09:01:59 -0700 (PDT)
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (mail-eopbgr110041.outbound.protection.outlook.com [40.107.11.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCEF312036E for <add@ietf.org>; Thu, 25 Jul 2019 09:01:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eZBtn/vdXIuKD3MXj1WpLpSZOl0/8HIimY1pudFU/INdQWPnk3IWtUwdDbvRli6TjifYyHjdMB3mXiTlx9HbzzIelogilITiS//Fe41QaK9nOIwQyckUbwdEJjyqS1Di3PIfbATGoqR12g+z5bc1lb3+7Ln8rmzXnBT3Epr9HK0q1qHwICYBHS3qJtWWnur+3HFF3s5zv9LowQPjHmebT3jloanyzZ560rXKzoN3Jj0LkWCyAEz/SyS8/ZE31dnIU9M9ha+9TQ0yMPk36malteqzXz+y8OTDbCYzfJrx/pKADOI+qjnzYZoCkYQ8hac9ukycXCqThQ7Ff3f+8JJ88w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uarRvsAMqdOH9XC57GCVG8++80nTAd5q1EJVIw6mowM=; b=eYgIsWAc+FVdfAirYTrLprbW/0GrF2YrKevE631uRcZoi+dzFuzSI9H7t7mCLh+3chu/hNkYk4xrQvbzFRXl3oxT3trZdWpVmbPZ7VfcT/KuQUooS3xPFPHVlSJTKKVtxz4T+tnKE2EXkITj9BPZ8HTbkQnf9nr8soRfILGjKuhKeSu7f8HK2habFcd5CsCyQhFqgCmmyZAAGHRSciINywXNfvfrHeXN49l547BMlKUSsHS5Kg3L0YbpK50ofYgLYd2UKS6LvqBztpESvHmkdjKWT1wQYluQ23BncdZvrF9nHKr6aFEHltOLm7KxQ87QRtYXz2d6ddSVTPdDI5ON9Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=419.consulting;dmarc=pass action=none header.from=419.consulting;dkim=pass header.d=419.consulting;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT5189650.onmicrosoft.com; s=selector1-NETORGFT5189650-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uarRvsAMqdOH9XC57GCVG8++80nTAd5q1EJVIw6mowM=; b=r1k1KLBrvbFF9f4NFWRblnznNF9qMrgrCXwNyVFKilsfNPXnSG+IJZEClfq2Rvr/2lUXn+gSzc4UkEY287RBsMq44vqdC4/uEwCMx+3mokRH8gs9QSGHf6jRWQcGVdhGouCY4je/m4lOV4iqxhALrl3dn/MdTOUaep/oDs+e2jk=
Received: from LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM (20.176.138.146) by LO2P265MB1517.GBRP265.PROD.OUTLOOK.COM (20.176.145.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Thu, 25 Jul 2019 16:01:55 +0000
Received: from LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM ([fe80::387c:9c12:531b:b7bd]) by LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM ([fe80::387c:9c12:531b:b7bd%3]) with mapi id 15.20.2094.013; Thu, 25 Jul 2019 16:01:55 +0000
From: Andrew Campling <andrew.campling@419.consulting>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] meeting hum: should the IETF take up this work?
Thread-Index: AQHVQvQ3hyEXUjk430e+e4o5zbaPCqbbaiGggAALOoCAAAQbAA==
Date: Thu, 25 Jul 2019 16:01:55 +0000
Message-ID: <LO2P265MB1327E54F6CE3C39EAF0C3BD1C2C10@LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM>
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <AAEA003A-58DB-4FEE-81B2-BBFE9BBB2A37@rfc1035.com> <CAChr6SwA+HM4u5-xpUxQXPH8G8k7sfm6AETJJ019HE=bsq+OXA@mail.gmail.com> <8F094057-DFBC-4732-9DA4-BE46E7914C8A@rfc1035.com> <20190724165951.GB29051@laperouse.bortzmeyer.org> <821B448B-F7EA-46A5-837D-DA0E8C60643A@open-xchange.com> <d653d422-4a71-9fab-fd2e-b8ddaa476f91@nostrum.com> <LO2P265MB13270867DB8A0F2614B46263C2C10@LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM> <c4c35603-310f-2f0b-379e-b86d0f7011b4@cs.tcd.ie>
In-Reply-To: <c4c35603-310f-2f0b-379e-b86d0f7011b4@cs.tcd.ie>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=andrew.campling@419.consulting;
x-originating-ip: [2a00:23c4:a499:2e00:4c4d:3a84:6d17:cecf]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 12fbc1b2-93e0-46b4-13eb-08d711196a84
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:LO2P265MB1517;
x-ms-traffictypediagnostic: LO2P265MB1517:
x-microsoft-antispam-prvs: <LO2P265MB15175BF1DB57CF8FD46B8914C2C10@LO2P265MB1517.GBRP265.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(346002)(366004)(39830400003)(136003)(376002)(34096005)(189003)(199004)(6506007)(6116002)(4326008)(186003)(6246003)(33656002)(30864003)(68736007)(66446008)(8936002)(316002)(71200400001)(486006)(64756008)(6306002)(5660300002)(71190400001)(102836004)(6436002)(52536014)(305945005)(74316002)(66476007)(66946007)(8676002)(76116006)(99286004)(66556008)(55016002)(9686003)(46003)(2906002)(476003)(7736002)(86362001)(81166006)(229853002)(25786009)(53546011)(81156014)(6916009)(508600001)(44832011)(11346002)(14454004)(256004)(966005)(7696005)(446003)(76176011)(14444005)(53936002)(46492003); DIR:OUT; SFP:1101; SCL:1; SRVR:LO2P265MB1517; H:LO2P265MB1327.GBRP265.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: 419.consulting does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5f2X7E1m2zTKeMAb6hhsx5iElmdhAxz+v31Mz44I75zCC3bB3CjPlpTjYZcCOZNkbLSI01cXWDBG5GbVu948VlKcAi4o0cokvBHAmPl7TK00WrwLhim6X8MaU9zNlIqq7GriKXINvJkjQlny6ESZ2onPFvVm43HcpMYGjW9lZp8AqP3Iocd3UUjOvexZijGTawjVU6XwcwDIsfQrRWuCfR3e29R2Brsyw2qlBLLNJNxqjR8ip0UxsS0iGOyB+cSbFx5n8ktkc3q3K5YglNp/U9vjQ7lutx8KrpRU7wT3UCk9i1IfPjBpTCRWh/tKNnpj+QtY/YCbwFEaBYwSLDSPe56dhxYIoeiccFPdR8VE7HHzrN74jTpEDxMMu7qIyMdik4BAhjnCBiItrqDHUtJ7MMxCkmV2JOreD4DC3vqMltU=
Content-Type: multipart/alternative; boundary="_000_LO2P265MB1327E54F6CE3C39EAF0C3BD1C2C10LO2P265MB1327GBRP_"
MIME-Version: 1.0
X-OriginatorOrg: 419.consulting
X-MS-Exchange-CrossTenant-Network-Message-Id: 12fbc1b2-93e0-46b4-13eb-08d711196a84
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 16:01:55.3380 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9c2ced3e-7522-4755-87dc-f983abc66ec3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: andrew.campling@419.consulting
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P265MB1517
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Go7vRQ_vLyhrG7qC5UohdMl8Wlc>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 16:02:07 -0000

On 25/07/2019 16:29, Stephen Farrell wrote:

> On 25/07/2019 16:19, Andrew Campling wrote:
      >> In Europe, DNS constitutes personal data and therefore needs to be
      >> processed in compliance with GDPR

> Sorry, it's not clear to me what you mean there.

> It's also not clear to me that the act of answering a DNS query is something where there's a specific way to comply with GDPR or not comply with GDPR.

> Can you provide a pointer to something with more detail as to GDPR requirements for DNS recursive resolvers?


Important health warning, for specific guidance please check with a privacy lawyer and/regulator, I'm neither!

It's the processing of DNS (data) that needs to be in compliance with GDPR, there's plenty of guidance out there regarding how personal data should be processed in a compliant manner.  The regulators have indicated that they view DNS as personal data, so in scope with regards GDPR.

For guidance regarding a specific implementation or application and how to ensure GDPR compliance, I'd suggest approaching the relevant national regulator as any such guidance will be case-specific.  In the UK this would be the Information Commissioner's Office - see https://ico.org.uk/for-organisations/guide-to-data-protection/ as a good place to start and  https://ico.org.uk/global/contact-us/ for contact information.


Andrew

v2.23.0 | Report a Bug | By Email