[Ietf-dkim] [Errata Rejected] RFC6376 (7862)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 March 2024 02:39 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAAEC14F6F7; Thu, 21 Mar 2024 19:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, 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=unavailable autolearn_force=no
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 nWC6PziafE1T; Thu, 21 Mar 2024 19:39:22 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (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 CF6DEC14F69D; Thu, 21 Mar 2024 19:39:17 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 99368120A59; Thu, 21 Mar 2024 19:39:17 -0700 (PDT)
To: steffen@sdaoden.eu, dcrocker@bbiw.net, tony+dkimov@maillennium.att.com, msk@cloudmark.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: superuser@gmail.com, iesg@ietf.org, ietf-dkim@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240322023917.99368120A59@rfcpa.amsl.com>
Date: Thu, 21 Mar 2024 19:39:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/Ux2YufFRmXMW6b131ll-auQv07s>
Subject: [Ietf-dkim] [Errata Rejected] RFC6376 (7862)
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2024 02:39:27 -0000

The following errata report has been rejected for RFC6376,
"DomainKeys Identified Mail (DKIM) Signatures".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7862

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Steffen Nurpmeso <steffen@sdaoden.eu>
Date Reported: 2024-03-21
Rejected by: Murray Kucherawy (IESG)

Section: 3.4.2

Original Text
-------------
[..]

Corrected Text
--------------
[insert after item 2]

Due to de-facto implementation practice, the term WSP of the following two items, 
as well as in the part that refers to after the separating colon (the field body) 
in the third, has to be interpreted differently, and must include all US-ASCII 
whitespace characters, namely %d9 (HT), %d10 (LF), %d11 (VT), %d12 (FF), %d12 
(CR) as well as %d32 (SP) [?](the isspace(3) set of characters in the ISO C "C" 
locale)[/?]

Notes
-----
As written.
The behaviour *could* originate in a partial misunderstanding of the Sendmail milter protocol, which is often used to implement DKIM; this protocol *may* send header continuation lines separated by lone LF bytes, instead of CRLF.
(Thanks to Claus Assmann of esmtp.org for this in-between-the-lines reading.)
 --VERIFIER NOTES-- 
   Withdrawn by submitter.

--------------------------------------
RFC6376 (draft-ietf-dkim-rfc4871bis-15)
--------------------------------------
Title               : DomainKeys Identified Mail (DKIM) Signatures
Publication Date    : September 2011
Author(s)           : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.
Category            : DRAFT STANDARD
Source              : Domain Keys Identified Mail SEC
Stream              : IETF
Verifying Party     : IESG