[Json] Working Group Last Call of draft-ietf-json-rfc4627bis-04
"Matt Miller (mamille2)" <mamille2@cisco.com> Thu, 26 September 2013 17:16 UTC
Return-Path: <mamille2@cisco.com>
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 A2ED121F8F24 for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 10:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ct0q80c1yH3 for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 10:16:37 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2C521F9AD5 for <json@ietf.org>; Thu, 26 Sep 2013 10:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6615; q=dns/txt; s=iport; t=1380215676; x=1381425276; h=from:to:subject:date:message-id:mime-version; bh=GAFdPZsOW4k+JL8cGgwb8Wy+QeYp1Rhp+iBEwKPfEnY=; b=AZ9LgqHa7hTU1YAsaZBoSqrQiNGCmYJdUiMJ1C6NiMoyrZCzC8BfztHH bQF+1DLwv3ymdTSAUi5lsvVATxg9R6JmfAauKHKrksy3v0F4Q+rsarIoj Mc2j9gSf2LyBMqETILMHl2XSvnjMEzT2qNeNsba/AM7L6QjAZoPvZkp5H g=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFADRqRFKtJV2d/2dsb2JhbABbgwc4UsBUgSAWdIInAQRuHQEqJjAnBBsGh3ibCqFHjyCDVYEBA5AngS+HVpBJgySCKg
X-IronPort-AV: E=Sophos; i="4.90,986,1371081600"; d="p7s'?scan'208"; a="264921286"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 26 Sep 2013 17:14:36 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8QHEZf4031586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Thu, 26 Sep 2013 17:14:35 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.253]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Thu, 26 Sep 2013 12:14:35 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: JSON WG <json@ietf.org>
Thread-Topic: Working Group Last Call of draft-ietf-json-rfc4627bis-04
Thread-Index: AQHOutveYZPkp5J8/EuBThMG3Fu+pw==
Date: Thu, 26 Sep 2013 17:14:34 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [64.101.72.48]
Content-Type: multipart/signed; boundary="Apple-Mail=_95204221-5B4B-4CD7-B589-7B3B67FD3E79"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Subject: [Json] Working Group Last Call of draft-ietf-json-rfc4627bis-04
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 26 Sep 2013 17:16:45 -0000
Hello All, This message begins the Working Group Last Call (WGLC) on "The JSON Data Interchange Format" < draft-ietf-json-rfc4627bis-04 >. WGLC will end in two weeks, on October 11. Please review the document and send comments to the Working Group mailing list < json at ietf.org > or the co-chairs <json-chairs at tools.ietf.org > before the end of the WGLC. Note that suggested changes which include proposed text will be more strongly considered than those without. Thanks, - Paul Hoffman and Matt Miller
- [Json] Working Group Last Call of draft-ietf-json… Matt Miller (mamille2)
- Re: [Json] Working Group Last Call of draft-ietf-… R S
- [Json] Differences between RFC 4627 or the curren… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Eliot Lear
- [Json] ECMA-262 normative? Carsten Bormann
- Re: [Json] ECMA-262 normative? John Cowan
- Re: [Json] ECMA-262 normative? Paul Hoffman
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] ECMA-262 normative? Eliot Lear
- Re: [Json] ECMA-262 normative? R S
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] ECMA-262 normative? Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] section 1 paragraph 2 on what JSON can… Carsten Bormann
- Re: [Json] section 1 paragraph 2 on what JSON can… Tim Bray
- Re: [Json] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] section 1 paragraph 2 on what JSON can… Paul Hoffman
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H
- Re: [Json] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Martin J. Dürst
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Martin J. Dürst
- Re: [Json] Differences between RFC 4627 or the cu… Bjoern Hoehrmann
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- [Json] "suffer fatal runtime exceptions" Paul Hoffman
- Re: [Json] "suffer fatal runtime exceptions" R S
- Re: [Json] "suffer fatal runtime exceptions" Tim Bray
- [Json] -0.0 Paul Hoffman
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Matt Miller (mamille2)
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 Peter Patel-Schneider
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Paul Hoffman
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Bjoern Hoehrmann
- Re: [Json] Working Group Last Call of draft-ietf-… Tim Bray
- Re: [Json] Working Group Last Call of draft-ietf-… Mark Nottingham
- Re: [Json] Working Group Last Call of draft-ietf-… Peter Saint-Andre
- Re: [Json] Working Group Last Call of draft-ietf-… Tim Bray
- Re: [Json] [authorship] (was: Working Group Last … Martin J. Dürst
- [Json] Authorship Paul Hoffman
- Re: [Json] Authorship R S
- Re: [Json] Authorship Peter Saint-Andre
- Re: [Json] Authorship John Cowan
- Re: [Json] Authorship Eliot Lear
- Re: [Json] Authorship Pete Resnick
- Re: [Json] Authorship Bjoern Hoehrmann
- [Json] Change Control (was: Re: Authorship) Martin J. Dürst
- [Json] Indentation (was: Re: Change Control) Martin J. Dürst
- Re: [Json] Indentation (was: Re: Change Control) Carsten Bormann
- Re: [Json] Indentation (was: Re: Change Control) Carsten Bormann
- Re: [Json] Change Control (was: Re: Authorship) Jorge Chamorro
- [Json] Change control for the MIME media type Paul Hoffman
- [Json] Obsoletes RFC 4627 Paul Hoffman
- Re: [Json] Obsoletes RFC 4627 Martin J. Dürst
- Re: [Json] Obsoletes RFC 4627 Tim Bray
- Re: [Json] Obsoletes RFC 4627 Eliot Lear
- Re: [Json] Obsoletes RFC 4627 Martin J. Dürst
- [Json] Section 1.3, "Changes from RFC 4627" Paul Hoffman
- Re: [Json] Section 1.3, "Changes from RFC 4627" Martin J. Dürst