[Json] RFC 8259 on The JavaScript Object Notation (JSON) Data Interchange Format

rfc-editor@rfc-editor.org Wed, 13 December 2017 19:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95282128B38; Wed, 13 Dec 2017 11:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lCYbi8pN4kNo; Wed, 13 Dec 2017 11:16:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 153FD1275F4; Wed, 13 Dec 2017 11:16:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 299BCB813D2; Wed, 13 Dec 2017 11:16:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, json@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20171213191609.299BCB813D2@rfc-editor.org>
Date: Wed, 13 Dec 2017 11:16:09 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/viZkqDPWV6p-mycPaNEoilqUmRk>
Subject: [Json] =?utf-8?q?RFC_8259_on_The_JavaScript_Object_Notation_=28JS?= =?utf-8?q?ON=29_Data_Interchange_Format?=
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 19:16:37 -0000

A new Request for Comments is now available in online RFC libraries.
   
        RFC 8259

        Title:      The JavaScript Object Notation (JSON) 
                    Data Interchange Format 
        Author:     T. Bray, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2017
        Mailbox:    tbray@textuality.com
        Pages:      16
        Characters: 28360
        Obsoletes:  RFC 7159

        I-D Tag:    draft-ietf-jsonbis-rfc7159bis-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8259

        DOI:        10.17487/RFC8259

JavaScript Object Notation (JSON) is a lightweight, text-based,
language-independent data interchange format.  It was derived from
the ECMAScript Programming Language Standard.  JSON defines a small
set of formatting rules for the portable representation of structured
data.

This document removes inconsistencies with other specifications of
JSON, repairs specification errors, and offers experience-based
interoperability guidance.

This document is a product of the Javascript Object Notation Update Working Group of the IETF.

This is now an Internet Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC