Re: [art] not an erratum in RFC 6376, was Argh!!!! onto https://www.rfc-editor.org/errata.php

Steffen Nurpmeso <steffen@sdaoden.eu> Fri, 22 March 2024 00:55 UTC

Return-Path: <steffen@sdaoden.eu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E48C14F6F7 for <art@ietfa.amsl.com>; Thu, 21 Mar 2024 17:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sdaoden.eu header.b="c5zvL0in"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=sdaoden.eu header.b="zRra9QeM"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMIV3GdlLWDM for <art@ietfa.amsl.com>; Thu, 21 Mar 2024 17:55:34 -0700 (PDT)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC813C14F6BE for <art@ietf.org>; Thu, 21 Mar 2024 17:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1711068930; x=1711735596; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-date:resent-from:resent-to: resent-cc:in-reply-to:references:mime-version:content-type: content-transfer-encoding:message-id:mail-followup-to:openpgp: blahblahblah; bh=fMPsPNZGAlSqAFLYwGJ88p2X1+HJd9eDqKMiQpgE+Oo=; b=c5zvL0in8mmjjlVkQ6UfZnp2Nk68XTn3RUohoqkKhEKy87W3+Wy4SuwEZPqIUZFzIM/CDzVs C14VbJmUPV81ZrndwWIv24Y2+rJrB4QNXxgDH44XO/4pYo9Dd1JrcWsY+RIHybdU96iX+V9QcM +Qk2c/1NJdSgeqisHAiGOmDNVoH3DDZ3+pXW6ompE3JZ24JNqUVahXlxf5tVR72WFpIiRJpSe+ yrH/XGS7VXJzS8lIO1n3OuBJGj+vJ6uaOxCmtjFO67Ry0jTwjqM7nwRlo38tkNbYr/6NTpK6xk pBGLbWIzK9sKNYcs23Cx7TMuC5KacK3piaju/xGHVrmdJGYw==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1711068930; x=1711735596; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-date:resent-from:resent-to: resent-cc:in-reply-to:references:mime-version:content-type: content-transfer-encoding:message-id:mail-followup-to:openpgp: blahblahblah; bh=fMPsPNZGAlSqAFLYwGJ88p2X1+HJd9eDqKMiQpgE+Oo=; b=zRra9QeM/VlpNP3uLVbrlglPUx1J+BsOagmRiQyvhcmWt+YBH/MjT6sVHpYTLTWKSAl3SpLo a2sVb/CqfE1XCw==
Date: Fri, 22 Mar 2024 01:55:29 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: John C Klensin <john-ietf@jck.com>
Cc: art@ietf.org
Message-ID: <20240322005529.kE6MPkIL@steffen%sdaoden.eu>
In-Reply-To: <44387288FF0DB8BDCA823345@PSB>
References: <20240320231817.ACF1585D06DE@ary.qy> <20240321010142.FBZ7WuUT@steffen%sdaoden.eu> <44387288FF0DB8BDCA823345@PSB>
Mail-Followup-To: John C Klensin <john-ietf@jck.com>, art@ietf.org
User-Agent: s-nail v14.9.24-612-g7e3bfac540
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/nw_0Hmw_VRe-5UPoUB_ODR0EAuU>
Subject: Re: [art] not an erratum in RFC 6376, was Argh!!!! onto https://www.rfc-editor.org/errata.php
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2024 00:55:39 -0000

Hello Mr. Klensin.

John C Klensin wrote in
 <44387288FF0DB8BDCA823345@PSB>:
 |--On Thursday, March 21, 2024 02:01 +0100 Steffen Nurpmeso
 |<steffen@sdaoden.eu> wrote:
 |> John Levine wrote in
 |>  <20240320231817.ACF1585D06DE@ary.qy>:
 |>|It appears that Steffen Nurpmeso  <steffen@sdaoden.eu> said:
 ...
 |>|See, for example, the last paragraph on page 13 of RFC 5321,
 |> published \  |in 2008.
 ...
 |> That is about domain names...
 |
 |Apparently a typo on John's part.  Try the bottom of Page 14.
 |To save time, the paragraph, at the end of Section 2.3.8, says:
 |
 | "In addition, the appearance of "bare" "CR" or "LF"
 | characters in text (i.e., either without the other) has a
 | long history of causing problems in mail implementations
 | and applications that use the mail system as a tool. SMTP
 | client implementations MUST NOT transmit these characters
 | except when they are intended as line terminators and then
 | MUST, as indicated above, transmit them only as a <CRLF>
 | sequence." 
 |
 |To put both John's comment and the statement about a long
 |history in better perspective, exactly the same paragraph
 |appears at the end of Section 2.3.7 of RFC 2821 (April 2001).
 |While RFC 821 does not say things that explicitly, it makes it
 |quite clear that both commands and lines are terminated in CRLF
 |and only CRLF, so these things have been clear for at least 20
 |years and actually more like over 40.    If those documents, all
 |of which have page numbers, are outdated, we probably don't mean
 |the same thing when we talk about Internet email.  And, btw, the
 |same paragraph appears in draft-ietf-emailcore-rfc5321bis-27
 |(with page numbers in the text form).  If you find that
 |objectionable, this would be a good time to try to convince that
 |WG.

Thank you for all this time, Mr. Klensin.

 |If the "real life software" to which you refer violates those
 |rules about CRLF, interoperability difficulties are to be
 |predicted.  It seems to me that the issues you are having just
 |demonstrate that point because you are having what sounds like
 |interoperability problems.

No i am only deaf (not dumb as i just had written; but maybe also
that, .. of course) and did not listen to Wiete Venema of postfix,
John Levine and maybe more.  Claus Assmann.

No it was too late at night and i did take my thought (there is
only one possibility left -- of "LF is literal", "LF is to be
stripped", and "LF is whitespace") for granted; apparantly the
last worked out for weeks starting in the afternoon thereafter
because of the folding that continues with whitespace.
Wietse Venema of postfix said weeks ago something like "this is
used for DKIM signing since 2006".  I just did not listen.
(What was actually wrong with me testing "LF is to be stripped",
i do not know.  It now works, exactly so, that much is plain.)

Friendly greetings from Germany, Mr. Klensin.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)