Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP

Dave Crocker <dhc@dcrocker.net> Wed, 01 January 2020 20:43 UTC

Return-Path: <dhc@dcrocker.net>
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 68A771200E0 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 12:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 UYO5UVzOEchr for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 12:43:20 -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 9D42C120096 for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 12:43:20 -0800 (PST)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 001KiCYt012989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 12:44:12 -0800
To: ietf-smtp@ietf.org
References: <20200101175510.8549A11E2905@ary.qy> <D441E0BE-1F32-4329-9296-A5026540E8D0@dukhovni.org> <994e7a23-9e80-4751-6067-8863ad0ee72f@network-heretics.com> <2Iq+URBKeODeFANB@highwayman.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <df822325-7149-6c3f-3136-94b302db0a61@dcrocker.net>
Date: Wed, 01 Jan 2020 12:43:11 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <2Iq+URBKeODeFANB@highwayman.com>
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/ietf-smtp/GkNaTJZKwJc8Q2Cm1z0qRsnIrxY>
Subject: Re: [ietf-smtp] Possible contribution to moving forward with RFC5321bis SMTP
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: Wed, 01 Jan 2020 20:43:23 -0000

> No-one in the world of large scale transfer thought that server certs
> from existing CAs (or DANE and its reliance on DNSSEC) were going to
> work reliably at scale ... so the bulk handlers of email went for (and
> have deployed) MTA-STS (RFC8461) instead.


This reminds me of a basic suggestion in trying to deal with interesting 
problems...

For every proposal here, I strongly suggest that it begin with a 
functional description that is entirely non-technical.  No acronyms and 
no protocols.

Just say:

    1.  What functional/semantic goal is being sought

    2.  What problems there are with not having that goal met

    3.  What current mechanisms, which might serve to meet the goal,
        don't.

    4.  How adopters will be motivated

After getting agreement on these 4 point, it will be reasonable to 
consider specific mechanisms for achieving the goals.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net