Re: [ietf-smtp] Email standard revision

John C Klensin <john-ietf@jck.com> Tue, 18 February 2020 22:42 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 3113612083A for <ietf-smtp@ietfa.amsl.com>; Tue, 18 Feb 2020 14:42:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 nA3SCsg_yfdQ for <ietf-smtp@ietfa.amsl.com>; Tue, 18 Feb 2020 14:42:13 -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 929BA120838 for <ietf-smtp@ietf.org>; Tue, 18 Feb 2020 14:42:13 -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 1j4BZE-000Fbd-2y; Tue, 18 Feb 2020 17:42:12 -0500
Date: Tue, 18 Feb 2020 17:42:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
cc: ietf-smtp@ietf.org
Message-ID: <57E9B77701DCFE0B4E62B6FC@PSB>
In-Reply-To: <1fc6097c-18be-6249-8dc1-528eb0d786a6@dcrocker.net>
References: <CAOEezJTLEzpDUivS50xUvQtQbNNyJXVKk29Q=c4QRaxgRvTxBw@mail.gmail.com> <972BC556117E20BE16D62E29@PSB> <7c7bd9e2-ffc8-c307-898a-2c827c72695f@tana.it> <eb8a1c75-294b-6deb-3bb2-68ac723543d5@dcrocker.net> <A154AA91085706BE2792213F@PSB> <1fc6097c-18be-6249-8dc1-528eb0d786a6@dcrocker.net>
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/I8opc6ib4bRjGVDfYKxgC_He2U4>
Subject: Re: [ietf-smtp] Email standard revision
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: Tue, 18 Feb 2020 22:42:15 -0000


--On Tuesday, February 18, 2020 14:34 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

>...
> On 2/18/2020 11:12 AM, John C Klensin wrote:
>> The difficulty I see
>> is that the language in RFC 2026 seems very clear to me: "no
>> known technical omissions with respect to the requirements
>> placed upon it" without an explicit IESG waiver for Proposed
>> Standards;
> 
> Since the goal for the effort described in the text I offered
> is for full standard and not proposed, I have no idea what
> your reference, here, pertains to.

Please read the rest of that sentence, which read...

>  not even an exception procedure for Internet
> Standard. 

Unless someone is going to argue that the omission of any
specific mention of Internet Standard in that discussion means
that known technical omissions are ok in full standards, I think
that is a bar to adoption of documents as full standards that
contain such defects.

The rest of the paragraph may or may not be useful, but the
above should answer the question of what the reference pertains
to.

best,
  john