JSON Type Definition
draft-ucarion-json-type-definition-04
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2020-11-03
|
04 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2020-10-04
|
04 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
2020-07-21
|
04 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
2020-06-29
|
04 | (System) | IANA Action state changed to No IANA Actions from In Progress |
2020-06-29
|
04 | (System) | RFC Editor state changed to EDIT |
2020-06-29
|
04 | (System) | IANA Action state changed to In Progress |
2020-06-28
|
04 | Adrian Farrel | ISE state changed to Sent to the RFC Editor from In IESG Review |
2020-06-28
|
04 | Adrian Farrel | Sent request for publication to the RFC Editor |
2020-06-28
|
04 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed |
2020-06-28
|
04 | Ulysse Carion | New version available: draft-ucarion-json-type-definition-04.txt |
2020-06-28
|
04 | (System) | New version approved |
2020-06-28
|
04 | (System) | Request for posting confirmation emailed to previous authors: Ulysse Carion |
2020-06-28
|
04 | Ulysse Carion | Uploaded new revision |
2020-05-06
|
03 | Adrian Farrel | draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in … draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in August 2019 and ran 6 revisions before changing name to the current draft which is on its 4th revision. The draft has been discussed on the JSON list (the mailing list for the closed JSON working group) where it attracted some comments and suggestions that the author acted on (see the Acknowledgements section). However, since that working group is closed, the author did not see any obvious place to develop his ideas within the IETF and came to the ISE. The ISE contacted the ART ADs (2020-01-25 and 2020-04-07) to see whether they think this work should be handled in their Area via a working group (new or existing) or through AD sponsorship. The ISE also sent mail to DISPATCH (2020-04-10) and the JSON list (2020-04-20). At this stage there seems to be zero interest in doing the work in the IETF although the author would have been happy, and the ISE would sill like to hear if that could be made to work. Once the 5742 review was requested, the ART ADs noted that recent work in the 3GPP has lead to a plan in the ART Area to create of a new IETF working group to discuss JSON schemas. The author and ISE are currently discussing the implications for the document, and the ADs and ISE are trying to understand the schedule for WG creation. Before bringing the document to the ISE, the author received additional input from Evgeny Poberezkin, Tim Bray, Anders Rundgren, and James Manger. The document has also received several reviews for the ISE. Most notably from Carsten Bormann, Henk Birkholz, and Nico Williams. The ISE also checked back with the authors of RFC 8610. The ISE (of course) also did a review. This document contains a very clear statement in the Abstract and Introduction that the work is not the product of the IETF and does not have IETF consensus. It also makes clear that this is an Experiment and sets out the objectives of the experimental work. The document makes no request for IANA action. |
2020-05-05
|
03 | (System) | IANA Review state changed to IANA OK - No Actions Needed |
2020-05-05
|
03 | Amanda Baber | (Via drafts-eval@iana.org): IESG/Authors/ISE: The IANA Functions Operator has reviewed draft-ucarion-json-type-definition-03 and has the following comments: We understand that this document doesn't require any registry … (Via drafts-eval@iana.org): IESG/Authors/ISE: The IANA Functions Operator has reviewed draft-ucarion-json-type-definition-03 and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object. If this assessment is not accurate, please respond as soon as possible. Thank you, Amanda Baber Lead IANA Services Specialist |
2020-05-05
|
03 | Adrian Farrel | draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in … draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in August 2019 and ran 6 revisions before changing name to the current draft which is on its 4th revision. The draft has been discussed on the JSON list (the mailing list for the closed JSON working group) where it attracted some comments and suggestions that the author acted on (see the Acknowledgements section). However, since that working group is closed, the author did not see any obvious place to develop his ideas within the IETF and came to the ISE. The ISE contacted the ART ADs (2020-01-25 and 2020-04-07) to see whether they think this work should be handled in their Area via a working group (new or existing) or through AD sponsorship. The ISE also sent mail to DISPATCH (2020-04-10) and the JSON list (2020-04-20). At this stage there seems to be zero interest in doing the work in the IETF although the author would have been happy, and the ISE would sill like to hear if that could be made to work. Once the 5742 review was requested, the ART ADs noted that recent work in the 3GPP has lead to a plan in the ART Area to create of a new IETF working group to discuss JSON schemas. The author and ISE are currently discussing the implications for the document, and the ADs and ISE are trying to understand the schedule for WG creation. Before bringing the document to the ISE, the author received additional input from Evgeny Poberezkin, Tim Bray, Anders Rundgren, and James Manger. The document has also received several reviews for the ISE. Most notably from Carsten Bormann and Nico Williams. The ISE also checked back with the authors of RFC 8610. The ISE (of course) also did a review. This document contains a very clear statement in the Abstract and Introduction that the work is not the product of the IETF and does not have IETF consensus. It also makes clear that this is an Experiment and sets out the objectives of the experimental work. The document makes no request for IANA action. |
2020-05-04
|
03 | Adrian Farrel | IETF conflict review initiated - see conflict-review-ucarion-json-type-definition |
2020-05-04
|
03 | Adrian Farrel | ISE state changed to In IESG Review from Finding Reviewers |
2020-05-04
|
03 | Adrian Farrel | draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in … draft-ucarion-json-type-definition has been presented for publication as an Experimental RFC in the Independent Stream. The document has a long history having started as draft-ucarion-jddf in August 2019 and ran 6 revisions before changing name to the current draft which is on its 4th revision. The draft has been discussed on the JSON list (the mailing list for the closed JSON working group) where it attracted some comments and suggestions that the author acted on (see the Acknowledgements section). However, since that working group is closed, the author did not see any obvious place to develop his ideas within the IETF and came to the ISE. The ISE contacted the ART ADs (2020-01-25 and 2020-04-07) to see whether they think this work should be handled in their Area via a working group (new or existing) or through AD sponsorship. The ISE also sent mail to DISPATCH (2020-04-10) and the JSON list (2020-04-20). At this stage there seems to be zero interest in doing the work in the IETF although the author would have been happy, and the ISE would sill like to hear if that could be made to work. Before bringing the document to the ISE, the author received additional input from Evgeny Poberezkin, Tim Bray, Anders Rundgren, and James Manger. The document has also received several reviews for the ISE. Most notably from Carsten Bormann and Nico Williams. The ISE also checked back with the authors of RFC 8610. The ISE (of course) also did a review. The document makes no request for IANA action. |
2020-05-04
|
03 | Adrian Farrel | Notification list changed to Adrian Farrel <rfc-ise@rfc-editor.org> |
2020-05-04
|
03 | Adrian Farrel | Document shepherd changed to Adrian Farrel |
2020-04-26
|
03 | Ulysse Carion | New version available: draft-ucarion-json-type-definition-03.txt |
2020-04-26
|
03 | (System) | New version approved |
2020-04-26
|
03 | (System) | Request for posting confirmation emailed to previous authors: Ulysse Carion |
2020-04-26
|
03 | Ulysse Carion | Uploaded new revision |
2020-04-07
|
02 | Adrian Farrel | ISE state changed to Finding Reviewers |
2020-04-07
|
02 | Adrian Farrel | Intended Status changed to Experimental from None |
2020-04-07
|
02 | Adrian Farrel | Stream changed to ISE from None |
2020-04-05
|
02 | Ulysse Carion | New version available: draft-ucarion-json-type-definition-02.txt |
2020-04-05
|
02 | (System) | New version approved |
2020-04-05
|
02 | (System) | Request for posting confirmation emailed to previous authors: Ulysse Carion |
2020-04-05
|
02 | Ulysse Carion | Uploaded new revision |
2020-03-22
|
01 | Ulysse Carion | New version available: draft-ucarion-json-type-definition-01.txt |
2020-03-22
|
01 | (System) | New version approved |
2020-03-22
|
01 | (System) | Request for posting confirmation emailed to previous authors: Ulysse Carion |
2020-03-22
|
01 | Ulysse Carion | Uploaded new revision |
2020-03-16
|
00 | (System) | This document now replaces draft-ucarion-jddf instead of None |
2020-03-16
|
00 | Ulysse Carion | New version available: draft-ucarion-json-type-definition-00.txt |
2020-03-16
|
00 | (System) | New version approved |
2020-03-16
|
00 | Ulysse Carion | Request for posting confirmation emailed to submitter and authors: Ulysse Carion |
2020-03-16
|
00 | Ulysse Carion | Uploaded new revision |