IETF Logo Mail Archive

[apps-discuss] [Technical Errata Reported] RFC6839 (4367)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 15 May 2015 13:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4031A6F20 for <apps-discuss@ietfa.amsl.com>; Fri, 15 May 2015 06:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUmiq1xbWhe5 for <apps-discuss@ietfa.amsl.com>; Fri, 15 May 2015 06:12:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 241F31A6F1D for <apps-discuss@ietf.org>; Fri, 15 May 2015 06:12:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8E76D180092; Fri, 15 May 2015 06:10:52 -0700 (PDT)
To: tony+sss@maillennium.att.com, Alexey.Melnikov@isode.com, barryleiba@computer.org, superuser@gmail.com, alexey.melnikov@isode.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150515131052.8E76D180092@rfc-editor.org>
Date: Fri, 15 May 2015 06:10:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/IcHcum9xOOZmYqv8Hh6aL1w9bZc>
Cc: yakov-ietf@shaftek.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] [Technical Errata Reported] RFC6839 (4367)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2015 13:12:46 -0000

The following errata report has been submitted for RFC6839,
"Additional Media Type Structured Syntax Suffixes".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6839&eid=4367

--------------------------------------
Type: Technical
Reported by: Yakov Shafranovich <yakov-ietf@shaftek.org>

Section: 3.1

Original Text
-------------
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]).

Corrected Text
--------------
Encoding considerations:  binary as per section 11 of RFC 7159

Notes
-----
RFC 7159, section 11 specifies that encoding for JSON is binary.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6839 (draft-ietf-appsawg-media-type-suffix-regs-08)
--------------------------------------
Title               : Additional Media Type Structured Syntax Suffixes
Publication Date    : January 2013
Author(s)           : T. Hansen, A. Melnikov
Category            : INFORMATIONAL
Source              : Applications Area Working Group
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email