From nobody Thu Feb 9 21:39:15 2017 Return-Path: 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 806B8129FC2 for ; Thu, 9 Feb 2017 21:39:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 uc7Q4LDQUHX6 for ; Thu, 9 Feb 2017 21:39:12 -0800 (PST) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B3FA129FB0 for ; Thu, 9 Feb 2017 21:39:12 -0800 (PST) Received: by mail-wr0-x236.google.com with SMTP id o16so99678727wra.1 for ; Thu, 09 Feb 2017 21:39:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=sElV2XatLpr5WFMXOpAVECExaCpuiR5lAa3TJjPGJTM=; b=gpXUwGgyHV7DklUuqld60f3O+oHADrvDQ1FK6UPIZJiKl7RCAWHzVid0m3ZzF48AKh 1DB1h8ki46Pnu4a3IguBYDxQZoDMR+x4BxKK8qrQneGssjtUcvwIDGL4r0tPod+ZmYcq AdkTEP/HZH7VPV9W4k8NpCNoU1qjlMTb/5C5aVLjxTfpfAyVPfxfsctOjC3xWvFf4SG4 qfvh6RhmISnw8vN+JT44G3hU02zJZYnwXHaAVKP+b604DayAV4ClOMNXgtV7HhqAkLWO oft7gk55rdgdQ4lFSahJ/7qAuAZSDQPziGVzzrmuD5W3xGTS9SS7RWAf1FMBR4eiSZMk rcyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=sElV2XatLpr5WFMXOpAVECExaCpuiR5lAa3TJjPGJTM=; b=HK5V/FnP0gODnLptMkfyxT1D49vAq4bJHtp4HeD38mGlZGnNQnykghIR5Ol7yh5eNI z6/0nJa++P46YcHoVXoKVcaDiEffvf1KCrFr5pcCwujBVTSV+mj2mkBQb7iJbVT42dpL hh5vXvPgZbWiSOwjgezMsKsx0C5qPReWG301758S6r+np1uOhT7NBF80mVhayMjHHqfJ nlV31LkDUZdJXqykjegJozEWHOdRpZ6NMfyQpvNlKTFrfTbW4BDpqQzJP/8nhXz8umW9 5tClCzZJzo5VttCV3K2ejdOmPzNwGJ/q1Lxh7ltZKotIN8H90joA7B03mJW5/QnyQZnz 2Ucg== X-Gm-Message-State: AMke39mftqsypM2Lk7hB9BI24GhgjF33/FsmbYUn/e7pcaqPfSdjk0YWpY/DxHYYwwpyzg== X-Received: by 10.223.141.229 with SMTP id o92mr6435473wrb.22.1486705150572; Thu, 09 Feb 2017 21:39:10 -0800 (PST) Received: from [192.168.1.79] (124.25.176.95.rev.sfr.net. [95.176.25.124]) by smtp.googlemail.com with ESMTPSA id b51sm861151wrd.39.2017.02.09.21.39.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 21:39:10 -0800 (PST) To: "json@ietf.org" From: Anders Rundgren Message-ID: <6aa19e14-f322-1c94-ebb3-f29d84c09737@gmail.com> Date: Fri, 10 Feb 2017 06:38:51 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [Json] ECMA reference in 7159bis X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 05:39:13 -0000 If there should be any reference to ECMA standards in 7159bis, it could (non-normatively maybe) point out that ECMA have defined a JavaScript <-> JSON serialization scheme which improves interoperability (assuming you want to be compatible with JavaScript), and also allows you to cryptographically hash JSON data only using "JSON.stringify()" for serialization. That this scheme is already implemented in Node.js and most browsers makes it close to a de-facto standard as well. Anders From nobody Sun Feb 19 17:09:54 2017 Return-Path: X-Original-To: json@ietf.org Delivered-To: json@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3491295FE; Sun, 19 Feb 2017 17:09:52 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.44.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148755299296.31224.8672277794235937204.idtracker@ietfa.amsl.com> Date: Sun, 19 Feb 2017 17:09:52 -0800 Archived-At: Cc: json@ietf.org Subject: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-03.txt X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.17 List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 01:09:53 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Javascript Object Notation Update of the IETF. Title : The JavaScript Object Notation (JSON) Data Interchange Format Author : Tim Bray Filename : draft-ietf-jsonbis-rfc7159bis-03.txt Pages : 14 Date : 2017-02-19 Abstract: 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-jsonbis-rfc7159bis-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jsonbis-rfc7159bis-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Feb 21 06:55:36 2017 Return-Path: X-Original-To: json@ietf.org Delivered-To: json@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C34412947E; Tue, 21 Feb 2017 06:55:30 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.45.0 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> Date: Tue, 21 Feb 2017 06:55:30 -0800 Archived-At: Cc: alexey.melnikov@isode.com, mamille2@cisco.com, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, json@ietf.org Subject: [Json] Last Call: (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.17 Reply-To: ietf@ietf.org List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 14:55:30 -0000 The IESG has received a request from the Javascript Object Notation Update WG (jsonbis) to consider the following document: - 'The JavaScript Object Notation (JSON) Data Interchange Format' as Internet Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2017-03-07. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Tue Feb 21 14:01:58 2017 Return-Path: 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 BC980129D27; Tue, 21 Feb 2017 14:01:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 1ybju2Fxr21p; Tue, 21 Feb 2017 14:01:56 -0800 (PST) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33F53129D22; Tue, 21 Feb 2017 14:01:56 -0800 (PST) Received: by mail-io0-x244.google.com with SMTP id m98so5420549iod.2; Tue, 21 Feb 2017 14:01:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r9jXsT3eq4b79zQO6MiuAStNnQaa9ubvBPrRZ2Q0BvI=; b=QL6UYRed5VUpD3Wkjz9P8fZP7pZ4iFFrbTgD8SnkNytXFm3w8KFySsaQKqoW/dsWkp f5GKmhAUVykY6M508Q9P2Yxja54vuM7Q3B7bHF058IajC/f8VKoWyiEl5EKCp1I8MPyp rPIZ/uKIbXnPt8jCzI06SAl0xvF1k4Yj5ptmTb9yKoMztN5GkUuLerR67Xga1dnp4xdb QITk7r5mZ7A9gfgvaHgYrqZVesQO1P+zSLfbIiGvTuwOuncMH0HB4uStYLSPhgfDY/Mi y+wAi5yS9cKw3fS38zpB1GMF59ByBnkm5AsYn7A2htXW0pPiHDJsJLWDtWCIOtP2XaYx NSlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r9jXsT3eq4b79zQO6MiuAStNnQaa9ubvBPrRZ2Q0BvI=; b=CSGbVvddWYbJOvEdJOmWvcJ7RzDQvvMw+s3OOe1c8s4L2coII8Eiw+ezcxjWilLLNO Dv1Lri24PUS6EqItj1qYl7z1CzRxVzc8nDjB3QJwDrxLNyItdrkbuNGdm61eTQMTf/zo yO5WxMAF+5jES7ktcU4OzKnXZd5a9REDMi38XTTpx8gp9RWSR7hdT0B4X8Y6nUsL5lNu yRTFoFvyCW8GitmlJdV5w4RozhEZjzzpK3yfJk7OEWUS1vwmD8MFuDz/wwIIu/JKqFa3 G65jvsRSNjGiOkr82WjVBafehFR+kEkYsEhmsJEPcBRA1T+KBjumxkQtsXJ+6Uzly6NV 4VBA== X-Gm-Message-State: AMke39lJkIoStGphogDCfYoJRj6DzBiw7MI9y0h8aI2532fDxwF28XIF/gW2nxKBSnAuB9oMBQXQ5X/FOk+K+g== X-Received: by 10.107.187.133 with SMTP id l127mr21185733iof.1.1487714515299; Tue, 21 Feb 2017 14:01:55 -0800 (PST) MIME-Version: 1.0 Sender: barryleiba.mailing.lists@gmail.com Received: by 10.107.55.134 with HTTP; Tue, 21 Feb 2017 14:01:54 -0800 (PST) In-Reply-To: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com> From: Barry Leiba Date: Tue, 21 Feb 2017 17:01:54 -0500 X-Google-Sender-Auth: 2ddsPmpdDPeB8hWiJFCNTmSjEeQ Message-ID: To: IETF discussion list Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "json@ietf.org" , Alexey Melnikov , draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, Matt Miller Subject: Re: [Json] Last Call: (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 22:01:58 -0000 The primary reasons for this document are (1) to advance the specification to Internet Standard and (2) to normatively align the IETF and ECMA specifications for JSON. I support both of those points, and think this document is ready for approval. Barry On Tue, Feb 21, 2017 at 9:55 AM, The IESG wrote: > > The IESG has received a request from the Javascript Object Notation > Update WG (jsonbis) to consider the following document: > - 'The JavaScript Object Notation (JSON) Data Interchange Format' > as Internet Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2017-03-07. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > 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. > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ > > IESG discussion can be tracked via > https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ballot/ > > > No IPR declarations have been submitted directly on this I-D. > > > >