Re: [yam] [Technical Errata Reported] RFC6152 (5646)

Dave Crocker <dcrocker@bbiw.net> Mon, 04 March 2019 16:34 UTC

Return-Path: <dcrocker@bbiw.net>
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 2FB7A1228B7 for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 08:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net
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 SEJzGwMwFpA8 for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 08:34:19 -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 339D812D84C for <yam@ietf.org>; Mon, 4 Mar 2019 08:34:19 -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 x24GY5a6029963 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 4 Mar 2019 08:34:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1551717246; bh=v/5IQRTQ+e/ZloJGjGAD6x4ORo4UsK6LOxuKRTO3PnY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=a5D56jY2zZalUTxUUcGzEsPdA9dUrR28tjYaGZRn97TpgaLInsnrzA6/YtmteITw+ ww/eaBV2FtPh3Im0/7mt/6hXftk/dEnleUmvWB/UmKkU15pWjqNKAccOmjsUb5fmcB dMEeTy/4VjLfAqEV8qEPZPgRZMGUAsuSAUQl/mR8=
To: RFC Errata System <rfc-editor@rfc-editor.org>, john+ietf@jck.com, ned.freed@mrochek.com, mrose17@gmail.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, tony@att.com, sm+ietf@elandsys.com
Cc: af13@protonmail.com, yam@ietf.org
References: <20190304153046.8443FB82AAA@rfc-editor.org>
From: Dave Crocker <dcrocker@bbiw.net>
Message-ID: <8fda601c-8162-b9eb-3677-b8c732d22d58@bbiw.net>
Date: Mon, 04 Mar 2019 08:32:26 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <20190304153046.8443FB82AAA@rfc-editor.org>
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/yam/BIspciJXjevH5mdmLlRtNpCn8L0>
X-Mailman-Approved-At: Mon, 04 Mar 2019 11:07:08 -0800
Subject: Re: [yam] [Technical Errata Reported] RFC6152 (5646)
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 16:34:21 -0000

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