Re: [ietf-smtp] why are we reinventing mta-sts ?
Viruthagiri Thirumavalavan <giri@dombox.org> Mon, 07 October 2019 17:47 UTC
Return-Path: <giri@dombox.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B903B120168 for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 10:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dombox.org
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 Tm5VUwPET8am for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Oct 2019 10:47:47 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 E1B2B1200F5 for <ietf-smtp@ietf.org>; Mon, 7 Oct 2019 10:47:43 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id t10so7209433plr.8 for <ietf-smtp@ietf.org>; Mon, 07 Oct 2019 10:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dombox.org; s=default; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GtnNYMpRUEEFqnl19FiYv/APLVg2ekWGpkjM8GMyMlg=; b=fUWyD81Z/h4KmSV2lIRdSChbrTRmBE9GX6mCyylkEctYmbmeGQ/WdxkG5JtWLFmLfB +UXs9N1TAcwlcoXznQyvpSYqyVIeMbfzs21WBXuD4qnbA3pB9mJRxaN9hCg9CEn02aaa 2iO572fZJDk8nGTzj3n1TTDOOKdja7MoyZSo9uxLulKifdmpZch+lYK2DoM0yTYaWeeq 3q4XlIbGVhKarLoeXxSNwzVwPUQ5//xGcP5frL1xcj8JK6TJkuWJIxNFGMGQ6V02dzEu 1azVqmFYwYTWJZHyg3+uqa00USD0wQ1Ww3LHdcIURQqlN5CzOrckRuewZwifKAeP8FpR iTKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GtnNYMpRUEEFqnl19FiYv/APLVg2ekWGpkjM8GMyMlg=; b=DEfjgQlGBntEqxbrl3CcMWc6P4oQMJbS8k+0zpg19Qy52hIlzJZ+vRhbvxhe7TyB01 ttyChVbEaNlqMiJCIxnpVaZS0bZXQNxIQiScCTdi9bDjufGKJoFN7/Q36IGCUCIUNgrZ fK44V2P6xf5/vV2IcbcColFVHdFBehPWGBJ8zYR54wP4JjTlCTbVM35ToTOr3y7bwx0n pC8IEby0ntVPcoT/tld6Ld4zIRmDid95jD+tV8KnaILtfgpDLPCYEPjEe4q3Yowg+DHa vIk+6v4C24dskgGiDvmc/Ce1wYKhPMLYhZFWSbpF/Io0iqQKDXXtrhr3w2X2ZPVM7ATs PYdA==
X-Gm-Message-State: APjAAAUB+BRUarC2QgenvgW3QOL4SgZmWEYx/yah3LBchVWaNOCExevi uMsVZWuRKNSR5wNJnKGMcTx9CnzE27eI6d+f8O5W6Q==
X-Google-Smtp-Source: APXvYqwi3OdSIV0/d+f7/DBrh/b0DjmvsDhTOB4NhUwmB2XIHY6KblPfCMBxQHe9IxZaoZrTNaTtkbv4VL3SgA2BJtg=
X-Received: by 2002:a17:902:5a44:: with SMTP id f4mr21984057plm.77.1570470463321; Mon, 07 Oct 2019 10:47:43 -0700 (PDT)
MIME-Version: 1.0
References: <20191007002348.GA23742@x2.esmtp.org> <20191007015616.BE113BB3D68@ary.qy> <CANtKdUeC0NVfvVpbHtwd=OoO=BoT8KNWVx8BGF-GPZPU-zo6QA@mail.gmail.com> <CAOEezJTH4Jukz2J4jSDfixECg2Jyyk4+cDnasiAoa4Q2F9=ZZw@mail.gmail.com> <b0dae4ca6e95dc83ca70f71ad780a1432273bcf5.camel@aegee.org> <CAOEezJRXUZkPoJn_kV92q=OQoUs32VzTR5a0JeAKg6NYBW55=Q@mail.gmail.com> <19705.1570469430@turing-police>
In-Reply-To: <19705.1570469430@turing-police>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Mon, 07 Oct 2019 23:17:17 +0530
Message-ID: <CAOEezJRXeF3hioZOD=-Mn9Qj0P0wxHYD2gY5igs=nH9v7fKBeg@mail.gmail.com>
To: Valdis Klētnieks <valdis.kletnieks@vt.edu>
Cc: SMTP Discuss <ietf-smtp@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000018cb5a059455a6e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/fvQTAc6y62vQTUA5XPBwfkoRETM>
Subject: Re: [ietf-smtp] why are we reinventing mta-sts ?
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 07 Oct 2019 17:47:50 -0000
Yes that's a good idea to solve this problem. But then again, people still have to pay money to make their mail secure. Not everyone would go for that. We can't always go like "we already defined the MTA-STS standard. You all have to live with it". So there is nothing wrong in discussing the alternatives. As Keith said, a new proposal need to have a high bar to become standard. And if DoT is not possible as John said, then my proposal still have a long way to go. Thanks On Mon, Oct 7, 2019 at 11:00 PM Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote: > On Mon, 07 Oct 2019 22:55:19 +0530, Viruthagiri Thirumavalavan said: > > > We both use a different demographic to define "end user" for MTA-STS. The > > way you see it, an end user is a "mail server operator". The way I see > it, > > an end user is a "small business" who hosts their mails in a third party > > mail service like Gmail. Configuring an HTTPS server is not going to be > > easy for such small businesses. > > The obvious answer is, of course, to write the proposal such that the > https server > can be outsourced the same way the email service was outsourced, and the > DNS > service was outsourced to a DNS hosting company. > > There's an obvious business opportunity for hosting the email, the DNS, > the http, and > any other bits as one turnkey package. > -- Best Regards, Viruthagiri Thirumavalavan Dombox, Inc.
- Re: [ietf-smtp] why are we reinventing mta-sts ? John R Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Claus Assmann
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Daniel Margolis
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? Дилян Палаузов
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? John R Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Stan Kalisch
- Re: [ietf-smtp] why are we reinventing mta-sts ? Daniel Margolis
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] why are we reinventing mta-sts ? Rich Kulawiec
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Tony Finch
- Re: [ietf-smtp] why are we reinventing mta-sts ? Keith Moore
- Re: [ietf-smtp] why are we reinventing mta-sts ? Tony Finch
- Re: [ietf-smtp] why are we reinventing mta-sts ? Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viruthagiri Thirumavalavan
- Re: [ietf-smtp] MTA-STS scale (was: why are we re… Viktor Dukhovni
- Re: [ietf-smtp] why are we reinventing mta-sts ? Rich Kulawiec
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] why are we reinventing mta-sts ? Hector Santos
- Re: [ietf-smtp] why are we reinventing mta-sts ? Viktor Dukhovni
- Re: [ietf-smtp] why are we reinventing mta-sts ? John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Viktor Dukhovni
- Re: [ietf-smtp] [OT] (signed TLDs) John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Viktor Dukhovni
- Re: [ietf-smtp] [OT] (signed TLDs) John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Viktor Dukhovni
- Re: [ietf-smtp] [OT] (signed TLDs) John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Viktor Dukhovni
- Re: [ietf-smtp] [OT] (signed TLDs) Tony Finch
- Re: [ietf-smtp] [OT] (signed TLDs) John R Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Tony Finch
- Re: [ietf-smtp] [OT] (signed TLDs) Hector Santos
- Re: [ietf-smtp] [OT] (signed TLDs) Arnt Gulbrandsen
- Re: [ietf-smtp] [OT] (signed TLDs) Valdis Kl=?utf-8?Q?=c4=93?=tnieks
- Re: [ietf-smtp] [OT] (signed TLDs) Hector Santos
- Re: [ietf-smtp] [OT] (signed TLDs) Keith Moore
- Re: [ietf-smtp] [OT] (signed TLDs) John Levine
- Re: [ietf-smtp] [OT] (signed TLDs) Mark Andrews
- Re: [ietf-smtp] [OT] (signed TLDs) Viktor Dukhovni
- Re: [ietf-smtp] [OT] (signed TLDs) Hector Santos
- [ietf-smtp] HTTPS degrading (was: [OT] (signed TL… Keith Moore
- Re: [ietf-smtp] [OT] (signed TLDs) Tony Finch
- Re: [ietf-smtp] HTTPS degrading Hector Santos