Re: [dmarc-ietf] ARC-Seal is meaningless security theatre

Dave Crocker <dcrocker@gmail.com> Fri, 18 August 2017 23:20 UTC

Return-Path: <dcrocker@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5701113214D for <dmarc@ietfa.amsl.com>; Fri, 18 Aug 2017 16:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 gVp-y_JVgibW for <dmarc@ietfa.amsl.com>; Fri, 18 Aug 2017 16:20:43 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E064132064 for <dmarc@ietf.org>; Fri, 18 Aug 2017 16:20:43 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id x3so110754133oia.1 for <dmarc@ietf.org>; Fri, 18 Aug 2017 16:20:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BDiO+TvGhA96paPAULw4BP44wpO1lO4XGKdW2oGxfTU=; b=i8r6R1WcdjCYqs9XjZkWkfj90L7e4nvmGybxH0KuKc7g5N/pLWdCun3R2Qq2GXwjTU UbLfuihatuSmbw9WHXSt6msXy28GCBpTbmucCICILhtJvWqWoXcjO7jfRu12DltRnI0s bRguvXB3HQKqvG6SaBCNmHnUivnM5xdTHFHXuxMJ+0wk8PSQl1cUmoQ0woDQjcwMRYPB lUceME3ePDTKzYDb7if/RAN5BJY6puKpOulV9tJc5tu09xLsRcBz+34TL1sdnxMdm4Cx 1KEnbAUZzGW0WCGGhbYpNsX5dC+NjXBe+nhq4hD6XT+gfnmgreR4hAUvpUyBWJJ9Aapd hQGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BDiO+TvGhA96paPAULw4BP44wpO1lO4XGKdW2oGxfTU=; b=Xc+k/oB33wYN/+5rnEvWgr5wIm2AnxLk6EwYVr245t3LA7sOBzvEi1Vu9mGn/hyPPh dZT9/Nycqbs/cm5bXBKJh/u9GovE+6GL7E0LvVF9wkioRfIL8Yv2+E9HS1On95UgN+t0 EKBfqy4l6UfCfyct8eJkZFDPXn5UmNECog89Pd+u+AOL/jf/Mg9QHuIwY0QkSa5Oehlh uZEJK6jblihgfWJl7QqgrL2NL4RRRC5VQ813ou6+/ytPHQwyuHu4PnLa+KUsJiMUUo0A hUjlWsqkI+25/DxbZbZFhoSiz7dX5sMnnRjckGtUnulCFlnh1UugQkXmol+2s1oMnFA6 Vx1w==
X-Gm-Message-State: AHYfb5hwnqI5+3zT3/JqhO2+EXTR/q5OGD4GMSM1SQREuXL+r/7vrAAK ZpTVu/vFjnUf8zKG9O0=
X-Received: by 10.202.235.140 with SMTP id j134mr12943539oih.281.1503098442016; Fri, 18 Aug 2017 16:20:42 -0700 (PDT)
Received: from ?IPv6:2602:304:cda0:8800:d17e:7fe3:9cb7:7c98? ([2602:304:cda0:8800:d17e:7fe3:9cb7:7c98]) by smtp.gmail.com with ESMTPSA id h138sm4964513oic.43.2017.08.18.16.20.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Aug 2017 16:20:40 -0700 (PDT)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Seth Blank <seth@sethblank.com>, "dmarc@ietf.org" <dmarc@ietf.org>
References: <1502083287.2191248.1065195288.7CDC7FF3@webmail.messagingengine.com> <a08c7590-ded3-1642-4ffc-07848b3c6cd2@gmail.com> <e14f2130-6f00-4ef1-485b-850a4cc1c48c@gmail.com> <1502495646.4099176.1070896040.2B09B1F8@webmail.messagingengine.com> <166070f0-4ba1-70da-1f73-885b4a7f7640@gmail.com> <1502497178.4103451.1070917304.23DD466D@webmail.messagingengine.com> <598F9484.7020700@isdg.net> <CABuGu1p=oLfLRkuoaDHoz3Cv3_FrURdsFPzkac7jNzBpqBmiSg@mail.gmail.com> <599484FB.9050908@isdg.net> <1502929303.4038704.1075868960.5D80A788@webmail.messagingengine.com> <CAD2i3WN_bmDgmQBw3pnyu7vWJJM2Kzwgru87VhK=NA_H91B+og@mail.gmail.com> <1502930858.4042926.1075890568.5069945B@webmail.messagingengine.com> <CABuGu1ofdkP6Gdsfin6KfpiTJW39gXz8Fa0iAAmXfcvyWGZxdA@mail.gmail.com> <CAD2i3WPuiMw6Gbdw0E+Gh=yNDfNjECMrqLHKPUspq_h6dnpbnA@mail.gmail.com> <f62ca9fc-e73c-82e7-173c-5cdc3c761dd6@gmail.com> <CAL0qLwZRfEEZ=Vz4tWAYEn97H9uvMzSyYe2+-Ak762qpvDmm3g@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <74033d99-6425-3676-e39e-64e1c947fb16@gmail.com>
Date: Fri, 18 Aug 2017 16:20:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwZRfEEZ=Vz4tWAYEn97H9uvMzSyYe2+-Ak762qpvDmm3g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/USIxDGnAhKBYj8RUOLGykr2TnUQ>
Subject: Re: [dmarc-ietf] ARC-Seal is meaningless security theatre
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2017 23:20:45 -0000

On 8/18/2017 11:10 AM, Murray S. Kucherawy wrote:
> 
> While I would normally agree firmly with that position, my view in this 
> case is softer given what I believe was consensus (I'm not the chair, so 
> that's not my call officially) that we're going to go for Experimental 
> status.
> 
> I submit that our primary mission here per our charter is to come up 
> with a mechanism that mitigates DMARC's damage to mailing lists.  The 
> claim that ARC as designed over-engineers a solution seems secondary to 
> me; the question we need to answer is "Can this mitigate the damage?"  
> With or without Bron's reduced design, that's the question before us.


Going for Experimental does not relieve the working group from trying to 
do careful engineering.

I'm sure you didn't mean to suggest otherwise, but fear that the result 
will be publishing a spec for something that is more complicated than it 
needs to be or less well understood than it needs to be.  Or both.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net