Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 6068, "The 'mailto' URI Scheme", October 2010

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

---

Errata ID: 8588
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Daniel Kahn Gillmor
Date Reported: 2025-09-30
Held for Document Update by: RFC Editor
Date Held: 2025-10-22

Section 7 says:

Some header fields are inherently unsafe to include in a message generated from
a URI.  For details, please see Section 3.

It should say:

Some header fields are inherently unsafe to include in a message generated from 
a URI.  For details, please see Sections 3 and 4.

Notes:

Section 3 is "Semantics and Operations" which does indeed discuss some unsafe header fields.

But Section 4 is titled "Unsafe Header Fields" and deserves to also be referenced from section 7, Security Considerations.

Report New Errata