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

John Levine <johnl@taugh.com> Wed, 20 March 2024 21:12 UTC

Return-Path: <johnl@iecc.com>
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 42DB3C14F614 for <art@ietfa.amsl.com>; Wed, 20 Mar 2024 14:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level:
X-Spam-Status: No, score=-1.858 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=iecc.com header.b="an7DX2B+"; dkim=pass (2048-bit key) header.d=taugh.com header.b="MzTeEsLp"
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 KEGwdZKh0-bt for <art@ietfa.amsl.com>; Wed, 20 Mar 2024 14:12:45 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B277C14F610 for <art@ietf.org>; Wed, 20 Mar 2024 14:12:45 -0700 (PDT)
Received: (qmail 58578 invoked from network); 20 Mar 2024 21:12:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e4d065fb514b.k2403; bh=JhIICOFh+Y4d8qrxm5h3nMToG1cKffAZBUPoBgB34v0=; b=an7DX2B+1G8ulidtydeVzjV0PBs9ZAauVbVFn2qjm7VyK5B5be6m2Hb4jrMQV0/IZZN31dn4WPuYgE8B435JJ/OBSpWgM6LnLtC5D/FxYBZ52hvf/maivY73ZvipbQSAZWTWC+HLQlMGToCEqCj+GCDfJaAkCNFZ18KdKO+uUo5ouXO9xbpcGRb+H/7DHRQieFx7r4whLzjThXz7g3qKpQwFhC5WlgCyTwErBKThlEh7QIML58duORpgVR4MPo5xl8rFQFxO/AhXqtGH9CRsvVTBaPTUMCUCQxy3BI6VW/ZP0yZn0P9X5koxTtmvkp9I6979gXm2d7fqawxQrtKjFQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e4d065fb514b.k2403; bh=JhIICOFh+Y4d8qrxm5h3nMToG1cKffAZBUPoBgB34v0=; b=MzTeEsLpigUh2iH3l8b+OGno/N8giq2FnT6cdX+ySZGG8XHjKe6S6+OU/Yoy56GXAFvvmv781tl1HPLpgAeRjJ+enyTa9v3WCn+kIWb7YrfpbhcmmDMbaoHsQYboWss7rs/i9uIDymbXR6M+oalEv18FtAxCXbpxlpFkBEsoi85Mx7g31uk1xukCRYKuVwWyIM2oQ0JJFS2xjjGIohcSdVxHrunQ0kL+KSo2VyQovCK3zpC3DuajvVartk2SxHS3jsTPH4RzApRMk4NejHCLamR5W9mvd8gxeKYLEwFn4ouu9jH81HJ+UCqbFwqTmyQKbKlGPIyBsxjhXz+IBfU5aQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 20 Mar 2024 21:12:42 -0000
Received: by ary.qy (Postfix, from userid 501) id 57E4085CEF48; Wed, 20 Mar 2024 17:12:42 -0400 (EDT)
Date: Wed, 20 Mar 2024 17:12:42 -0400
Message-Id: <20240320211242.57E4085CEF48@ary.qy>
From: John Levine <johnl@taugh.com>
To: art@ietf.org
In-Reply-To: <20240320202928.Lk0_Vk5n@steffenxsdaoden.eu>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/G1_W7N3aIE6SOL7GyJTnjkomsy8>
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: Wed, 20 Mar 2024 21:12:51 -0000

It appears that Steffen Nurpmeso  <steffen@sdaoden.eu> said:
> |No, it's correct as is.
> |
> |The first bullet on page 16 says to unfold all the lines, so the CR/LF
> |are gone before it does anything with WSP.
>
>But *that* unfolding refers to exactly CRLF alone, because only
>this combination is allowed by RFC 5322.
>I .. now you make me a bit unsure, but i really think i did test
>both, removing lone CR and LF, as well as treating them literally.

Since unpaired CR and LF are not valid in a 5322 message, if you see a
message that contains one of them, you can do whatever you want. My
preference would be to have the signature fail since there is no
reason to expect that the other end will do the same thing you do.

We quite deliberately did not speculate about what one might do with
a block of text that is sort of like a 5322 message but isn't one.

R's,
John