Re: [yam] [Technical Errata Reported] RFC6152 (5646) {dkim-fail}

John C Klensin <john-ietf@jck.com> Mon, 04 March 2019 17:47 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: yam@ietfa.amsl.com
Delivered-To: yam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4942130DC9 for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 09:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 BQXb4Kt3YaeN for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 09:47:41 -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 5DA0F128B14 for <yam@ietf.org>; Mon, 4 Mar 2019 09:47:41 -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 1h0rgH-000LRd-OM; Mon, 04 Mar 2019 12:47:13 -0500
Date: Mon, 04 Mar 2019 12:47:08 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>, Dave Crocker <dcrocker@bbiw.net>
cc: RFC Errata System <rfc-editor@rfc-editor.org>, mrose17@gmail.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, tony@att.com, sm+ietf@elandsys.com, af13@protonmail.com, yam@ietf.org
Message-ID: <6A18BAD97E1F44F885EB7E59@PSB>
In-Reply-To: <01R3WD68QPDO00004L@mauve.mrochek.com>
References: <20190304153046.8443FB82AAA@rfc-editor.org> <8fda601c-8162-b9eb-3677-b8c732d22d58@bbiw.net> <01R3WD68QPDO00004L@mauve.mrochek.com>
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/yam/VaKN0upHPn7DTTQI8j1RZOdt4uc>
X-Mailman-Approved-At: Mon, 04 Mar 2019 11:07:07 -0800
Subject: Re: [yam] [Technical Errata Reported] RFC6152 (5646) {dkim-fail}
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yam/>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2019 17:47:44 -0000

+1.  As Ned suggests, we certainly could have written the
statement more clearly, but it is correct.

   john


--On Monday, March 4, 2019 09:25 -0800 Ned Freed
<ned.freed@mrochek.com> wrote:

> Agreed; the current text is correct and this should be
> rejected.
> 
> 				Ned
> 
>> Please reject.
> 
>> The existing text is correct. It might have helped for the
>> language to be a bit simpler, but it is correct.
> 
>> Reduced to its essence, the current language means:
> 
>>     The usual SMTP data-stuffing algorithm applies, so that
>>     some content does not prematurely terminate the transfer
>>     of content.
> 
>> d/
> 
> 
>> On 3/4/2019 7:30 AM, RFC Errata System wrote:
>> > The following errata report has been submitted for RFC6152,
>> > "SMTP Service Extension for 8-bit MIME Transport".
>> > 
>> > --------------------------------------
>> > You may review the report below and at:
>> > http://www.rfc-editor.org/errata/eid5646
>> > 
>> > --------------------------------------
>> > Type: Technical
>> > Reported by: HE Zhixiang <af13@protonmail.com>
>> > 
>> > Section: 3
>> > 
>> > Original Text
>> > -------------
>> > Naturally, the usual SMTP data-stuffing algorithm applies,
>> > so that a content that contains the five-character sequence
>> > of <CR> <LF> <DOT> <CR> <LF>
>> > or a content that begins with the three-character sequence
>> > of <DOT> <CR> <LF>
>> > does not prematurely terminate the transfer of the content.
>> > 
>> > Corrected Text
>> > --------------
>> > Naturally, the usual SMTP data-stuffing algorithm applies,
>> > so that a content that contains the five-character sequence
>> > of <CR> <LF> <DOT> <CR> <LF>
>> > or a content that begins with the three-character sequence
>> > of <DOT> <CR> <LF>
>> > would prematurely terminate the transfer of the content.
>> > 
>> > Notes
>> > -----
>> > RFC 5321, section 4.5.2:
>> > Without some provision for data transparency, the character
>> > sequence "<CRLF>.<CRLF>" ends the mail text and cannot be
>> > sent by the user.
>> > 
>> > Instructions:
>> > -------------
>> > This erratum is currently posted as "Reported". If
>> > necessary, please use "Reply All" to discuss whether it
>> > should be verified or rejected. When a decision is reached,
>> > the verifying party can log in to change the status and
>> > edit the report, if necessary.
>> > 
>> > --------------------------------------
>> > RFC6152 (draft-ietf-yam-rfc1652bis-03)
>> > --------------------------------------
>> > Title               : SMTP Service Extension for 8-bit MIME
>> > Transport Publication Date    : March 2011
>> > Author(s)           : J. Klensin, N. Freed, M. Rose, D.
>> > Crocker, Ed. Category            : INTERNET STANDARD
>> > Source              : Yet Another Mail
>> > Area                : Applications
>> > Stream              : IETF
>> > Verifying Party     : IESG
>> > 
> 
> 
>> --
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net