Re: [ietf-dkim] Fwd: SendGrid, GetResponse and Hubspot being used over DKIM "patent"

"Mark Delany" <sx6un-fcsr7@qmda.emu.st> Tue, 05 December 2017 20:56 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636F2128891 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 12:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emu.st
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 wttFOI2RgYok for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 12:56:21 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 48E591286CA for <ietf-dkim-archive@ietf.org>; Tue, 5 Dec 2017 12:56:12 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id vB5Kp2C5001500; Tue, 5 Dec 2017 12:51:03 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=emu.st header.i=@emu.st header.b=pS+rNirU; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from f3.bushwire.net (f3.bushwire.net [203.0.120.11]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id vB5Kov1h001454 for <ietf-dkim@mipassoc.org>; Tue, 5 Dec 2017 12:50:59 -0800
Received: by f3.bushwire.net (Postfix, from userid 1001) id 6E5C234AA07; Wed, 6 Dec 2017 06:50:39 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=emu.st; s=2017; t=1512507039; bh=rpnbw8Cn2yLzeUGpJGyzLra0oqU=; h=Comments:Received:Date:Message-ID:From:To:Subject:References: MIME-Version:Content-Type:Content-Disposition:In-Reply-To; b=pS+rNirU0XeNipkwiN8uxAVwJtV9AT1uYEn0Ir/Efo9H3MSlbWD65nX50pIWF7AKB 6liKJhwDL++Axqk6OSOVVCh07NQrfQvyG0aOQ6JOPbTkeZn+jNbbKlMB6e1kPEFy+s otTVzAGvagGgo1veak3dmlJPYZKHzaiRgfi1SgRQ=1SgRQ=
Comments: QMDA 0.3a
Received: (qmail 83403 invoked by uid 1001); 5 Dec 2017 20:50:38 -0000
Date: Tue, 05 Dec 2017 20:50:38 +0000
Message-ID: <20171205205038.83402.qmail@f3-external.bushwire.net>
From: Mark Delany <sx6un-fcsr7@qmda.emu.st>
To: ietf-dkim@mipassoc.org
References: <011A51D9-76B5-4CE5-A457-3F820E2623E7@wordtothewise.com> <9F71493B-4A29-42A9-A354-2584B6A46873@wordtothewise.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <9F71493B-4A29-42A9-A354-2584B6A46873@wordtothewise.com>
Subject: Re: [ietf-dkim] Fwd: SendGrid, GetResponse and Hubspot being used over DKIM "patent"
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On 05Dec17, Steve Atkins allegedly wrote:
> 
> I thought this might be of interest to DKIM implementers.

> The Asserted Patents share a common specification.

Did the claimants vacuum up the IP of the now defunct Goodmail? Reads
somewhat similar to what they were once trying to sell. Particularly
the "contractual" obligations of the senders.

From what I can glean, the plan is to digitally sign the email along
the lines of S/MIME (PKI and CAs are referred to extensively and
exclusively) and the sender include a "pledge" about the contents such
as "no more than 5 recipients will get this email". Recipients can act
on the pledge in the knowledge that senders apparently won't lie in
their pledge. Or if they do lie something will happen to them -
exactly what or how is not specified.

How the pledge is validated across the whole of Internet email is
undefined as is what to do to the sender if the pledge is known to be
a lie.

There are no references to DNS, no reference to how they determine
identical mail (canonicalization), no reference to S/MIME or DKIM in
any of their filings.

I guess the "pledge" on the part of the sender is vaguely novel but
there is no equivalent in DKIM as far as I recall. Maybe the vendors
you refer to have features that emulates pledges when sending email?

For moral equivalence, the Date: header is a pledge as to when the
email was composed/sent and Content-Type: is a pledge as to how the
MIME part has been encoded so the novelty is not even that there are
pledges in the email, just the nature of the pledge.

To me they seem to have invented a new mail header.


Mark.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html