From nobody Sun Mar 1 03:17:53 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 219AA1A88A0; Sun, 1 Mar 2015 03:17:49 -0800 (PST) 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 gNTvkAMcPgKM; Sun, 1 Mar 2015 03:17:47 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id CFA431A889F; Sun, 1 Mar 2015 03:17:47 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 5A823181D1B; Sun, 1 Mar 2015 03:17:08 -0800 (PST) To: tg@mirbsd.org, tbray@textuality.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20150301111708.5A823181D1B@rfc-editor.org> Date: Sun, 1 Mar 2015 03:17:08 -0800 (PST) Archived-At: Cc: rfc-editor@rfc-editor.org, barryleiba@computer.org, iesg@ietf.org, json@ietf.org Subject: [Json] [Errata Rejected] RFC7159 (4220) X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Sun, 01 Mar 2015 11:17:49 -0000 The following errata report has been rejected for RFC7159, "The JavaScript Object Notation (JSON) Data Interchange Format". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4220 -------------------------------------- Status: Rejected Type: Technical Reported by: mirabilos Date Reported: 2015-01-05 Rejected by: Barry Leiba (IESG) Section: 7 Original Text ------------- […] All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F). […] unescaped = %x20-21 / %x23-5B / %x5D-10FFFF Corrected Text -------------- […] All Unicode characters may be placed within the quotation marks, except for the characters that must be escaped: quotation mark, reverse solidus, the control characters (U+0000 through U+001F), and codepoints beyond the BMP (U-00010000 through U-0010FFFF). […] unescaped = %x20-21 / %x23-5B / %x5D-FFFF Notes ----- ECMA-262 states that "ECMAScript source text is assumed to be a sequence of 16-bit code units", and everything must be converted to UTF-16 first. This stems from the fact that Java™, like Win32, used UCS-2, which only later got extended to allow UTF-16. This means that SMP codepoints must always be escaped into their twelve-character form. This is also an interoperability issue: implementations may wish to parse (or generate) JSON by using a wchar_t data type (in C) which, depending on the platform, may be only 16 bits wide. ECMAscript allows for this. --VERIFIER NOTES-- This is reporting a disagreement with a decision the working group made in the development of the document, and is not reporting an erratum. -------------------------------------- RFC7159 (draft-ietf-json-rfc4627bis-rfc7159bis) -------------------------------------- Title : The JavaScript Object Notation (JSON) Data Interchange Format Publication Date : March 2014 Author(s) : T. Bray, Ed. Category : PROPOSED STANDARD Source : JavaScript Object Notation Area : Applications Stream : IETF Verifying Party : IESG From nobody Sun Mar 1 03:20:00 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0DB71A88A0; Sun, 1 Mar 2015 03:19:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.912 X-Spam-Level: X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zRpB1j991EN7; Sun, 1 Mar 2015 03:19:54 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 835FF1A889F; Sun, 1 Mar 2015 03:19:54 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 0C0A5181D1B; Sun, 1 Mar 2015 03:19:15 -0800 (PST) To: federico_dopino@fibertel.com.ar, tbray@textuality.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20150301111915.0C0A5181D1B@rfc-editor.org> Date: Sun, 1 Mar 2015 03:19:15 -0800 (PST) Archived-At: Cc: rfc-editor@rfc-editor.org, barryleiba@computer.org, iesg@ietf.org, json@ietf.org Subject: [Json] [Errata Verified] RFC7159 (4264) X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Sun, 01 Mar 2015 11:19:56 -0000 The following errata report has been verified for RFC7159, "The JavaScript Object Notation (JSON) Data Interchange Format". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4264 -------------------------------------- Status: Verified Type: Editorial Reported by: Federico do Pino Date Reported: 2015-02-05 Verified by: Barry Leiba (IESG) Section: 15.2 Original Text ------------- [Err3607] RFC Errata, Errata ID 3607, RFC 3607, . [Err607] RFC Errata, Errata ID 607, RFC 607, . Corrected Text -------------- [Err3607] RFC Errata, Errata ID 3607, for RFC 4627, . [Err607] RFC Errata, Errata ID 607, for RFC 4627, . Notes ----- The references point to RFCs by the same numbers as the errata IDs, while the intention was to refer to errata (by the same IDs) reported for the previous JSON RFC, namely RFC 4627. (RFCs 607 and 3607 are completely unrelated.) The links may also be replaced with direct links to the errata pages, for instance http://www.rfc-editor.org/errata_search.php?eid=607 and http://www.rfc-editor.org/errata_search.php?eid=3607 -------------------------------------- RFC7159 (draft-ietf-json-rfc4627bis-rfc7159bis) -------------------------------------- Title : The JavaScript Object Notation (JSON) Data Interchange Format Publication Date : March 2014 Author(s) : T. Bray, Ed. Category : PROPOSED STANDARD Source : JavaScript Object Notation Area : Applications Stream : IETF Verifying Party : IESG From nobody Wed Mar 11 13:02:53 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1D21A6FEF for ; Wed, 11 Mar 2015 13:02:52 -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 sB93w4XyKM5q for ; Wed, 11 Mar 2015 13:02:51 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2521A1AB9 for ; Wed, 11 Mar 2015 13:02:51 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 60311180207; Wed, 11 Mar 2015 13:02:02 -0700 (PDT) To: tbray@textuality.com, barryleiba@computer.org, presnick@qti.qualcomm.com, mamille2@cisco.com, paul.hoffman@vpnc.org X-PHP-Originating-Script: 6000:errata_mail_lib.php From: RFC Errata System Message-Id: <20150311200202.60311180207@rfc-editor.org> Date: Wed, 11 Mar 2015 13:02:02 -0700 (PDT) Archived-At: Cc: rfc-editor@rfc-editor.org, mike@saxonica.com, json@ietf.org Subject: [Json] [Technical Errata Reported] RFC7159 (4298) X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Wed, 11 Mar 2015 20:02:52 -0000 The following errata report has been submitted for RFC7159, "The JavaScript Object Notation (JSON) Data Interchange Format". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4298 -------------------------------------- Type: Technical Reported by: Michael Kay Section: 7 Strings Original Text ------------- 4HEXDIG Corrected Text -------------- Something along the lines 4hexdig hexdig = 0..9 A..F a..f Notes ----- The prose states that within a six-character escape sequence starting \u, the hex digits can be either upper or lower case. But the grammar only allows upper case, because it uses the symbol HEXDIG which is defined in RFC 5234 to include upper case A..F only. There is thus an inconsistency beween the grammar and the prose, and although most readers are likely to know which to believe, the spec is formally ambiguous on this point. 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. -------------------------------------- RFC7159 (draft-ietf-json-rfc4627bis-rfc7159bis) -------------------------------------- Title : The JavaScript Object Notation (JSON) Data Interchange Format Publication Date : March 2014 Author(s) : T. Bray, Ed. Category : PROPOSED STANDARD Source : JavaScript Object Notation Area : Applications Stream : IETF Verifying Party : IESG From nobody Wed Mar 11 13:45:59 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49011A8713; Wed, 11 Mar 2015 13:45:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.912 X-Spam-Level: X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZfFTO-_I7L1z; Wed, 11 Mar 2015 13:45:54 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 650A71A870A; Wed, 11 Mar 2015 13:45:54 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 9D4FD180207; Wed, 11 Mar 2015 13:45:05 -0700 (PDT) To: mike@saxonica.com, tbray@textuality.com X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20150311204505.9D4FD180207@rfc-editor.org> Date: Wed, 11 Mar 2015 13:45:05 -0700 (PDT) Archived-At: Cc: rfc-editor@rfc-editor.org, barryleiba@computer.org, iesg@ietf.org, json@ietf.org Subject: [Json] [Errata Rejected] RFC7159 (4298) X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Wed, 11 Mar 2015 20:45:55 -0000 The following errata report has been rejected for RFC7159, "The JavaScript Object Notation (JSON) Data Interchange Format". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4298 -------------------------------------- Status: Rejected Type: Technical Reported by: Michael Kay Date Reported: 2015-03-11 Rejected by: Barry Leiba (IESG) Section: 7 Strings Original Text ------------- 4HEXDIG Corrected Text -------------- Something along the lines 4hexdig hexdig = 0..9 A..F a..f Notes ----- The prose states that within a six-character escape sequence starting \u, the hex digits can be either upper or lower case. But the grammar only allows upper case, because it uses the symbol HEXDIG which is defined in RFC 5234 to include upper case A..F only. There is thus an inconsistency beween the grammar and the prose, and although most readers are likely to know which to believe, the spec is formally ambiguous on this point. --VERIFIER NOTES-- The reporter doesn't understand RFC 5234. Look in Section 2.3 (Terminal Values), and see this: > NOTE: > > ABNF strings are case insensitive and the character set for these > strings is US-ASCII. There is no inconsistency, and the text as written allows both upper and lower case for the hex digits. -------------------------------------- RFC7159 (draft-ietf-json-rfc4627bis-rfc7159bis) -------------------------------------- Title : The JavaScript Object Notation (JSON) Data Interchange Format Publication Date : March 2014 Author(s) : T. Bray, Ed. Category : PROPOSED STANDARD Source : JavaScript Object Notation Area : Applications Stream : IETF Verifying Party : IESG From nobody Sun Mar 22 09:34:19 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61CAF1AC3E9; Sun, 22 Mar 2015 09:34:17 -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 zBC8RkW7bIb3; Sun, 22 Mar 2015 09:34:16 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id E73031AC3DC; Sun, 22 Mar 2015 09:34:14 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id D2EF1180459; Sun, 22 Mar 2015 09:32:52 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 6000:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20150322163252.D2EF1180459@rfc-editor.org> Date: Sun, 22 Mar 2015 09:32:52 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, json@ietf.org, rfc-editor@rfc-editor.org Subject: [Json] RFC 7493 on The I-JSON Message Format X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Sun, 22 Mar 2015 16:34:17 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7493 Title: The I-JSON Message Format Author: T. Bray, Ed. Status: Standards Track Stream: IETF Date: March 2015 Mailbox: tbray@textuality.com Pages: 6 Characters: 12849 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-json-i-json-06.txt URL: https://www.rfc-editor.org/info/rfc7493 I-JSON (short for "Internet JSON") is a restricted profile of JSON designed to maximize interoperability and increase confidence that software can process it successfully with predictable results. This document is a product of the JavaScript Object Notation Working Group of the IETF. This is now a Proposed 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/rfc.html 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 From nobody Mon Mar 23 09:35:14 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 017F61ACD26 for ; Mon, 23 Mar 2015 09:35:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.011 X-Spam-Level: X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 SNjWoTeMqmh3 for ; Mon, 23 Mar 2015 09:35:11 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679E11ACC8C for ; Mon, 23 Mar 2015 09:35:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1427128511; x=1458664511; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=nFlTsboFcDxJKphe2NlaT8xs0XoJqlqS1mXXNbVfso0=; b=kotSxuq1y5kN/ssfFiUy3IqFTtLabVJwUKtJp6o2NnNBOM6/oK/4HwTy Fug7m/xpTQMnub0Fib/qKFeVlVzkM/f88NZ61/jVOvJPNpfHOo9AwWHDf VvdTv+EIsDxaTclupkdCOFMOuj/ZZWGoJohX5aBM63pKkicylvQYMEKVA E=; X-IronPort-AV: E=McAfee;i="5600,1067,7748"; a="109809626" Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine01.qualcomm.com with ESMTP; 23 Mar 2015 09:35:10 -0700 X-IronPort-AV: E=Sophos;i="5.11,452,1422950400"; d="scan'208";a="32068928" Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Mar 2015 09:35:11 -0700 Received: from dhcp-88e2.meeting.ietf.org (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Mon, 23 Mar 2015 09:35:09 -0700 Message-ID: <551040BC.2080409@qti.qualcomm.com> Date: Mon, 23 Mar 2015 11:35:08 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32) Archived-At: Subject: [Json] Closing of the group X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Mar 2015 16:35:13 -0000 Congrats on getting all of the work items completed. I have sent in the request to the secretariat to conclude the WG. The mailing list will remain open for future discussion. Thanks, pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Mon Mar 23 11:32:34 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 145B41AD0B2 for ; Mon, 23 Mar 2015 11:32:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 jFQL_4N5pNCl for ; Mon, 23 Mar 2015 11:32:31 -0700 (PDT) Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) (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 347AB1AD082 for ; Mon, 23 Mar 2015 11:32:31 -0700 (PDT) Received: by labto5 with SMTP id to5so33647007lab.0 for ; Mon, 23 Mar 2015 11:32:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vZ6aQkiDwpiXHUe+itEbUpmKzOSsIoll5O79WINXdJ8=; b=ZM1I8x/2SXDlCjZ9DBV/eDNQxKEbL3c5giOqBFnMVdRDpeik5JMPWqGTlsOm8E9ojU MrAroechBPOPuJFrYh3UJIrvEL7/UPAp3iin35b7zHyEHLQgnL4LmKr/TO//dRbyxMaI 27Z37VMznO/4k8RJlpxjSWVvA6OZPBUEHF40XYgKTiUDxliyglYsgUzcWgVPp3c5pJkg 6r+evLOZh0joq8gGtybNpTCmSyx2oeEGGsaM79MMIpyYGt1GxkQZX1HkpFSILfi1kqjS 6kvum64G2T33tG6fTv89d5KtZKNfnAjG3pPIznC/MP7dIlcBxFzqzBINFrrbAeny79Ht aSnw== X-Gm-Message-State: ALoCoQnhV2Nv9svCO8XFl4sd/hEL+VHLjWp2N0QR9oAE15Bw8ZVHIeehbHaKgVFHKoOk7ihYj0/a MIME-Version: 1.0 X-Received: by 10.152.204.101 with SMTP id kx5mr487663lac.18.1427135549728; Mon, 23 Mar 2015 11:32:29 -0700 (PDT) Received: by 10.114.3.242 with HTTP; Mon, 23 Mar 2015 11:32:29 -0700 (PDT) X-Originating-IP: [118.92.158.243] Received: by 10.114.3.242 with HTTP; Mon, 23 Mar 2015 11:32:29 -0700 (PDT) In-Reply-To: <551040BC.2080409@qti.qualcomm.com> References: <551040BC.2080409@qti.qualcomm.com> Date: Tue, 24 Mar 2015 07:32:29 +1300 Message-ID: From: Tim Bray To: Pete Resnick Content-Type: multipart/alternative; boundary=001a11342f5a7cff3c0511f8e31e Archived-At: Cc: json@ietf.org Subject: Re: [Json] Closing of the group X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Mar 2015 18:32:33 -0000 --001a11342f5a7cff3c0511f8e31e Content-Type: text/plain; charset=UTF-8 Thanks everyone. On Mar 24, 2015 5:35 AM, "Pete Resnick" wrote: > Congrats on getting all of the work items completed. I have sent in the > request to the secretariat to conclude the WG. The mailing list will remain > open for future discussion. > > Thanks, > > pr > > -- > Pete Resnick > Qualcomm Technologies, Inc. - +1 (858)651-4478 > > _______________________________________________ > json mailing list > json@ietf.org > https://www.ietf.org/mailman/listinfo/json > --001a11342f5a7cff3c0511f8e31e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks everyone.

