IETF Logo Mail Archive

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

John C Klensin <john-ietf@jck.com> Fri, 27 December 2019 01:00 UTC

Return-Path: <john-ietf@jck.com>
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 970441200C4 for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 17:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 ILnmGjZ5-P96 for <ietf-smtp@ietfa.amsl.com>; Thu, 26 Dec 2019 17:00:16 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38CE112009C for <ietf-smtp@ietf.org>; Thu, 26 Dec 2019 17:00:16 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ikdzC-000GWS-8M for ietf-smtp@ietf.org; Thu, 26 Dec 2019 20:00:14 -0500
Date: Thu, 26 Dec 2019 20:00:06 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf-smtp@ietf.org
Message-ID: <A0B67A507CCD3DFCB37BF130@PSB>
In-Reply-To: <C8C800EE-4CAA-48E4-AF22-21C80999C74E@dukhovni.org>
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <0cbf23be-dbfc-f78f-8e63-d92d6e34fbf0@network-heretics.com> <37C195CAA3295DE832711B38@PSB> <434a885c-3709-b90b-40cd-4c45ba339666@network-heretics.com> <64DEBBA8-FEBC-499B-80A0-EF49A2210BB2@dukhovni.org> <C8C800EE-4CAA-48E4-AF22-21C80999C74E@dukhovni.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/GDrQ-jyWLliS1V3x8ZIom_QFluk>
Subject: Re: [ietf-smtp] Possible cont4ibution 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: Fri, 27 Dec 2019 01:00:17 -0000


--On Thursday, December 26, 2019 17:59 -0500 Viktor Dukhovni
<ietf-dane@dukhovni.org> wrote:

>> On Dec 26, 2019, at 5:37 PM, Viktor Dukhovni
>> <ietf-dane@dukhovni.org> wrote:
>> 
>> It may well be too soon to *mandate* TLS, but we could
>> perhaps MUST a RECOMMENDED or a SHOULD for inter-domain relay
>> of email.
> 
> I botched that sentence, the "MUST" was not supposed to be
> there.
> 
> 	... we could perhaps agree on ...

Since I've recently been chewed out again for writing long
messages, if there is an attempt to form a WG, argue that this
should be in scope.  And, if a WG is created with it in scope,
propose text and see where it leads.

   john

v2.23.0 | Report a Bug | By Email