Re: [ietf-smtp] [Shutup] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG (fwd)

"Kurt Andersen (b)" <kboth@drkurt.com> Tue, 01 December 2015 18:25 UTC

Return-Path: <kurta@drkurt.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D78B1B2EB0 for <ietf-smtp@ietfa.amsl.com>; Tue, 1 Dec 2015 10:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level:
X-Spam-Status: No, score=-0.779 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, SPF_PASS=-0.001] autolearn=no
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 EUhZn9XzN4Y3 for <ietf-smtp@ietfa.amsl.com>; Tue, 1 Dec 2015 10:25:29 -0800 (PST)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 CA7811B2E54 for <ietf-smtp@ietf.org>; Tue, 1 Dec 2015 10:25:28 -0800 (PST)
Received: by qkao63 with SMTP id o63so6174914qka.2 for <ietf-smtp@ietf.org>; Tue, 01 Dec 2015 10:25:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=JRTarXcCHMX3FyffLHHyJaBLZN4+XTePNBsrPxR2sf0=; b=JFt3VMIPNelJpIL3ip3lfnuF0jz4cIF5EUFZZxLXdbTi0bcPSW7u5veOPAGD3Xmn0B WuEjBi9j9qlDLcbl6RXnNxjjKd1Ip7d1Lrb4/stvBvHDfAY4v5NHC9vL26agh1mgbmAg NEWTz8nsycDHEZgQzbM0WqXsrYWU9QjYOCQ8A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc:content-type; bh=JRTarXcCHMX3FyffLHHyJaBLZN4+XTePNBsrPxR2sf0=; b=UleccU0C46Al0GzCIY7C3nAMb4jDWjDvIQUz1IYgLFysA9nOEzW/R56ANqqk2TFFdV BB22fuzg7je1Q3I4SSTeQsF356eFMVLm7APzeW1RryLlYAH2PO26PkJTMZbeMapoHagB GUnwybgSlJDRZubh50GisJoOXuLDKrgmmSFfjEIAQta8KfWJs14Z/BQKakRGo4ykMZbb xWvFQ8MjcbV/HZTRdvPqJulO7u4bpY+ieD6qrbSwsh14SKWzi/nVAYC+odb5ugttOcc8 2QK472MIqZNbOi4t7zeDITPpgBeG7cPr3bwqflExAqT1rKL77sR1JBwXv9iLuz6JKMDw RCMg==
X-Gm-Message-State: ALoCoQnuWiYO8TDAaH3UcecBKLpJMH2Ohhql1QZC90IFGW6ywc0reeYYAqDOO+Gxna5QiRZwqkdy
MIME-Version: 1.0
X-Received: by 10.55.76.137 with SMTP id z131mr83047795qka.29.1448994327941; Tue, 01 Dec 2015 10:25:27 -0800 (PST)
Sender: kurta@drkurt.com
Received: by 10.55.198.219 with HTTP; Tue, 1 Dec 2015 10:25:27 -0800 (PST)
Date: Tue, 01 Dec 2015 10:25:27 -0800
X-Google-Sender-Auth: CrxFDgKov_TjbDT_1VGB2nrZKFo
Message-ID: <CABuGu1pj+8ZUiu=PziBNR7Vb1w4+OA5t7dEw-JU27Eta-rKeXg@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/G6b0MpnkhNQq7MyE7JTwiLnx0Dw>
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, SMTP Discuss <ietf-smtp@ietf.org>
Subject: Re: [ietf-smtp] [Shutup] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG (fwd)
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 18:25:30 -0000

On Tue, Dec 1, 2015 at 9:57 AM, Ned Freed <ned.freed@mrochek.com> wrote:
> Second, good luck on getting anyone to comment on the details of their own
> secret sauce, or for that matter getting anyone who has learned such details
> through business relationships. All such information is pretty much
> guaranteed to be covered by confidentiality or nondisclosure agreements.

Last year, when we had a discussion session at M3AAWG to discuss how
to effectively move from IP-based reputation toward a domain-based
reputation model, it was clear that there were two camps of thought:

1) Throw everything (all headers, all content) into a ML framework and
let the algorithms figure out what to pay attention to in order to
determine spam/not spam as well as a reputation accrual mechanism for
any authenticated domain entities associated with the message;

2) Cherry-pick particular attributes and features of a message, with
particular attention to some headers and come to some heuristic
determination of spam/not spam + reputation accrual.

People with big ML frameworks and expertise use every available piece
of information. If they are mailbox providers, they use it on behalf
of their customers. If they are state actors, they use it for their
own purposes.

It is unclear which would be more affected by redacting trace headers,
but in the interest of moving domain authentication forward to handle
indirect email flows, we are proposing an authenticated version of the
Received chain in https://tools.ietf.org/html/draft-andersen-arc-00
and https://tools.ietf.org/html/draft-jones-arc-usage-00. We think
that this will be a benefit rather than a detriment to the community.

--Kurt