Re: [Json] Working Group Last Call of draft-ietf-json-rfc4627bis-04
Peter Saint-Andre <stpeter@stpeter.im> Thu, 26 September 2013 23:27 UTC
Return-Path: <stpeter@stpeter.im>
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 C5A5E21F9CC8 for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 16:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.256
X-Spam-Level:
X-Spam-Status: No, score=-102.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 mGIlpOEGocco for <json@ietfa.amsl.com>; Thu, 26 Sep 2013 16:27:09 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 514FF21E80C5 for <json@ietf.org>; Thu, 26 Sep 2013 16:27:08 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E3AB541509; Thu, 26 Sep 2013 17:32:19 -0600 (MDT)
Message-ID: <5244C2C5.9010608@stpeter.im>
Date: Thu, 26 Sep 2013 17:27:01 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <B2706F01-E791-40AE-AC54-6DC7C3E2A0E3@mnot.net>
In-Reply-To: <B2706F01-E791-40AE-AC54-6DC7C3E2A0E3@mnot.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: JSON WG <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [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 23:27:17 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/26/13 5:24 PM, Mark Nottingham wrote: > * Since this document is so similar to 4627, have you considered > leaving Crockford on the author list? IMHO that is the right thing to do, unless he objects. The Area Director might need to perform an AD-override on AUTH48 approvals if Mr. Crockford has in fact disappeared or is uncommunicative. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSRMLFAAoJEOoGpJErxa2p1HAQAJNQpOnjgHJJ/Vvn/4Rw4a3T AuF3MFRN1c1rXa4a3vvAv/H64tXjgVZXbBzNQScB3P0F1jOdL1DGzeyCYQlSci30 Nl1Kn3GF9aLFSaD7JkgnSOkTjkptQuZS9tj5ybm0ub9M8rQBXMPFRSCuzMczJOiV ZuQyXbx2maSX/Nm1UIZo+wpFw34NnmE2+pTnBeIvclIY+LVJTmPkXoUvDW8Nq3WQ Ng2klJ8f7Qyd6OFOitsdmci7xNuxqQgu8taZn1fHWJa9KsQ20xg41UoHKpI5+C6a 4/xzBicLTKGLdJY6Fp+paXfxk6EL2P3EV0IFHI8E66B8cPi3x+y1/lfxDSH5Gl8z M9uXbDj7s8FzKBFUc8trlyFk5cXbHcBv/yqJOQAK07UuWo95VGKbsVL8Z9VxnbPe 2gQn83HRa04RfZUzEqUCGqoSIOQBIV0YqzLbRfowR7mI2sKCvo6v2fasGDLw19Ik D4HH3uCaBbmPr04lGH+XdfOmAeSJdqsA9tVnmAL4/XmvyX7vzca6o5g2tzjqA2m6 E3vWk9MEFBmx29tNU/etg1sLVQsKqIQmbyHLaQDmwl6Q2JZuNnI/0ugt+QARqngs oXJNWtvXOsztaeS6HR1sqWWU+vHWRdV04wk3R24QnS/DrcYwg43m0TDIojBCQdCq 9xElSZ6E1K7fhUHZNCKJ =dz4j -----END PGP SIGNATURE-----
- [Json] Working Group Last Call of draft-ietf-json… Matt Miller (mamille2)
- Re: [Json] Working Group Last Call of draft-ietf-… R S
- Re: [Json] Working Group Last Call of draft-ietf-… Tim Bray
- [Json] Differences between RFC 4627 or the curren… Paul Hoffman
- [Json] "suffer fatal runtime exceptions" Paul Hoffman
- [Json] -0.0 Paul Hoffman
- Re: [Json] -0.0 R S
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] -0.0 Tim Bray
- Re: [Json] "suffer fatal runtime exceptions" R S
- Re: [Json] Differences between RFC 4627 or the cu… Eliot Lear
- Re: [Json] "suffer fatal runtime exceptions" Tim Bray
- Re: [Json] -0.0 R S
- Re: [Json] -0.0 Tim Bray
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 R S
- Re: [Json] Differences between RFC 4627 or the cu… R S
- 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] Differences between RFC 4627 or the cu… Paul Hoffman
- [Json] Authorship Paul Hoffman
- [Json] Obsoletes RFC 4627 Paul Hoffman
- [Json] Section 1.3, "Changes from RFC 4627" Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Authorship 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… John Cowan
- Re: [Json] Authorship Peter Saint-Andre
- Re: [Json] Authorship John Cowan
- 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] Authorship Eliot Lear
- Re: [Json] [authorship] (was: Working Group Last … Martin J. Dürst
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] Section 1.3, "Changes from RFC 4627" Martin J. Dürst
- Re: [Json] Obsoletes RFC 4627 Martin J. Dürst
- Re: [Json] -0.0 Martin J. Dürst
- Re: [Json] -0.0 Carsten Bormann
- Re: [Json] -0.0 Bjoern Hoehrmann
- Re: [Json] Authorship Pete Resnick
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- Re: [Json] Authorship Bjoern Hoehrmann
- 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 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 R S
- Re: [Json] -0.0 John Cowan
- Re: [Json] -0.0 Carsten Bormann
- [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
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- [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? Eliot Lear
- [Json] Change control for the MIME media type Paul Hoffman
- Re: [Json] ECMA-262 normative? R S
- Re: [Json] Differences between RFC 4627 or the cu… R S
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] ECMA-262 normative? Tim Bray
- Re: [Json] ECMA-262 normative? Carsten Bormann
- 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… 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… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- 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… R S
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… Paul Hoffman
- Re: [Json] section 1 paragraph 2 on what JSON can… Carsten Bormann
- Re: [Json] Differences between RFC 4627 or the cu… Jorge Chamorro
- Re: [Json] section 1 paragraph 2 on what JSON can… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Tony Hansen
- Re: [Json] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… John Cowan
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] section 1 paragraph 2 on what JSON can… Tony Hansen
- Re: [Json] Differences between RFC 4627 or the cu… Carsten Bormann
- 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… Jorge Chamorro
- Re: [Json] section 1 paragraph 2 on what JSON can… Paul Hoffman
- Re: [Json] Differences between RFC 4627 or the cu… Tim Bray
- Re: [Json] Differences between RFC 4627 or the cu… Martin J. Dürst
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H
- 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] section 1 paragraph 2 on what JSON can… John Cowan
- Re: [Json] section 1 paragraph 2 on what JSON can… Manger, James H