IETF Logo Mail Archive

Re: [Gen-art] [Uta] Genart last call review of draft-ietf-uta-smtp-tlsrpt-17

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 08 March 2018 23:46 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BE9126CBF; Thu, 8 Mar 2018 15:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 S_nd2-l-hvP3; Thu, 8 Mar 2018 15:46:44 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 C79D5126DCA; Thu, 8 Mar 2018 15:46:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 7BC821C5BAF; Thu, 8 Mar 2018 15:46:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1520552804; bh=P60k5qIJ0nTzdb0CV96dyUKqU/Ara8s20Rz1J2ilRgw=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=p7b5Jit4Lq1ov3BpA9PkXFpkYAe4X/IVTBtuWep1ZuzHJzGMiJBdnvN2eYwAbIzNB xlmrP9L1Y15wXkL3+iTkcViBmRbW2XDAjaCyVzIS5HUU1b/7lV2sf2I1u/Lkgtdn6P NvqlDRk+Rg53x+i8FCQKNpxDBTfta7ZNvoC5SNAE=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id A95CD1C0C10; Thu, 8 Mar 2018 15:46:43 -0800 (PST)
To: Viktor Dukhovni <ietf-dane@dukhovni.org>
Cc: gen-art@ietf.org, uta@ietf.org, draft-ietf-uta-smtp-tlsrpt.all@ietf.org, ietf@ietf.org
References: <152054808275.11187.13276762980596133506@ietfa.amsl.com> <0423F6BE-6CF5-4DBA-A241-56142268D067@dukhovni.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <5960ef77-8310-0b05-6c89-46b35023f314@joelhalpern.com>
Date: Thu, 08 Mar 2018 18:46:42 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <0423F6BE-6CF5-4DBA-A241-56142268D067@dukhovni.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9Bxb0MO9-KNhaalvUL-3hJQ94oQ>
Subject: Re: [Gen-art] [Uta] Genart last call review of draft-ietf-uta-smtp-tlsrpt-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 23:46:46 -0000

A reasonable perspective.  Could that be added to the document?

Yours,
Joel

On 3/8/18 6:33 PM, Viktor Dukhovni wrote:
> 
> 
>> On Mar 8, 2018, at 5:28 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
>>
>>     It is surprising in Section 3 Bullet 4 that reporting via email requires
>>     that the report submitted use DKIM.  Particularly while ignoring any
>>     security errors in communicating with the recipient domain.
> 
> Actually, this is not surprising.  The main security risk here is report spam,
> that will drown the true signal in noise, making it impossible to notice real
> validation failures or operate the service.
> 
> Therefore, the report origin domain must be authenticated via DKIM.  I'd
> be tempted to go further and require a particular "selector" prefix that
> is specifically chosen for "tlsrpt", so that with domains such as "gmail",
> where anyone can get an email account, just being a user on the sending
> system is not enough to be able to forge a DKIM authenticated report.
> But that would create significant complications for the sender to make it
> so, and so is probably not needed.
> 
> In summary, when sending reports the party that needs to be authenticated
> is the sender domain, while the receiving domain is presumed operationally
> compromised, and so should be exempt from any authentication requirements.
>

v2.23.0 | Report a Bug | By Email