On Mar 24, 2015 5:35 AM, "Pete Resnick"= ; <presnick@qti.qualcomm.co= m> wrote:
Con= grats on getting all of the work items completed. I have sent in the reques= t to the secretariat to conclude the WG. The mailing list will remain open = for future discussion.

Thanks,

pr

--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

_______________________________________________
json mailing list
json@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/json
--001a11342f5a7cff3c0511f8e31e-- From nobody Mon Mar 23 13:36:58 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB321A1A47; Mon, 23 Mar 2015 13:36:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 o4ACcLTsdhVo; Mon, 23 Mar 2015 13:36:54 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA25A1A0B00; Mon, 23 Mar 2015 13:36:54 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: "IETF Announcement List" X-Test-IDTracker: no X-IETF-IDTracker: 5.12.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150323203654.25905.16420.idtracker@ietfa.amsl.com> Date: Mon, 23 Mar 2015 13:36:54 -0700 Archived-At: Cc: mamille2@cisco.com, paul.hoffman@vpnc.org, json@ietf.org Subject: [Json] WG Action: Conclusion of JavaScript Object Notation (json) X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Mar 2015 20:36:55 -0000 The JavaScript Object Notation (json) working group in the Applications Area has completed its work items and is now closed. The mailing list will remain open for future discussions. The IESG contact persons are Barry Leiba and Pete Resnick. From nobody Mon Mar 23 13:56:48 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 341DE1A1A51 for ; Mon, 23 Mar 2015 13:56:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.347 X-Spam-Level: X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 g_PBwXxuQZjJ for ; Mon, 23 Mar 2015 13:56:45 -0700 (PDT) Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE0631B2A47 for ; Mon, 23 Mar 2015 13:56:38 -0700 (PDT) Received: from dhcp-b493.meeting.ietf.org (dhcp-b493.meeting.ietf.org [31.133.180.147]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t2NKubs7035024 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Mar 2015 13:56:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) From: Paul Hoffman Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <1A364644-D2A5-4CAE-A7EA-12A2059B563D@vpnc.org> Date: Mon, 23 Mar 2015 15:56:37 -0500 To: IETF JSON WG Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Archived-At: Subject: [Json] Thank you, and the list will remain open X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Mar 2015 20:56:46 -0000 Thank you to the WG participants: we were able to do good work in a = reasonably short period of time. There are other JSON-related lists; this one should probably only be for = IETF use of JSON. It certainly not the right place to discuss changes to = the Ecma JSON spec. --Paul Hoffman, no longer having a hat= From nobody Mon Mar 23 14:45:52 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2008C1B2AB1 for ; Mon, 23 Mar 2015 14:45:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.044 X-Spam-Level: X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 n25370gUi3NA for ; Mon, 23 Mar 2015 14:45:50 -0700 (PDT) Received: from homiemail-a36.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB351B2AAD for ; Mon, 23 Mar 2015 14:45:50 -0700 (PDT) Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id 0C93D77805F for ; Mon, 23 Mar 2015 14:45:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=zcNUNgXB6JcNlMgWyKm0 EqV+0F0=; b=Tgqls4MsI/TrzhtXdis0z73JYNG+dEIjyZrQGXf2gz0T5FYFhaM0 zPztDCCB0hTb5YcwzOyGbU7px3solY7vg4e9yzp9RFj01wKuAcl8f0ExjntU7T1W D2Jd3ybJS/vE97d2hXgwn3zNAY4204IEShJccFzv6HC3nVedMDH1mb8= Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPSA id ED26F77805B for ; Mon, 23 Mar 2015 14:45:49 -0700 (PDT) Received: by ignm3 with SMTP id m3so40862440ign.0 for ; Mon, 23 Mar 2015 14:45:49 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.35.195 with SMTP id k3mr13989838igj.11.1427147149570; Mon, 23 Mar 2015 14:45:49 -0700 (PDT) Received: by 10.64.130.66 with HTTP; Mon, 23 Mar 2015 14:45:49 -0700 (PDT) In-Reply-To: References: <551040BC.2080409@qti.qualcomm.com> Date: Mon, 23 Mar 2015 16:45:49 -0500 Message-ID: From: Nico Williams To: Tim Bray Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Pete Resnick , "json@ietf.org" Subject: Re: [Json] Closing of the group X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Mar 2015 21:45:51 -0000 On Mon, Mar 23, 2015 at 1:32 PM, Tim Bray wrote: > Thanks everyone. Seconded! From nobody Mon Mar 23 17:47:44 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B983B1AC39D for ; Mon, 23 Mar 2015 17:47:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.726 X-Spam-Level: ** X-Spam-Status: No, score=2.726 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_03_06=1.592, IP_NOT_FRIENDLY=0.334] autolearn=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 yjhxSkRgLxHv for ; Mon, 23 Mar 2015 17:47:42 -0700 (PDT) Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 283501A89F0 for ; Mon, 23 Mar 2015 17:47:42 -0700 (PDT) Received: from vil78-h03-89-89-75-225.dsl.sta.abo.bbox.fr ([89.89.75.225]:50300 helo=GHM-SAM.dot.dj) by host.presenceweb.org with esmtpa (Exim 4.85) (envelope-from ) id 1YaD0O-0004CU-E2; Mon, 23 Mar 2015 17:47:40 -0700 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 23 Mar 2015 21:23:13 +0100 To: Tim Bray ,Pete Resnick From: JFC Morfin In-Reply-To: References: <551040BC.2080409@qti.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.presenceweb.org X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: intl+dot.dj/only user confirmed/virtual account not confirmed X-Source: X-Source-Args: X-Source-Dir: Message-Id: <20150324004742.283501A89F0@ietfa.amsl.com> Archived-At: Cc: json@ietf.org Subject: Re: [Json] Closing of the group X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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, 24 Mar 2015 00:47:43 -0000 At 19:32 23/03/2015, Tim Bray wrote: >Thanks everyone. +1. Very interesting to follow. jfc >On Mar 24, 2015 5:35 AM, "Pete Resnick" ><presnick@qti.qualcomm.com> wrote: >Congrats on getting all of the work items completed. I have sent in >the request to the secretariat to conclude the WG. The mailing list >will remain open for future discussion. From nobody Tue Mar 24 07:29:18 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFD741A877A for ; Tue, 24 Mar 2015 07:29:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.211 X-Spam-Level: X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 8QCh92GlFBQW for ; Tue, 24 Mar 2015 07:29:16 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32581A877E for ; Tue, 24 Mar 2015 07:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=953; q=dns/txt; s=iport; t=1427207356; x=1428416956; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=x/QmkMwOUduoB6FAeWUgtKtw3srX39aTIEKNZGCgt+I=; b=DnwzoOFRioOLoO2lM0THCctlIrTI41YM5N7nhjJlDJaL/XOaQypkVlV5 YnX/EiiUAsxkgmCBsYF2fifI0wi3HzKA6NgFB1oep8adUZn1mUu2zqDKr W9pZvGNuJmEoVUDWgtK2uAbChwZt2wntKeZPET1PpmvKc89leLfEaoJJJ 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AOBQBodBFV/5JdJa1cgwZSWgSDDMM4hX0CgThMAQEBAQEBfYQVAQEEI0sKEQsaAgUWCwICCQMCAQIBRQYNCAEBiCuuZ5oeAQEBAQEBAQMBAQEBAQEBARYEgSGKAIRDOhaCUoFFAQSLE4kshgCHA40pIoIBHYFuUYFEfwEBAQ X-IronPort-AV: E=Sophos;i="5.11,458,1422921600"; d="scan'208";a="406202103" Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP; 24 Mar 2015 14:29:15 +0000 Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t2OETFlh001628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 24 Mar 2015 14:29:15 GMT Received: from [10.89.8.107] (10.89.8.107) by xhc-rcd-x15.cisco.com (173.37.183.89) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 24 Mar 2015 09:29:15 -0500 Message-ID: <551174BA.6080201@cisco.com> Date: Tue, 24 Mar 2015 09:29:14 -0500 From: =?UTF-8?B?4oyYIE1hdHQgTWlsbGVy?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: References: <551040BC.2080409@qti.qualcomm.com> In-Reply-To: <551040BC.2080409@qti.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.89.8.107] Archived-At: Subject: Re: [Json] Closing of the group X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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, 24 Mar 2015 14:29:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thanks to all who participated in this Working Group, and especially to our authors and sponsoring AD for seeing the documents through to completion. As noted a few times now, the Working Group is closed but the mailing list will remain open. Feel free to continue to discuss JSON-related things. - - Matt Miller Doffed and returned hat -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJVEXS6AAoJEDWi+S0W7cO1GJYIAJjMo2vEpC5EU2hXaVEU+pU4 QAdTrX9UD/PdQemMPwZn5mSqh1faemJtTnDQpXxJzXoerBfSkUkmthbsPsam+nIw agtuRd75ltuKGjKd7nF5MNsdM0nngiuAMC+eZJltp4OAl54wtU4SlbFQRdTB++3Y 4ZqzcKGbAnI99VEeGkqok2d96w4h1AnjL/3qgiKzSdklnvvleGzaOTiimqbJqQDp 1STtd9L4P7aQZ6vmqoT7PzNDi/7PSPiXA7qXvwj26CclhhWLDWREslfyIoKUzK1L ZIn86J69d+/JF2eAriA4RAP+3b2iteUBOaVky8v31nFHjTqVsXiBLsD7wIW/BLM= =UyHL -----END PGP SIGNATURE----- From nobody Mon Mar 30 12:39:04 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162671A8734 for ; Mon, 30 Mar 2015 12:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.422 X-Spam-Level: * X-Spam-Status: No, score=1.422 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 Rd8SnMXxNhbv for ; Mon, 30 Mar 2015 12:39:02 -0700 (PDT) Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (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 9C0F01A82E2 for ; Mon, 30 Mar 2015 12:38:40 -0700 (PDT) Received: by lbdc10 with SMTP id c10so48496790lbd.2 for ; Mon, 30 Mar 2015 12:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=HpYSdWTyYjRuaP7zHD5sHApm5+BvPG+5d7IEcmcTZy0=; b=CVNVmSzxAhcNEwN69lDjwoen8a+2Dn7ZlUHKV0NMFy5ijSWh1Fdd2urYVudP3mqIoy BJetZD0uNlJB8TmPpsgqJJfPw2FDfA+fbnlFbkUR8GiK49Ini66W78gQ20Ryut8s4VOP C+p/b/wGx6aWTxd8/Lbi1vroV5rgKHNt88dNgaGJYnHSLNqng8bJAEAWEaZ4FxSBSHB8 yrzhMPw6bzrBwV22kk0y+wCyVDX+kFexSnjpiDQE/2c83bIQNBn6JSE1bcvWnHK835qm ngF11uzyt89O3ug+yScJmWZFp3D72sh0aX/2WPXL3GFQum0didwiNqfSSLWxlznt4YNz X25Q== MIME-Version: 1.0 X-Received: by 10.152.4.136 with SMTP id k8mr27936005lak.103.1427744319191; Mon, 30 Mar 2015 12:38:39 -0700 (PDT) Sender: hallam@gmail.com Received: by 10.112.147.165 with HTTP; Mon, 30 Mar 2015 12:38:39 -0700 (PDT) Date: Mon, 30 Mar 2015 15:38:39 -0400 X-Google-Sender-Auth: L8I5ECCeKUxuqDxTklCMoyAZrgc Message-ID: From: Phillip Hallam-Baker To: JSON WG Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [Json] Doofus Parameter Labels X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 30 Mar 2015 19:39:03 -0000 So, I am implementing an IETF draft which is fairly widely used and using a code generator to speed things along. The code is breaking because the spec has decided to use 'protected' as a tag which is of course a reserved keyword in Java, C# and much else. OK so there is an escape feature that I can use instead. But those don't exist in other languages. And then I come across a tag that has a non alphanumeric tag value. This sort of thing is likely to be happening quite a bit now that people are using JSON and it would be a lot better if we could avoid it. The fact that JSON allows tags to be any valid UNICODE sequence does not mean that all choices are equal. In general it would be good if people writing specs could stick to the identifier naming rules for C and avoid reserved words from Java, C#, etc. The languages and tools I use are quite capable of using accented characters. I have absolutely no clue how to generate them on the keyboard though. From nobody Mon Mar 30 13:04:33 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDBE1A886D for ; Mon, 30 Mar 2015 13:04:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 b7fz3VAGHNiD for ; Mon, 30 Mar 2015 13:04:31 -0700 (PDT) Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551271A1B62 for ; Mon, 30 Mar 2015 13:04:31 -0700 (PDT) Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65]) by Websense Email Security Gateway with ESMTPS id 38166AE10EDD4; Mon, 30 Mar 2015 20:04:25 +0000 (GMT) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id t2UK4Qmr012283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Mar 2015 16:04:27 -0400 Received: from [135.222.152.71] (wdr-i7mbp2.mh.lucent.com [135.222.152.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id t2UK4OTE024083; Mon, 30 Mar 2015 15:04:25 -0500 (CDT) User-Agent: Microsoft-MacOutlook/14.4.8.150116 Date: Mon, 30 Mar 2015 16:04:32 -0400 From: Wendy Roome To: Phillip Hallam-Baker , JSON WG Message-ID: Thread-Topic: [Json] Doofus Parameter Labels References: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [Json] Doofus Parameter Labels X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 30 Mar 2015 20:04:33 -0000 It would help if you told us which draft and which code generator you are using. My first reaction is that if the code generator is supposed to generate real code that you can feed directly into a compiler, then the code generator should ensure that it generates legal code. Eg, if it maps a protocol field into a variable, the code gen should transmogrify the protocol field name into a valid variable name. Simplest solution is to slap a fixed prefix, like m_, onto every generated variable, and replace non-alpha-num chars with _. My second reaction is why can=B9t you do that yourself? - Wendy Roome On 03/30/2015, 15:38, "Phillip Hallam-Baker" wrote: >So, I am implementing an IETF draft which is fairly widely used and >using a code generator to speed things along. > >The code is breaking because the spec has decided to use 'protected' >as a tag which is of course a reserved keyword in Java, C# and much >else. > >OK so there is an escape feature that I can use instead. But those >don't exist in other languages. And then I come across a tag that has >a non alphanumeric tag value. > > >This sort of thing is likely to be happening quite a bit now that >people are using JSON and it would be a lot better if we could avoid >it. The fact that JSON allows tags to be any valid UNICODE sequence >does not mean that all choices are equal. > >In general it would be good if people writing specs could stick to the >identifier naming rules for C and avoid reserved words from Java, C#, >etc. The languages and tools I use are quite capable of using accented >characters. I have absolutely no clue how to generate them on the >keyboard though. > >_______________________________________________ >json mailing list >json@ietf.org >https://www.ietf.org/mailman/listinfo/json From nobody Mon Mar 30 13:20:14 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 308651A8756 for ; Mon, 30 Mar 2015 13:20:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.233 X-Spam-Level: X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 2bvT-Z21LtEk for ; Mon, 30 Mar 2015 13:20:11 -0700 (PDT) Received: from homiemail-a86.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D813E1A886D for ; Mon, 30 Mar 2015 13:16:42 -0700 (PDT) Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id D4EDE360155; Mon, 30 Mar 2015 13:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=Yh1QkE09XiscMu AQmmFuiiIWk9o=; b=IGXFyK9+hwA4YoPzdFhph70zMR8QoJw5j3mUTGzX099s5q O9VsOhrhp52JNDYG3YlWDh9Cl+aMHXSFfa+45rgwHCQ5zeriuXj7O1Tg5OEqyKVZ FVBAuSTLv1RLEowRBPaObxYoVXb/DHfE5EI2PhSCGhzNhRMEEAF8kAV3mYImI= Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPA id CF747360135; Mon, 30 Mar 2015 13:15:45 -0700 (PDT) Date: Mon, 30 Mar 2015 15:15:35 -0500 From: Nico Williams To: Phillip Hallam-Baker Message-ID: <20150330201534.GV10960@localhost> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: JSON WG Subject: Re: [Json] Doofus Parameter Labels X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 30 Mar 2015 20:20:12 -0000 On Mon, Mar 30, 2015 at 03:38:39PM -0400, Phillip Hallam-Baker wrote: > So, I am implementing an IETF draft which is fairly widely used and > using a code generator to speed things along. > > The code is breaking because the spec has decided to use 'protected' > as a tag which is of course a reserved keyword in Java, C# and much > else. > > OK so there is an escape feature that I can use instead. But those > don't exist in other languages. And then I come across a tag that has > a non alphanumeric tag value. This sort of question comes up a lot for jq. I don't think you can produce a generic rule here. "protected" is a keyword in many languages, but not others. It's not a keyword in jq, for example, though 'reduce' is (which is probably not a keyword elsewhere). There is a workaround, of course. Instead of writing .then.protected one has to write .["then"].protected or ."then".protected in jq in order to access the value at the "protected" object name in the object at the "then" name in the top-level object. What sort of rule do you have in mind for avoiding this? Why are the workarounds insufficient? > This sort of thing is likely to be happening quite a bit now that > people are using JSON and it would be a lot better if we could avoid > it. The fact that JSON allows tags to be any valid UNICODE sequence > does not mean that all choices are equal. There are other considerations too. For example: names shorter than 8 or 16 bytes may get treated as immediate values, without heap allocation (I have a half-baked patch to do that for jq) in some implementations. (E.g., a NaN-coding implementation may be able to store most 7-byte strings as immediate values.) > In general it would be good if people writing specs could stick to the > identifier naming rules for C and avoid reserved words from Java, C#, > etc. The languages and tools I use are quite capable of using accented > characters. I have absolutely no clue how to generate them on the > keyboard though. OK, so, stick to identifier naming rules for C, avoid keywords from some set of programming languages, and don't use non-ASCII characters. How do we specify such constraints? Remember, programming language specs evolve and tend to grow new keywords. -1 From nobody Mon Mar 30 15:35:52 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D4A1A6F29 for ; Mon, 30 Mar 2015 15:35:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.122 X-Spam-Level: X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 Lc0dliiXLF43 for ; Mon, 30 Mar 2015 15:35:49 -0700 (PDT) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 48FE51A6F28 for ; Mon, 30 Mar 2015 15:35:49 -0700 (PDT) Received: by lbdc10 with SMTP id c10so51290491lbd.2 for ; Mon, 30 Mar 2015 15:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=PKFEr5EcGt0xhMoNHVG12ecqjrdM7hPcofATcXQ86Lc=; b=uv/nBmpJVqFlouTEisupFEvQHuWlbcS5LHfC90qCsApkQaXysXP7H3APMIwEvcSFEk YQlgEnsRYxMFwb7ijqbFxnU14Gy8Ndzz58OlQluP1g6HgL7u1BmFwfSrWrFNit+noUwV dmVNZlxZfHce5+PCh8teKJEePYVM3ktps/EtqmC/nsub14G4WJhT8BKsOFFQGfKrthu3 e3DF3D5SvfrjCBoYYvU0QBeXJNP+saIekOMxVe8+gwo9Y4s3WbzudVAk10ORU0vh43uF 59ei9m2dk2bqN1aQlpGlOzGRQUghuzXoUGvbo3VI4Us5ToON/qkTxBTPkoSthVeMsxCr NOUQ== MIME-Version: 1.0 X-Received: by 10.112.161.66 with SMTP id xq2mr28451807lbb.103.1427754947782; Mon, 30 Mar 2015 15:35:47 -0700 (PDT) Sender: hallam@gmail.com Received: by 10.112.147.165 with HTTP; Mon, 30 Mar 2015 15:35:47 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Mar 2015 18:35:47 -0400 X-Google-Sender-Auth: QIxDwELiex2XmW4hwNFcCJ7QuPY Message-ID: From: Phillip Hallam-Baker To: Wendy Roome Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: Cc: JSON WG Subject: Re: [Json] Doofus Parameter Labels X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 30 Mar 2015 22:35:50 -0000 On Mon, Mar 30, 2015 at 4:04 PM, Wendy Roome w= rote: > It would help if you told us which draft and which code generator you are > using. The draft is water under the bridge at this point. The code generator is ProtoGen. > My first reaction is that if the code generator is supposed to generate > real code that you can feed directly into a compiler, then the code > generator should ensure that it generates legal code. Eg, if it maps a > protocol field into a variable, the code gen should transmogrify the > protocol field name into a valid variable name. The issue is not the difficulty of transmogrification in the generator, it is remembering what the transmogrification is in my head. Programming is a process of getting ideas into electronic form. The more unnecessary hoops people have to jump through, the greater the probability of error. > Simplest solution is to > slap a fixed prefix, like m_, onto every generated variable, and replace > non-alpha-num chars with _. > > My second reaction is why can=C2=B9t you do that yourself? The problem comes when you are using two code generators that have different ways of coping with the problem. The choice of labels is arbitrary. Why make choices that introduce unnecessary complexity? From nobody Mon Mar 30 16:20:42 2015 Return-Path: X-Original-To: json@ietfa.amsl.com Delivered-To: json@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5761A88E4 for ; Mon, 30 Mar 2015 16:20:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.044 X-Spam-Level: X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 sT475K8D27ST for ; Mon, 30 Mar 2015 16:20:40 -0700 (PDT) Received: from homiemail-a84.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1C82B1A88E3 for ; Mon, 30 Mar 2015 16:20:40 -0700 (PDT) Received: from homiemail-a84.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTP id D28F21DE087 for ; Mon, 30 Mar 2015 16:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=GhBvM/Q3a+ldq9z3novF XL3R5D0=; b=FqG5qVvcDdo870qjqEjlwSHJnp2zBofhxjGXZXXyGuXclg8QRYCz XGdeSXRoyn+QEurQLJnMjfqEh6xUJYYpvz2ld94xsnG1CLrK4dqJgI61B/PSl0p1 HaiesRMiK7tyOIGwx/DpPPWb1XrE0K/B5nXZCVmj380k9UAqSqjeCDM= Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTPSA id BFB6C1DE085 for ; Mon, 30 Mar 2015 16:20:39 -0700 (PDT) Received: by iedfl3 with SMTP id fl3so3196099ied.1 for ; Mon, 30 Mar 2015 16:20:39 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.164.69 with SMTP id n66mr51804792ioe.82.1427757639421; Mon, 30 Mar 2015 16:20:39 -0700 (PDT) Received: by 10.64.130.66 with HTTP; Mon, 30 Mar 2015 16:20:39 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Mar 2015 18:20:39 -0500 Message-ID: From: Nico Williams To: Phillip Hallam-Baker Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Wendy Roome , JSON WG Subject: Re: [Json] Doofus Parameter Labels X-BeenThere: json@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 30 Mar 2015 23:20:41 -0000 On Mon, Mar 30, 2015 at 5:35 PM, Phillip Hallam-Baker wrote: > The choice of labels is arbitrary. Why make choices that introduce > unnecessary complexity? Because we can't predict what all those names will be.