Found 2 records.

Status: Verified (1)

RFC 6532, "Internationalized Email Headers", February 2012

Errata ID: 3153
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Dave Thaler
Date Reported: 2012-03-09
Verifier Name: Peter Saint-Andre
Date Verified: 2012-03-21

Section 4 says:

The security impact of UTF-8 headers on email signature systems such
as Domain Keys Identified Mail (DKIM), S/MIME, and OpenPGP is
discussed in Section 14 of [RFC6530].

It should say:

The security impact of UTF-8 headers on email signature systems such
as Domain Keys Identified Mail (DKIM), S/MIME, and OpenPGP is
discussed in Section 13 of [RFC6530].

Notes:

Incorrect section number in reference.

Status: Reported (1)

RFC 6532, "Internationalized Email Headers", February 2012

Errata ID: 6036
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Alessandro Vesely
Date Reported: 2020-04-01

Throughout the document, when it says:

A section 3.2bis, "Syntax Extensions to RFC 2045", is missing.

It should say:

In particular, Section 5.1 of RFC 2045, "Syntax of the Content-Type Header Field", deserves an extension:

    token /= UTF8-non-ascii

similar to the extensions given to various text types given in Section 3.2.

Notes:

Various header fields are defined in terms of the grammar defined in RFC 2045. In particular, the missing extension of token was reported for Authentication-Results:
https://mailarchive.ietf.org/arch/msg/dmarc/g1U__axJW5I6OenEuwD48nwptzU

Report New Errata