[Ietf-dkim] [Technical Errata Reported] RFC6376 (7862)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 21 March 2024 01:10 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 65530C151061 for <ietf-dkim@ietfa.amsl.com>; Wed, 20 Mar 2024 18:10:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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
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 1SH3M700-DxV for <ietf-dkim@ietfa.amsl.com>; Wed, 20 Mar 2024 18:10:02 -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 A2C58C14F6BB for <ietf-dkim@ietf.org>; Wed, 20 Mar 2024 18:10:02 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 630EE1D51; Wed, 20 Mar 2024 18:10:02 -0700 (PDT)
To: dcrocker@bbiw.net, tony+dkimov@maillennium.att.com, msk@cloudmark.com, debcooley1@gmail.com, paul.wouters@aiven.io, laura@wordtothewise.com, tjw.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: steffen@sdaoden.eu, ietf-dkim@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240321011002.630EE1D51@rfcpa.amsl.com>
Date: Wed, 20 Mar 2024 18:10:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/qRglpjgVuWFHoHeDUvILmzmS_G0>
X-Mailman-Approved-At: Thu, 21 Mar 2024 08:25:30 -0700
Subject: [Ietf-dkim] [Technical Errata Reported] 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: Thu, 21 Mar 2024 01:10:07 -0000

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

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

--------------------------------------
Type: Technical
Reported by: Steffen Nurpmeso <steffen@sdaoden.eu>

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.)

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
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