Re: [dmarc-ietf] Proposal to adopt ARC documents into the WG (toward phase 2 milestone)

Alessandro Vesely <vesely@tana.it> Thu, 12 May 2016 07:28 UTC

Return-Path: <vesely@tana.it>
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 C5A3212D875 for <dmarc@ietfa.amsl.com>; Thu, 12 May 2016 00:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.298
X-Spam-Level:
X-Spam-Status: No, score=-5.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tana.it
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 GUtmuu8Yzxaa for <dmarc@ietfa.amsl.com>; Thu, 12 May 2016 00:28:48 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D601712D561 for <dmarc@ietf.org>; Thu, 12 May 2016 00:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1463038122; bh=OiREMxfEC2sJ5DGtRDY8CWVrqQ/jLrqdSnkj8+DFf44=; l=1432; h=To:References:Cc:From:Date:In-Reply-To; b=PqHgc3CGsNeKgGujNsTUXDfvZjlhWu04w/cEZ2B4uU/yspSprNbUo5LE7eLKn6fm2 dYrpUQaDRq70W/9O32+9jdWC1Kq05pXHfBDXS+lD7ptEmBzXqEs1r1E/RKkHt968UM BLtCNoB7ZCiLXV/gBq4z87ezmDP+iY0OAe2/Q8f0=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Thu, 12 May 2016 09:28:42 +0200 id 00000000005DC042.00000000573430AA.0000132B
To: "Kurt Andersen (b)" <kboth@drkurt.com>
References: <CABuGu1qZNGfGkPDVRcs5tb_KF=UyAfMG0XKs07tud81iFZF44g@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <573430A9.8080207@tana.it>
Date: Thu, 12 May 2016 09:28:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1qZNGfGkPDVRcs5tb_KF=UyAfMG0XKs07tud81iFZF44g@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmarc/hkHfdDjfyAuRbT3piXul7tu2Qb0>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: [dmarc-ietf] Proposal to adopt ARC documents into the WG (toward phase 2 milestone)
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 12 May 2016 07:28:50 -0000

On Wed 11/May/2016 22:35:29 +0200 Kurt Andersen (b) wrote:
> On Wed, May 11, 2016 at 11:40 AM, Alessandro Vesely wrote:
> 
>> If the body was altered the original DKIM-Signature is broken.  If AS(0) is
>> good --which is possible since it didn't sign the body-- and rfc5322.from
>> matches the AS(0) signer, can we then bypass DMARC validation?  To address
>> Brandon's concern, high value targets should never produce an AS(0) in the
>> first place.
> 
> AS[0] will not be "good" in the way you propose because nearly all of the
> transformations that will break DKIM will also break the AMS
> (ARC-Message-Signature) and, per
> https://tools.ietf.org/html/draft-andersen-arc-04#section-5.1.1.5 bullet 3,
> AMS must pass for the overall ARC set to be considered valid.

That requirement is not necessarily about AMS(0).  It can be AMS(i), i > 0.
(Indeed, the current spec contemplates i > 0 only.)

> I'd like to respectfully suggest that "bypassing DMARC validation" is
> pretty far out of scope for what we've intended with ARC.

Yet, I share the feeling which originated this thread, namely that ARC can do
more than validate email address portability (via forwarding) among a private
group of huge mailbox providers.

If a single solution can be used for both solving DMARC's indirect mail flows
problem and participating in safe forwarding, that can make life easier for
mail system maintainers.

Ale