JavaScript Object Notation (JSON) Text Sequences
draft-ietf-json-text-sequence-05
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7464.
|
|
---|---|---|---|
Author | Nicolás Williams | ||
Last updated | 2014-08-19 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
GENART Last Call review
(of
-09)
by David Black
On the Right Track
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | Paul E. Hoffman | ||
IESG | IESG state | Became RFC 7464 (Proposed Standard) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Pete Resnick | ||
Send notices to | json-chairs@tools.ietf.org, draft-ietf-json-text-sequence@tools.ietf.org |
draft-ietf-json-text-sequence-05
Internet-Draft JSON Text Sequences August 2014 5. Acknowledgements Phillip Hallam-Baker proposed the use of JSON text sequences for logfiles and pointed out the need for resynchronization. James Manger contributed the ABNF for resynchronization. Stephen Dolan created <jq>, which uses something like JSON text sequences (with LF as the separator between texts on output, and requiring only such whitespace as needed to disambiguate on input). Williams Expires February 21, 2015 [Page 7] Internet-Draft JSON Text Sequences August 2014 6. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159, March 2014. Williams Expires February 21, 2015 [Page 8] Internet-Draft JSON Text Sequences August 2014 Author's Address Nicolas Williams Cryptonector, LLC Email: nico@cryptonector.com Williams Expires February 21, 2015 [Page 9]