Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)

"Murray S. Kucherawy" <superuser@gmail.com> Fri, 18 July 2014 19:32 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C80441B2A16 for <ietf@ietfa.amsl.com>; Fri, 18 Jul 2014 12:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 hIg5D87WTO8b for <ietf@ietfa.amsl.com>; Fri, 18 Jul 2014 12:32:26 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A24871A000F for <ietf@ietf.org>; Fri, 18 Jul 2014 12:32:25 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id n3so1394244wiv.5 for <ietf@ietf.org>; Fri, 18 Jul 2014 12:32:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=65ubGScQtg8xr7jxj0EmyyhzExAW4UTPLQJcVrGEh4I=; b=B80LzyTqiHf2sW99nZg9jArA19p6SrkYdiTe7jlDXAs8ZLM+tkX196hcTpPXTISJAl c51AUiBAzIWdorL2O7ZPrIU1R/+hHklsbgF9sxSHhqoJmTMfIiTv/dS8NhauQd6vpVly OyukHG/M6r3Gv5E9iJDjtwHsP0R5iTFx+YuaCju6vm306ACIugu7C9nNW8I4jDKmPayU poq3NGvllo6Lcr34jEVpqqfu2Di2Aze3THDOEJ84puz5q+NOJGI75f4MqYC6vpNRpB1e biuwjcvdQVOQmw7gIWGvv360d+MCyPHSeVipWtDcSwIRZuYvNkzqjHeyyI/egBUya9cs U//w==
MIME-Version: 1.0
X-Received: by 10.180.105.68 with SMTP id gk4mr10843888wib.24.1405711944175; Fri, 18 Jul 2014 12:32:24 -0700 (PDT)
Received: by 10.180.10.99 with HTTP; Fri, 18 Jul 2014 12:32:23 -0700 (PDT)
In-Reply-To: <20140718174827.652621ADAF@ld9781.wdf.sap.corp>
References: <CAL0qLwYZPO9L9e7MHA6zP5vcTbQEJmwCSonLdMeQiOw4CUoiFw@mail.gmail.com> <20140718174827.652621ADAF@ld9781.wdf.sap.corp>
Date: Fri, 18 Jul 2014 12:32:23 -0700
Message-ID: <CAL0qLwaZLdWvjHQUnZf7c3T5GynotxVP=Z5a3461ytZGGtKLYw@mail.gmail.com>
Subject: Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary="f46d04426a6016d6c304fe7cd109"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/97eyCtm69k259y1-NT7K3XxfmxM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 19:32:27 -0000

On Fri, Jul 18, 2014 at 10:48 AM, Martin Rex <mrex@sap.com> wrote:

> Article 2 "Definitions" of this EU directive (page 7 of above PDF)
>
>   The following definitions shall also apply:
>    (a) "user" means any natural person using a publicly available
>        electronic communications service, for private or business
>        purposes, without necessarily having subscribed to this
>        service;
>

I am certainly no lawyer (are you?), but it seems to me that a corporate
domain owner that chooses to use DMARC to protect its brand might have
users within that domain -- employees, for instance.  I would claim that
such an employer's email servers do not comprise "a publicly available
electronic communications service", so I don't think employees using a
protected domain are "users" under this definition.  And even if that
doesn't wash, an employment contract (here, at least) typically grants the
Article 5 consent that makes this point moot, and is not typically a "Click
OK and forget" situation.

I imagine email service providers could secure the same sort of consent
through a privacy policy, though "I had no idea" might be a more successful
counter-argument there because nobody really reads those.

-MSK