[Uta] MTA-STS-03 review

ranjana mukhia <fbmails2me@gmail.com> Tue, 04 April 2017 12:13 UTC

Return-Path: <fbmails2me@gmail.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1E3129556 for <uta@ietfa.amsl.com>; Tue, 4 Apr 2017 05:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TwgrApxkaJ6n for <uta@ietfa.amsl.com>; Tue, 4 Apr 2017 05:13:01 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 12E5B12871F for <uta@ietf.org>; Tue, 4 Apr 2017 05:13:01 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id d2so27002404oig.1 for <uta@ietf.org>; Tue, 04 Apr 2017 05:13:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0+VmB982cKF+Yg4IztQUGSSyWwS1vQJ+ehhBw3pC5gU=; b=mUlN5rn5a19zhI7jfBSCa0olGfODruI0X/xUblx1q0uvAxXh+648+zdyVyPKv192I6 uq8XJA3NEwMA3DquZYi5m/1k8Ki9gXXBSGJYT+HZNo4pD21WNVrzpU3kxCZcOC5sB1ou niOkEKMsa3XSsbKIj5BfiaZ2+Nj4Hq0OCBS20MWassmtvCMk/f6iJvQHQu/D7LCj/p1J j5wwzJUkrI+GXqBuSH+HCbbUyk3enZbvZILP7NFGQT5ILy97YJzQx8sFfGc9C7eAbTTh /mDK2mdXYVBUn8s0M7h9G9Du9zZbQBuL8A8kxYgz+pp0Yrr8YnF566l5ot2Aox0nds5Z xubA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0+VmB982cKF+Yg4IztQUGSSyWwS1vQJ+ehhBw3pC5gU=; b=fsC1Q/qBMbPOdtnmZ66qqKdz3R065Rg0QM6kZVrXx1D7oB6v6t8FKWcWz4rpWOGQqW BDqe8vpcsrCOjlmV5PZo0kSx+mWT7GUNAa4XrGxYf2B0Kg7ShNfttSK02FShWtdyzixp YND6tn9sfIVaDvRhIvzzwLJVUre+N7VNoLmBDyc1b2Pq2jMjTCWRPpWWgES4L1IunXZj qDT4CZARTBbjPZoCn++kQjEv3WJCEziX/1v6zMW+h9B2W8QSX59aMUI828Je0dD9hGdc zcwIIXNanTqHRftr92gnlskY0uSRlxLyVOj2Id18M4GCjTSPY1PCLJ36h1OcbvWwTUfa Ea9w==
X-Gm-Message-State: AFeK/H0NMy2ec4IbUwYE4LRs9nWhIFihVbliNT1uXaqxpcSiOpEGPah/b3ylPMWvMTYvxVpnSmtRSNdKEkhHuQ==
X-Received: by 10.157.21.86 with SMTP id z22mr245982otz.36.1491307980227; Tue, 04 Apr 2017 05:13:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.101.11 with HTTP; Tue, 4 Apr 2017 05:12:59 -0700 (PDT)
From: ranjana mukhia <fbmails2me@gmail.com>
Date: Tue, 04 Apr 2017 17:42:59 +0530
Message-ID: <CAHUgVDDDL6+4gyvL1c0-bLsi2yL2JEzJ73C3F-To2K4y8UEDvw@mail.gmail.com>
To: uta@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c191e04698acf054c5632f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/pZMtvIgSLL__2nF9tPydiIKeOAE>
Subject: [Uta] MTA-STS-03 review
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 12:13:03 -0000

Hi All,

I have a basic question to ask related to the below-mentioned lines of the
draft.

>We additionally consider the Denial of Service risk posed by an

>  attacker who can modify the DNS records for a victim domain.  Absent
>   SMTP STS, such an attacker can cause a sending MTA to cache invalid
>   MX records for a long TTL.  With SMTP STS, the attacker can

>   additionally advertise a new, long-"max_age" SMTP STS policy with
>  "mx" constraints that validate the malicious MX record, causing
>   senders to cache the policy and refuse to deliver messages once the
>   victim has resecured the MX records.

>   This attack is mitigated in part by the ability of a victim domain to
>   (at any time) publish a new policy updating the cached, malicious
>   policy, though this does require the victim domain to both obtain a
>   valid CA-signed certificate and to understand and properly configure
>   SMTP STS.



*can the above mentioned solution, provide the preemptive measure for
avoiding the DOS attack?*



Regards

Ranjana

Centre for Development  of Advanced Computing(CDAC),Bangalore(India)