draft-reschke-http-jfv-14.txt | draft-reschke-http-jfv-latest.txt | |||
---|---|---|---|---|
Network Working Group J. F. Reschke | Network Working Group J. F. Reschke | |||
Internet-Draft greenbytes | Internet-Draft greenbytes | |||
Intended status: Informational April 22, 2021 | Intended status: Informational May 2, 2023 | |||
Expires: October 24, 2021 | Expires: November 3, 2023 | |||
A JSON Encoding for HTTP Field Values | A JSON Encoding for HTTP Field Values | |||
draft-reschke-http-jfv-14 | draft-reschke-http-jfv-latest | |||
Abstract | Abstract | |||
This document establishes a convention for use of JSON-encoded field | This document establishes a convention for use of JSON-encoded field | |||
values in new HTTP fields. | values in new HTTP fields. | |||
Editorial Note | Editorial Note | |||
This note is to be removed before publishing as an RFC. | This note is to be removed before publishing as an RFC. | |||
skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
sending a message with subject "subscribe" to ietf-http-wg- | sending a message with subject "subscribe" to ietf-http-wg- | |||
request@w3.org (mailto:ietf-http-wg- | request@w3.org (mailto:ietf-http-wg- | |||
request@w3.org?subject=subscribe). | request@w3.org?subject=subscribe). | |||
Discussions of the HTTPbis Working Group are archived at | Discussions of the HTTPbis Working Group are archived at | |||
<http://lists.w3.org/Archives/Public/ietf-http-wg/>. | <http://lists.w3.org/Archives/Public/ietf-http-wg/>. | |||
XML versions and latest edits for this document are available from | XML versions and latest edits for this document are available from | |||
<http://greenbytes.de/tech/webdav/#draft-reschke-http-jfv>. | <http://greenbytes.de/tech/webdav/#draft-reschke-http-jfv>. | |||
The changes in this draft are summarized in Appendix D.17. | The changes in this draft are summarized in Appendix D.18. | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on October 24, 2021. | This Internet-Draft will expire on November 3, 2023. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2023 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
extracted from this document must include Revised BSD License text as | extracted from this document must include Revised BSD License text as | |||
described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
provided without warranty as described in the Revised BSD License. | provided without warranty as described in the Revised BSD License. | |||
skipping to change at page 3, line 21 ¶ | skipping to change at page 3, line 21 ¶ | |||
D.8. Since draft-ietf-httpbis-jfv-02 . . . . . . . . . . . . . 13 | D.8. Since draft-ietf-httpbis-jfv-02 . . . . . . . . . . . . . 13 | |||
D.9. Since draft-reschke-http-jfv-05 . . . . . . . . . . . . . 13 | D.9. Since draft-reschke-http-jfv-05 . . . . . . . . . . . . . 13 | |||
D.10. Since draft-reschke-http-jfv-06 . . . . . . . . . . . . . 13 | D.10. Since draft-reschke-http-jfv-06 . . . . . . . . . . . . . 13 | |||
D.11. Since draft-reschke-http-jfv-07 . . . . . . . . . . . . . 13 | D.11. Since draft-reschke-http-jfv-07 . . . . . . . . . . . . . 13 | |||
D.12. Since draft-reschke-http-jfv-08 . . . . . . . . . . . . . 14 | D.12. Since draft-reschke-http-jfv-08 . . . . . . . . . . . . . 14 | |||
D.13. Since draft-reschke-http-jfv-09 . . . . . . . . . . . . . 14 | D.13. Since draft-reschke-http-jfv-09 . . . . . . . . . . . . . 14 | |||
D.14. Since draft-reschke-http-jfv-10 . . . . . . . . . . . . . 14 | D.14. Since draft-reschke-http-jfv-10 . . . . . . . . . . . . . 14 | |||
D.15. Since draft-reschke-http-jfv-11 . . . . . . . . . . . . . 14 | D.15. Since draft-reschke-http-jfv-11 . . . . . . . . . . . . . 14 | |||
D.16. Since draft-reschke-http-jfv-12 . . . . . . . . . . . . . 14 | D.16. Since draft-reschke-http-jfv-12 . . . . . . . . . . . . . 14 | |||
D.17. Since draft-reschke-http-jfv-13 . . . . . . . . . . . . . 14 | D.17. Since draft-reschke-http-jfv-13 . . . . . . . . . . . . . 14 | |||
D.18. Since draft-reschke-http-jfv-14 . . . . . . . . . . . . . 15 | ||||
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 15 | Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
1. Introduction | 1. Introduction | |||
Defining syntax for new HTTP fields ([HTTP], Section 5) is non- | Defining syntax for new HTTP fields ([HTTP], Section 5) is non- | |||
trivial. Among the commonly encountered problems are: | trivial. Among the commonly encountered problems are: | |||
o There is no common syntax for complex field values. Several well- | o There is no common syntax for complex field values. Several well- | |||
known fields do use a similarly looking syntax, but it is hard to | known fields do use a similarly looking syntax, but it is hard to | |||
skipping to change at page 9, line 15 ¶ | skipping to change at page 9, line 15 ¶ | |||
Other than that, any syntax that makes extensions easy can be used to | Other than that, any syntax that makes extensions easy can be used to | |||
smuggle information through field values; however, this concern is | smuggle information through field values; however, this concern is | |||
shared with other widely used formats, such as those using parameters | shared with other widely used formats, such as those using parameters | |||
in the form of name/value pairs. | in the form of name/value pairs. | |||
10. References | 10. References | |||
10.1. Normative References | 10.1. Normative References | |||
[HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
Ed., "HTTP Semantics", Work in Progress, Internet-Draft, | Ed., "HTTP Semantics", RFC 9110, DOI 10.17487/RFC9110, | |||
draft-ietf-httpbis-semantics-15, March 30, 2021, | June 2022, <https://www.rfc-editor.org/info/rfc9110>. | |||
<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis- | ||||
semantics-15>. | ||||
[RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, | [RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, | |||
RFC 20, DOI 10.17487/RFC0020, October 1969, | RFC 20, DOI 10.17487/RFC0020, October 1969, | |||
<https://www.rfc-editor.org/info/rfc20>. | <https://www.rfc-editor.org/info/rfc20>. | |||
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax | [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax | |||
Specifications: ABNF", STD 68, RFC 5234, | Specifications: ABNF", STD 68, RFC 5234, | |||
DOI 10.17487/RFC5234, January 2008, | DOI 10.17487/RFC5234, January 2008, | |||
<https://www.rfc-editor.org/info/rfc5234>. | <https://www.rfc-editor.org/info/rfc5234>. | |||
skipping to change at page 15, line 12 ¶ | skipping to change at page 15, line 12 ¶ | |||
Mention test implementation. | Mention test implementation. | |||
Clarify that Unicode unpaired surrogates or Noncharacters must not be | Clarify that Unicode unpaired surrogates or Noncharacters must not be | |||
sent. | sent. | |||
Rewrite text about [RFC8941], add appendix comparing both formats. | Rewrite text about [RFC8941], add appendix comparing both formats. | |||
And send/receive examples. | And send/receive examples. | |||
D.18. Since draft-reschke-http-jfv-14 | ||||
Update HTTP reference. | ||||
Acknowledgements | Acknowledgements | |||
Thanks go to the Hypertext Transfer Protocol Working Group | Thanks go to the Hypertext Transfer Protocol Working Group | |||
participants. | participants. | |||
Author's Address | Author's Address | |||
Julian F. Reschke | Julian F. Reschke | |||
greenbytes GmbH | greenbytes GmbH | |||
Hafenweg 16 | Hafenweg 16 | |||
End of changes. 8 change blocks. | ||||
10 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |