| rfc9205v6.txt | rfc9205.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) M. Nottingham | Internet Engineering Task Force (IETF) M. Nottingham | |||
| Request for Comments: 9205 March 2022 | Request for Comments: 9205 June 2022 | |||
| BCP: 56 | BCP: 56 | |||
| Obsoletes: 3205 | Obsoletes: 3205 | |||
| Category: Best Current Practice | Category: Best Current Practice | |||
| ISSN: 2070-1721 | ISSN: 2070-1721 | |||
| Building Protocols with HTTP | Building Protocols with HTTP | |||
| Abstract | Abstract | |||
| Applications often use HTTP as a substrate to create HTTP-based APIs. | Applications often use HTTP as a substrate to create HTTP-based APIs. | |||
| skipping to change at line 1327 ¶ | skipping to change at line 1327 ¶ | |||
| 7. References | 7. References | |||
| 7.1. Normative References | 7.1. Normative References | |||
| [BCP190] Nottingham, M., "URI Design and Ownership", BCP 190, | [BCP190] Nottingham, M., "URI Design and Ownership", BCP 190, | |||
| RFC 8820, DOI 10.17487/RFC8820, June 2020, | RFC 8820, DOI 10.17487/RFC8820, June 2020, | |||
| <https://www.rfc-editor.org/rfc/rfc8820>. | <https://www.rfc-editor.org/rfc/rfc8820>. | |||
| [HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
| Ed., "HTTP Semantics", RFC 9110, DOI 10.17487/RFC9110, | Ed., "HTTP Semantics", STD 97, RFC 9110, | |||
| March 2022, <https://www.rfc-editor.org/info/rfc9110>. | DOI 10.17487/RFC9110, June 2022, | |||
| <https://www.rfc-editor.org/info/rfc9110>. | ||||
| [HTTP-CACHING] | [HTTP-CACHING] | |||
| Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
| Ed., "HTTP Caching", RFC 9111, DOI 10.17487/RFC9111, March | Ed., "HTTP Caching", STD 98, RFC 9111, | |||
| 2022, <https://www.rfc-editor.org/info/rfc9111>. | DOI 10.17487/RFC9111, June 2022, | |||
| <https://www.rfc-editor.org/info/rfc9111>. | ||||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC6454] Barth, A., "The Web Origin Concept", RFC 6454, | [RFC6454] Barth, A., "The Web Origin Concept", RFC 6454, | |||
| DOI 10.17487/RFC6454, December 2011, | DOI 10.17487/RFC6454, December 2011, | |||
| <https://www.rfc-editor.org/info/rfc6454>. | <https://www.rfc-editor.org/info/rfc6454>. | |||
| skipping to change at line 1396 ¶ | skipping to change at line 1398 ¶ | |||
| Draft, June 2021, | Draft, June 2021, | |||
| <https://www.w3.org/TR/2021/WD-CSP3-20210629>. | <https://www.w3.org/TR/2021/WD-CSP3-20210629>. | |||
| [FETCH] WHATWG, "Fetch - Living Standard", | [FETCH] WHATWG, "Fetch - Living Standard", | |||
| <https://fetch.spec.whatwg.org>. | <https://fetch.spec.whatwg.org>. | |||
| [HTML] WHATWG, "HTML - Living Standard", | [HTML] WHATWG, "HTML - Living Standard", | |||
| <https://html.spec.whatwg.org>. | <https://html.spec.whatwg.org>. | |||
| [HTTP-PRIORITY] | [HTTP-PRIORITY] | |||
| Oku, K. and L. Pardue, "Extensible Prioritization Scheme | 奥 一穂 (Oku, K.) and L. Pardue, "Extensible Prioritization | |||
| for HTTP", Work in Progress, Internet-Draft, draft-ietf- | Scheme for HTTP", RFC 9218, DOI 10.17487/RFC9218, June | |||
| httpbis-priority-12, 18 January 2022, | 2022, <https://www.rfc-editor.org/info/rfc9218>. | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-httpbis- | ||||
| priority-12>. | ||||
| [HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
| Ed., "HTTP/1.1", RFC 9112, DOI 10.17487/RFC9112, March | Ed., "HTTP/1.1", STD 99, RFC 9112, DOI 10.17487/RFC9112, | |||
| 2022, <https://www.rfc-editor.org/info/rfc9112>. | June 2022, <https://www.rfc-editor.org/info/rfc9112>. | |||
| [HTTP/2] Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", Work in | [HTTP/2] Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, | |||
| Progress, Internet-Draft, draft-ietf-httpbis-http2bis-07, | DOI 10.17487/RFC9113, June 2022, | |||
| 24 January 2022, <https://datatracker.ietf.org/doc/html/ | <https://www.rfc-editor.org/info/rfc9113>. | |||
| draft-ietf-httpbis-http2bis-07>. | ||||
| [HTTP/3] Bishop, M., Ed., "Hypertext Transfer Protocol Version 3 | [HTTP/3] Bishop, M., Ed., "HTTP/3", RFC 9114, DOI 10.17487/RFC9114, | |||
| (HTTP/3)", RFC 9114, DOI 10.17487/RFC9114, March 2022, | June 2022, <https://www.rfc-editor.org/info/rfc9114>. | |||
| <https://www.rfc-editor.org/info/rfc9114>. | ||||
| [JSON] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data | [JSON] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data | |||
| Interchange Format", STD 90, RFC 8259, | Interchange Format", STD 90, RFC 8259, | |||
| DOI 10.17487/RFC8259, December 2017, | DOI 10.17487/RFC8259, December 2017, | |||
| <https://www.rfc-editor.org/info/rfc8259>. | <https://www.rfc-editor.org/info/rfc8259>. | |||
| [PROBLEM-DETAILS] | [PROBLEM-DETAILS] | |||
| Nottingham, M. and E. Wilde, "Problem Details for HTTP | Nottingham, M. and E. Wilde, "Problem Details for HTTP | |||
| APIs", RFC 7807, DOI 10.17487/RFC7807, March 2016, | APIs", RFC 7807, DOI 10.17487/RFC7807, March 2016, | |||
| <https://www.rfc-editor.org/info/rfc7807>. | <https://www.rfc-editor.org/info/rfc7807>. | |||
| End of changes. 7 change blocks. | ||||
| 19 lines changed or deleted | 17 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/ | ||||