The JavaScript Object Notation (JSON) Data Interchange Format
RFC 8259
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2018-12-20
|
04 | (System) | Received changes through RFC Editor sync (changed abstract to 'JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from … Received changes through RFC Editor sync (changed abstract to '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.') |
2017-12-18
|
04 | (System) | Received changes through RFC Editor sync (added Errata tag) |
2017-12-13
|
04 | (System) | Received changes through RFC Editor sync (created alias STD 90) |
2017-12-13
|
04 | (System) | Received changes through RFC Editor sync (created alias RFC 8259, changed abstract to 'JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange … Received changes through RFC Editor sync (created alias RFC 8259, changed abstract to '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.', changed pages to 16, changed standardization level to Internet Standard, changed state to RFC, added RFC published event at 2017-12-13, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-jsonbis-rfc7159bis and RFC 7159) |
2017-12-13
|
04 | (System) | RFC published |
2017-12-08
|
04 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8259">AUTH48-DONE</a> from IESG |
2017-10-06
|
04 | (System) | RFC Editor state changed to IESG from AUTH48 |
2017-08-28
|
04 | (System) | RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8259">AUTH48</a> from RFC-EDITOR |
2017-08-14
|
04 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
2017-07-31
|
04 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2017-07-24
|
04 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
2017-07-21
|
04 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2017-07-19
|
04 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2017-07-19
|
04 | Matthew Miller | New version available: draft-ietf-jsonbis-rfc7159bis-04.txt |
2017-07-19
|
04 | (System) | Forced post of submission |
2017-07-18
|
03 | (System) | RFC Editor state changed to EDIT |
2017-07-18
|
03 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2017-07-18
|
03 | (System) | Announcement was received by RFC Editor |
2017-07-18
|
04 | (System) | Request for posting confirmation emailed to previous authors: Tim Bray <tbray@textuality.com> |
2017-07-18
|
04 | Matthew Miller | Uploaded new revision |
2017-07-18
|
03 | (System) | IANA Action state changed to In Progress |
2017-07-18
|
03 | Cindy Morgan | IESG state changed to Approved-announcement sent from IESG Evaluation::Revised I-D Needed |
2017-07-18
|
03 | Cindy Morgan | IESG has approved the document |
2017-07-18
|
03 | Cindy Morgan | Closed "Approve" ballot |
2017-07-18
|
03 | Cindy Morgan | Ballot approval text was generated |
2017-07-18
|
03 | Cindy Morgan | Ballot writeup was changed |
2017-07-18
|
03 | Alexey Melnikov | RFC Editor Note was changed |
2017-07-17
|
03 | Alexey Melnikov | RFC Editor Note was changed |
2017-05-30
|
03 | Alexey Melnikov | IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation::AD Followup |
2017-03-23
|
03 | Alexey Melnikov | [Ballot comment] Alvaro: I think you are correct. I've added an RFC Editor note. |
2017-03-23
|
03 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to Yes from Discuss |
2017-03-23
|
03 | Alexey Melnikov | RFC Editor Note was changed |
2017-03-21
|
03 | Alexey Melnikov | Notification list changed to Matthew Miller <linuxwolf+ietf@outer-planes.net> from linuxwolf+ietf@outer-planes.net, Matthew Miller <linuxwolf+ietf@outer-planes.net> |
2017-03-21
|
03 | Alexey Melnikov | Notification list changed to linuxwolf+ietf@outer-planes.net, Matthew Miller <linuxwolf+ietf@outer-planes.net> from linuxwolf+ietf@outer-planes.net |
2017-03-21
|
03 | Alexey Melnikov | Document shepherd changed to Matthew A. Miller |
2017-03-21
|
03 | Alexey Melnikov | Notification list changed to linuxwolf+ietf@outer-planes.net from "Matthew Miller" <mamille2@cisco.com> |
2017-03-21
|
03 | Alexey Melnikov | RFC Editor Note was changed |
2017-03-16
|
03 | Cindy Morgan | IESG state changed to IESG Evaluation::AD Followup from IESG Evaluation |
2017-03-15
|
03 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
2017-03-15
|
03 | Jari Arkko | [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko |
2017-03-15
|
03 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2017-03-15
|
03 | Kathleen Moriarty | [Ballot comment] I don't see a response to the first part of the SecDir review on the Security Considerations section. Given the content of the … [Ballot comment] I don't see a response to the first part of the SecDir review on the Security Considerations section. Given the content of the current security considerations section, I agree with Ben that the additional considerations he mentions should be included. Can someone respond to Ben please on that part of his review? Thank you. |
2017-03-15
|
03 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2017-03-15
|
03 | Alexey Melnikov | [Ballot discuss] Text about mandatory to implement charset encodings or charset auto-discovery need to be added back to the document. Alvaro: I think you are … [Ballot discuss] Text about mandatory to implement charset encodings or charset auto-discovery need to be added back to the document. Alvaro: I think you are correct. I've added an RFC Editor note. |
2017-03-15
|
03 | Alexey Melnikov | Ballot discuss text updated for Alexey Melnikov |
2017-03-15
|
03 | Alexey Melnikov | RFC Editor Note was changed |
2017-03-15
|
03 | Alexey Melnikov | RFC Editor Note for ballot was generated |
2017-03-15
|
03 | Alexey Melnikov | RFC Editor Note for ballot was generated |
2017-03-15
|
03 | Alexey Melnikov | [Ballot discuss] Text about mandatory to implement charset encodings or charset auto-discovery need to be added back to the document. |
2017-03-15
|
03 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to Discuss from Yes |
2017-03-14
|
03 | Ben Campbell | [Ballot comment] - section 9: This allows limits for nesting depth, number range and precision, and string length. Can you offer any guidance about what … [Ballot comment] - section 9: This allows limits for nesting depth, number range and precision, and string length. Can you offer any guidance about what sorts of limits might be reasonable? Or what limits might unreasonably impact interoperability? - 12, 2nd paragraph: This paragraph sort of buries the lede. I thought it was going to talk about the implications of not being able to parse certain JSON legal characters with eval(), but I understand it really about the risk of arbitrary executable content. I suggest you say that in the first sentence. |
2017-03-14
|
03 | Ben Campbell | [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell |
2017-03-14
|
03 | Stephen Farrell | [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell |
2017-03-14
|
03 | Alvaro Retana | |
2017-03-14
|
03 | Alvaro Retana | [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana |
2017-03-14
|
03 | Alia Atlas | [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas |
2017-03-14
|
03 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
2017-03-14
|
03 | Benoît Claise | [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise |
2017-03-14
|
03 | Mirja Kühlewind | [Ballot Position Update] New position, Yes, has been recorded for Mirja Kühlewind |
2017-03-13
|
03 | Joel Jaeggli | [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli |
2017-03-13
|
03 | Alexey Melnikov | IESG state changed to IESG Evaluation from Waiting for Writeup |
2017-03-13
|
03 | Alexey Melnikov | Ballot has been issued |
2017-03-13
|
03 | Alexey Melnikov | [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov |
2017-03-13
|
03 | Alexey Melnikov | Created "Approve" ballot |
2017-03-13
|
03 | Alexey Melnikov | Ballot writeup was changed |
2017-03-07
|
03 | Benjamin Kaduk | Request for Last Call review by SECDIR Completed: Has Issues. Reviewer: Benjamin Kaduk. |
2017-03-07
|
03 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2017-03-06
|
03 | Sabrina Tanamal | IANA Review state changed to IANA OK - Actions Needed from IANA - Not OK |
2017-03-06
|
03 | (System) | IANA Review state changed to IANA - Not OK from IANA - Review Needed |
2017-03-06
|
03 | Sabrina Tanamal | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-jsonbis-rfc7159bis-03.txt. If any part of this review is inaccurate, please let … (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Services Operator has completed its review of draft-ietf-jsonbis-rfc7159bis-03.txt. If any part of this review is inaccurate, please let us know. The IANA Services Operator has a question about one of the actions requested in the IANA Considerations section of this document. The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete. In the application Media Types registry located at: https://www.iana.org/assignments/media-types/ the entry for application/json already exists. IANA Question --> Should the reference be changed from RFC 7159 to the new [ RFC-to-be ]? Are there changes to the template? The IANA Services Operator understands that this is the only action required to be completed upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. Thank you, Sabrina Tanamal IANA Services Specialist PTI |
2017-03-03
|
03 | Elwyn Davies | Request for Last Call review by GENART Completed: Ready. Reviewer: Elwyn Davies. |
2017-03-02
|
03 | Jürgen Schönwälder | Request for Last Call review by OPSDIR Completed: Ready. Reviewer: Jürgen Schönwälder. Sent review to list. |
2017-02-27
|
03 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Jürgen Schönwälder |
2017-02-27
|
03 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Jürgen Schönwälder |
2017-02-23
|
03 | Jean Mahoney | Request for Last Call review by GENART is assigned to Elwyn Davies |
2017-02-23
|
03 | Jean Mahoney | Request for Last Call review by GENART is assigned to Elwyn Davies |
2017-02-23
|
03 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Benjamin Kaduk |
2017-02-23
|
03 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Benjamin Kaduk |
2017-02-22
|
03 | Alexey Melnikov | Placed on agenda for telechat - 2017-03-16 |
2017-02-21
|
03 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2017-02-21
|
03 | Amy Vezza | The following Last Call announcement was sent out:<br><br>From: The IESG <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> CC: jsonbis-chairs@ietf.org, json@ietf.org, "Matthew Miller" … The following Last Call announcement was sent out:<br><br>From: The IESG <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> CC: jsonbis-chairs@ietf.org, json@ietf.org, "Matthew Miller" <mamille2@cisco.com>, mamille2@cisco.com, alexey.melnikov@isode.com, draft-ietf-jsonbis-rfc7159bis@ietf.org Reply-To: ietf@ietf.org Sender: <iesg-secretary@ietf.org> Subject: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard 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' <draft-ietf-jsonbis-rfc7159bis-03.txt> 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. |
2017-02-21
|
03 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2017-02-21
|
03 | Alexey Melnikov | Last call was requested |
2017-02-21
|
03 | Alexey Melnikov | Last call announcement was generated |
2017-02-21
|
03 | Alexey Melnikov | Ballot approval text was generated |
2017-02-21
|
03 | Alexey Melnikov | Ballot writeup was generated |
2017-02-21
|
03 | Alexey Melnikov | IESG state changed to Last Call Requested from AD Evaluation::AD Followup |
2017-02-19
|
03 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2017-02-19
|
03 | Tim Bray | New version available: draft-ietf-jsonbis-rfc7159bis-03.txt |
2017-02-19
|
03 | (System) | New version approved |
2017-02-19
|
03 | (System) | Request for posting confirmation emailed to previous authors: "Tim Bray" <tbray@textuality.com> |
2017-02-19
|
03 | Tim Bray | Uploaded new revision |
2017-01-17
|
02 | Alexey Melnikov | IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation |
2016-12-18
|
02 | Alexey Melnikov | IESG state changed to AD Evaluation from Publication Requested |
2016-12-05
|
02 | Matthew Miller | 1. Summary This document is an update to RFC 7159 to promote the JSON format to Internet Standard. In promoting to Internet Standard, this document … 1. Summary This document is an update to RFC 7159 to promote the JSON format to Internet Standard. In promoting to Internet Standard, this document is a minimal update to RFC 7159 to apply accepted errata and to normatively reference ECMA-404. Matthew Miller is the document shepherd. Alexey Melnikov is the responsible AD. 2. Review and Consensus This document had numerous reviews, drawn out over several months. While no new technical concerns were raised, the consensus on this document is rough due to the unique nature of the normative reference to ECMA-404. It is not strictly necessary to understand ECMA-404 to implement JSON; rather the reference is an agreement with Ecma TC39 to agree on a single shared definition of JSON. 3. Intellectual Property As with RFC 7159, there was no WG discussion of IPR given that this is an update to a format document for which there was no IPR statements in the first place. 4. Other Points Ecma TC39 has agreed to publish an update to ECMA-404 to reference the RFC-to-be 7159bis. The responsible AD may hold publication until TC39 makes their change, which is waiting until 7159bis is assigned a number. |
2016-12-02
|
02 | Alexey Melnikov | IETF WG state changed to Submitted to IESG for Publication from In WG Last Call |
2016-12-02
|
02 | Alexey Melnikov | IESG state changed to Publication Requested from AD is watching |
2016-11-30
|
02 | Matthew Miller | Notification list changed to "Matthew Miller" <mamille2@cisco.com> |
2016-11-30
|
02 | Matthew Miller | Document shepherd changed to Matthew Miller |
2016-07-18
|
02 | Matthew Miller | IETF WG state changed to In WG Last Call from WG Document |
2016-06-15
|
02 | Tim Bray | New version available: draft-ietf-jsonbis-rfc7159bis-02.txt |
2016-06-13
|
01 | Alexey Melnikov | IESG state changed to AD is watching from Dead |
2016-06-12
|
01 | Tim Bray | New version available: draft-ietf-jsonbis-rfc7159bis-01.txt |
2016-04-21
|
00 | (System) | Document has expired |
2016-04-21
|
00 | (System) | IESG state changed to Dead from AD is watching |
2016-04-13
|
00 | Alexey Melnikov | IESG process started in state AD is watching |
2016-04-13
|
00 | Alexey Melnikov | Changed consensus to Yes from Unknown |
2016-04-13
|
00 | Alexey Melnikov | Intended Status changed to Internet Standard from None |
2015-10-19
|
00 | Tim Bray | New version available: draft-ietf-jsonbis-rfc7159bis-00.txt |