RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Rejected (1)

RFC 6839, "Additional Media Type Structured Syntax Suffixes", January 2013

Note: This RFC has been updated by RFC 7303

Source of RFC: appsawg (app)

Errata ID: 4367
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Yakov Shafranovich
Date Reported: 2015-05-15
Rejected by: Barry Leiba
Date Rejected: 2015-05-28

Section 3.1 says: 

Encoding considerations:

      Per [RFC4627], JSON is allowed to be represented using UTF-8,
      UTF-16, or UTF-32.  When JSON is written in UTF-8, JSON is 8bit
      compatible ([RFC2045]).  When JSON is written in UTF-16 or UTF-32,
      JSON is binary ([RFC2045]).

It should say:

Encoding considerations:  binary as per section 11 of RFC 7159

Notes:

RFC 7159, section 11 specifies that encoding for JSON is binary.
--VERIFIER NOTES--
This does not qualify as an erratum, but do see the mailing list discussion that starts here:
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg14321.html

Report New Errata



Advanced Search