RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (2)

RFC 2152, "UTF-7 A Mail-Safe Transformation Format of Unicode", May 1997

Source of RFC: Legacy
Area Assignment: app

Errata ID: 3982
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Occil
Date Reported: 2014-05-08
Verifier Name: Pete Resnick
Date Verified: 2014-06-04

Section Definitions says: 

               Character   ASCII & Unicode Value (decimal)

                 [...]       [...]

                  '           96

It should say:

               Character   ASCII & Unicode Value (decimal)

                 [...]       [...]

                  `           96

Notes:

The wrong character is used in the left column: code point 96 corresponds to "Grave Accent", not "Apostrophe".

Errata ID: 862
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Christian Aymon
Date Reported: 2006-05-16

In "UTF-7 Definition", it says:

Such characters
include control characters such as carriage returns and line
feeds; thus, a Unicode shifted sequence always terminates at the
of a line.

It should say:

Such characters
include control characters such as carriage returns and line
feeds; thus, a Unicode shifted sequence always terminates at the
end of a line.

Notes:

missing word

Status: Rejected (1)

RFC 2152, "UTF-7 A Mail-Safe Transformation Format of Unicode", May 1997

Source of RFC: Legacy
Area Assignment: app

Errata ID: 5475
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Peter Occil
Date Reported: 2018-08-22
Rejected by: Barry Leiba
Date Rejected: 2019-04-30

Section Discussion says: 

      Content-type: multipart/mixed; boundary=foo
      Content-Disposition: inline

      --foo
      Content-type: text/plain; charset=us-ascii

      Hi Mom
      --foo
      Content-type: text/plain; charset=UNICODE-2-0
      Content-transfer-encoding: base64

      Jjo=
      --foo
      Content-type: text/plain; charset=us-ascii

      !
      --foo--

It should say:

      Content-type: multipart/mixed; boundary=foo
      Content-Disposition: inline

      --foo
      Content-type: text/plain; charset=us-ascii

      Hi Mom
      --foo
      Content-type: text/plain; charset=UTF-7
      Content-transfer-encoding: base64

      Jjo=
      --foo
      Content-type: text/plain; charset=us-ascii

      !
      --foo--

Notes:

The charset name for this RFC is UTF-7, not UNICODE-2-0.
--VERIFIER NOTES--

This is an example that's specifically introduced with, "As an alternative to use of UTF-7," and quite intentionally uses a charset other than UTF-7.

Report New Errata



Advanced Search