IETF Logo Mail Archive

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

John C Klensin <john@jck.com> Fri, 27 December 2019 18:42 UTC

Return-Path: <john@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 02AFC120806 for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 10:42:42 -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 hgy7QwyHKaw1 for <ietf-smtp@ietfa.amsl.com>; Fri, 27 Dec 2019 10:42:40 -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 A3D14120018 for <ietf-smtp@ietf.org>; Fri, 27 Dec 2019 10:42:40 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1ikuZL-000J3T-G6 for ietf-smtp@ietf.org; Fri, 27 Dec 2019 13:42:39 -0500
Date: Fri, 27 Dec 2019 13:42:33 -0500
From: John C Klensin <john@jck.com>
To: ietf-smtp@ietf.org
Message-ID: <C620BDD6C0C346E6E9651168@PSB>
In-Reply-To: <2BB1805D-05F3-47B6-9897-45C4AE05EB08@dukhovni.org>
References: <FCDE38AEA7DDB9BB0FB206F9@PSB> <0605ee67-86eb-3e27-26b0-7a1c16a37bee@tana.it> <553FE6792AFBD83DA7DFE7F0@PSB> <2BB1805D-05F3-47B6-9897-45C4AE05EB08@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@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/FKODPH4rTmMNMVx4dr7uQ2n93KE>
Subject: Re: [ietf-smtp] Possible contiibution 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 18:42:42 -0000


--On Friday, December 27, 2019 13:13 -0500 Viktor Dukhovni
<ietf-dane@dukhovni.org> wrote:

>> On Dec 27, 2019, at 12:07 PM, John C Klensin
>> <john-ietf@jck.com> wrote:
>> 
>> Ok, I have revised the working draft to include additional
>> issues suggested by on and off-list notes.  Several of those
>> identified issues already called out in -02 either by the
>> errata or by the inline CREF notes.
> 
> It seems that the -02 has not yet been uploaded, did you mean
> for it to be already available?

Sorry... meant -01.  Been thinking about and working on -02 too
much.   It should be up in the next couple of hours.

  john

v2.23.0 | Report a Bug | By Email