IETF Logo Mail Archive

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

S Moonesamy <sm+ietf@elandsys.com> Mon, 04 March 2019 21:26 UTC

Return-Path: <sm@elandsys.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 E8DC6130EA8 for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 13:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=rEc8zzbx; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=mPybAX8X
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 RXGYjFP4hw27 for <yam@ietfa.amsl.com>; Mon, 4 Mar 2019 13:26:18 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 934B612008A for <yam@ietf.org>; Mon, 4 Mar 2019 13:26:18 -0800 (PST)
Received: from sm-THINK.elandsys.com (50-39-226-71.bvtn.or.frontiernet.net [50.39.226.71]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x24LPrEN021490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Mar 2019 13:25:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1551734764; x=1551821164; bh=KFnbhgjxkMHHLMky7Tw7eJxu03NakDFsOh08EuYhq7w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rEc8zzbxIKYvRu+Av2gSS1ffkGFuN1SgpZySlPeqHipGTAXsok6qPZ4O8/lRLbyT8 VgSbK9Gswj28pZO0c22CHtqMfosxaSJwkobpEoJ4xjpHjfhydrh2YXmwRYPxBVg9gi /SvtlIBJrvMtzBThVkcRkGU1H3s22jp49GVgCIiM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1551734764; x=1551821164; i=@elandsys.com; bh=KFnbhgjxkMHHLMky7Tw7eJxu03NakDFsOh08EuYhq7w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mPybAX8Xm2RvOvLs5C1Fw07zDFdDneh6ipvQ9zp1H9upKYp9XHZ+6wmsJoey0wGy5 ckyaZrCLYl+llZr/PE8CilomrPmQAcYlEIrMaglZZkKfg06B3XfNRUNA+Ql9IWbH67 rIngb4+gkntzazwGzVz1JVzXDWfVde2icTvj6edU=
Message-Id: <6.2.5.6.2.20190304132342.0952fed0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Mar 2019 13:24:59 -0800
To: Dave Crocker <dcrocker@bbiw.net>, 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
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: af13@protonmail.com, yam@ietf.org
In-Reply-To: <8fda601c-8162-b9eb-3677-b8c732d22d58@bbiw.net>
References: <20190304153046.8443FB82AAA@rfc-editor.org> <8fda601c-8162-b9eb-3677-b8c732d22d58@bbiw.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yam/oSlTim0cYaZiEdL17gm3cT_PSxA>
X-Mailman-Approved-At: Mon, 04 Mar 2019 13:32:49 -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 21:26:20 -0000

Hi Dave,
At 08:32 AM 3/4/2019, Dave Crocker wrote:
>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.

Agreed.

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email