RFC 6376, "DomainKeys Identified Mail (DKIM) Signatures", September 2011

Note: This RFC has been updated by RFC 8301, RFC 8463, RFC 8553, RFC 8616

Errata ID: 7862
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Steffen Nurpmeso
Date Reported: 2024-03-21
Rejected by: Murray Kucherawy
Date Rejected: 2024-03-22

Section 3.4.2 says:

[..]

It should say:

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

Report New Errata