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

Alessandro Vesely <vesely@tana.it> Wed, 16 July 2014 08:24 UTC

Return-Path: <vesely@tana.it>
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 F32391A0322 for <ietf@ietfa.amsl.com>; Wed, 16 Jul 2014 01:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level:
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-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 BfTmF-0hCcYe for <ietf@ietfa.amsl.com>; Wed, 16 Jul 2014 01:24:04 -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 3EA8C1B29E4 for <ietf@ietf.org>; Wed, 16 Jul 2014 01:24:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1405499038; bh=FIFGfTclOa9K/pvRjRie14UJCBzFCd1FJVIwHM1VWy4=; l=1338; h=Date:From:To:References:In-Reply-To; b=QNet08ezBxktg3kAlC7VH1mynM63Wwn+E13oli2X6Ftfph4Ev8u2+aOxx108SbOfW FNsqCBu1kkKWwycKTAKTTwJJZHry25lSlYx/xBd34GZ1V4JWWkcMaAgeHvhXDrcTzr 7r1JgoPo661u4opGqER+K0JzVrUhs30jtCF/R50k=
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; Wed, 16 Jul 2014 10:23:58 +0200 id 00000000005DC033.0000000053C6369E.000071AE
Message-ID: <53C6369E.90403@tana.it>
Date: Wed, 16 Jul 2014 10:23:58 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: really to do with Re: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)
References: <20140714164212.22974.20340.idtracker@ietfa.amsl.com> <4450964.7UmRiHm4KW@scott-latitude-e6320> <20140715001549.GG2595@mournblade.imrryr.org> <2270075.AYnCC6OxAQ@scott-latitude-e6320> <20140715033346.GL2595@mournblade.imrryr.org> <026301cfa01a$7ebdde40$4001a8c0@gateway.2wire.net> <20140715112023.GU2595@mournblade.imrryr.org> <01PA78TOWR4O007ZXF@mauve.mrochek.com> <53C55509.8050108@dcrocker.net> <01PA7DC3IFS0007ZXF@mauve.mrochek.com>
In-Reply-To: <01PA7DC3IFS0007ZXF@mauve.mrochek.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AH7CYl3-ZJk175BYLrTmM9FTz9g
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: Wed, 16 Jul 2014 08:24:07 -0000

On Tue 15/Jul/2014 19:22:57 +0200 Ned+ietf wrote:
> 
>> But it's not likely to have much to do with DMARC, anytime soon.
> 
> I've yet to see any evidence that anything being proposed will have
> any effect on DMARC in the short term. I've heard a bunch of
> assertions that if the need arose MTA changes can be rolled out
> quickly. I have 25+ years of experience doing this stuff that says
> otherwise.

I fully agree.  However, it is the converse statement --evidence that
DMARC will have any effect on reclaiming semantics of the most basic
protocol elements in email-- which is intriguing.

If you pardon my oversimplifying, recipient semantics is well
established by SMTP.  Defining the meaning of the domain requires DNS
write access, while the local part's meaning is local.  DMARC can be
seen as an attempt to reestablish the same in From:, conditioning
deliverability to its enforcement like in the previous case.

Thus far, DMARC is a private agreement which works reliably only with
direct mailing, where it is backed up by SPF.  DKIM is afflicted by a
fierce crowd of breakage forms, which nobody seems to be interested in
as they occur sporadically in the current use case.  The challenge is
to see its much trumpeted bet on multi-hop tolerance.  IMHO, there
lies the worthiness of the proposed WG.

Ale