| draft-reschke-http-oob-encoding-12.txt | draft-reschke-http-oob-encoding-latest.txt | |||
|---|---|---|---|---|
| Network Working Group J. Reschke | Network Working Group J. Reschke | |||
| Internet-Draft greenbytes | Internet-Draft greenbytes | |||
| Intended status: Standards Track S. Loreto | Intended status: Standards Track S. Loreto | |||
| Expires: December 26, 2017 Ericsson | Expires: January 7, 2025 Ericsson | |||
| June 24, 2017 | July 6, 2024 | |||
| 'Out-Of-Band' Content Coding for HTTP | 'Out-Of-Band' Content Coding for HTTP | |||
| draft-reschke-http-oob-encoding-12 | draft-reschke-http-oob-encoding-latest | |||
| Abstract | Abstract | |||
| This document describes an Hypertext Transfer Protocol (HTTP) content | This document describes an Hypertext Transfer Protocol (HTTP) content | |||
| coding that can be used to describe the location of a secondary | coding that can be used to describe the location of a secondary | |||
| resource that contains the payload. | resource that contains the payload. | |||
| Editorial Note (To be removed by RFC Editor before publication) | Editorial Note (To be removed by RFC Editor before publication) | |||
| Distribution of this document is unlimited. Although this is not a | Distribution of this document is unlimited. Although this is not a | |||
| skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
| "subscribe" to ietf-http-wg-request@w3.org [2]. | "subscribe" to ietf-http-wg-request@w3.org [2]. | |||
| 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, latest edits, and issue tracking for this document are | XML versions, latest edits, and issue tracking for this document are | |||
| available from <https://github.com/EricssonResearch/Blind-Cache- | available from <https://github.com/EricssonResearch/Blind-Cache- | |||
| Drafts> and <http://greenbytes.de/tech/webdav/#draft-reschke-http- | Drafts> and <http://greenbytes.de/tech/webdav/#draft-reschke-http- | |||
| oob-encoding>. | oob-encoding>. | |||
| The changes in this draft are summarized in Appendix D.12. | The changes in this draft are summarized in Appendix D.13. | |||
| 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 http://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 December 26, 2017. | This Internet-Draft will expire on January 7, 2025. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2024 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 | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| skipping to change at page 3, line 28 ¶ | skipping to change at page 3, line 28 ¶ | |||
| D.3. Changes since draft-reschke-http-oob-encoding-02 . . . . 22 | D.3. Changes since draft-reschke-http-oob-encoding-02 . . . . 22 | |||
| D.4. Changes since draft-reschke-http-oob-encoding-03 . . . . 22 | D.4. Changes since draft-reschke-http-oob-encoding-03 . . . . 22 | |||
| D.5. Changes since draft-reschke-http-oob-encoding-04 . . . . 23 | D.5. Changes since draft-reschke-http-oob-encoding-04 . . . . 23 | |||
| D.6. Changes since draft-reschke-http-oob-encoding-05 . . . . 23 | D.6. Changes since draft-reschke-http-oob-encoding-05 . . . . 23 | |||
| D.7. Changes since draft-reschke-http-oob-encoding-06 . . . . 23 | D.7. Changes since draft-reschke-http-oob-encoding-06 . . . . 23 | |||
| D.8. Changes since draft-reschke-http-oob-encoding-07 . . . . 24 | D.8. Changes since draft-reschke-http-oob-encoding-07 . . . . 24 | |||
| D.9. Changes since draft-reschke-http-oob-encoding-08 . . . . 24 | D.9. Changes since draft-reschke-http-oob-encoding-08 . . . . 24 | |||
| D.10. Changes since draft-reschke-http-oob-encoding-09 . . . . 24 | D.10. Changes since draft-reschke-http-oob-encoding-09 . . . . 24 | |||
| D.11. Changes since draft-reschke-http-oob-encoding-10 . . . . 24 | D.11. Changes since draft-reschke-http-oob-encoding-10 . . . . 24 | |||
| D.12. Changes since draft-reschke-http-oob-encoding-11 . . . . 24 | D.12. Changes since draft-reschke-http-oob-encoding-11 . . . . 24 | |||
| D.13. Changes since draft-reschke-http-oob-encoding-12 . . . . 24 | ||||
| Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 24 | Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 24 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 | |||
| 1. Introduction | 1. Introduction | |||
| This document describes an Hypertext Transfer Protocol (HTTP) content | This document describes an Hypertext Transfer Protocol (HTTP) content | |||
| coding (Section 3.1.2.1 of [RFC7231]) that can be used to describe | coding (Section 3.1.2.1 of [RFC7231]) that can be used to describe | |||
| the location of a secondary resource that contains the payload. | the location of a secondary resource that contains the payload. | |||
| The primary use case for this content coding is to enable origin | The primary use case for this content coding is to enable origin | |||
| servers to securely delegate the delivery of content to a secondary | servers to securely delegate the delivery of content to a secondary | |||
| server that might be "closer" to the client (with respect to network | server that might be "closer" to the client (with respect to network | |||
| skipping to change at page 15, line 23 ¶ | skipping to change at page 15, line 23 ¶ | |||
| Change controller: IESG | Change controller: IESG | |||
| 8. References | 8. References | |||
| 8.1. Normative References | 8.1. Normative References | |||
| [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, | |||
| <http://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform | [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform | |||
| Resource Identifier (URI): Generic Syntax", STD 66, | Resource Identifier (URI): Generic Syntax", STD 66, | |||
| RFC 3986, DOI 10.17487/RFC3986, January 2005, | RFC 3986, DOI 10.17487/RFC3986, January 2005, | |||
| <http://www.rfc-editor.org/info/rfc3986>. | <https://www.rfc-editor.org/info/rfc3986>. | |||
| [RFC5988] Nottingham, M., "Web Linking", RFC 5988, | [RFC5988] Nottingham, M., "Web Linking", RFC 5988, | |||
| DOI 10.17487/RFC5988, October 2010, | DOI 10.17487/RFC5988, October 2010, | |||
| <http://www.rfc-editor.org/info/rfc5988>. | <https://www.rfc-editor.org/info/rfc5988>. | |||
| [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | |||
| DOI 10.17487/RFC6265, April 2011, | DOI 10.17487/RFC6265, April 2011, | |||
| <http://www.rfc-editor.org/info/rfc6265>. | <https://www.rfc-editor.org/info/rfc6265>. | |||
| [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data | [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data | |||
| Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March | Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March | |||
| 2014, <http://www.rfc-editor.org/info/rfc7159>. | 2014, <https://www.rfc-editor.org/info/rfc7159>. | |||
| [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
| Protocol (HTTP/1.1): Message Syntax and Routing", | Protocol (HTTP/1.1): Message Syntax and Routing", | |||
| RFC 7230, DOI 10.17487/RFC7230, June 2014, | RFC 7230, DOI 10.17487/RFC7230, June 2014, | |||
| <http://www.rfc-editor.org/info/rfc7230>. | <https://www.rfc-editor.org/info/rfc7230>. | |||
| [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
| Protocol (HTTP/1.1): Semantics and Content", RFC 7231, | Protocol (HTTP/1.1): Semantics and Content", RFC 7231, | |||
| DOI 10.17487/RFC7231, June 2014, | DOI 10.17487/RFC7231, June 2014, | |||
| <http://www.rfc-editor.org/info/rfc7231>. | <https://www.rfc-editor.org/info/rfc7231>. | |||
| [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
| Protocol (HTTP/1.1): Authentication", RFC 7235, | Protocol (HTTP/1.1): Authentication", RFC 7235, | |||
| DOI 10.17487/RFC7235, June 2014, | DOI 10.17487/RFC7235, June 2014, | |||
| <http://www.rfc-editor.org/info/rfc7235>. | <https://www.rfc-editor.org/info/rfc7235>. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type | [BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type | |||
| Specifications and Registration Procedures", BCP 13, | Specifications and Registration Procedures", BCP 13, | |||
| RFC 6838, January 2013, | RFC 6838, January 2013, | |||
| <http://www.rfc-editor.org/info/bcp13>. | <https://www.rfc-editor.org/info/bcp13>. | |||
| [CONTENTSIG] | [CONTENTSIG] | |||
| Thomson, M., "Content-Signature Header Field for HTTP", | Thomson, M., "Content-Signature Header Field for HTTP", | |||
| draft-thomson-http-content-signature-00 (work in | draft-thomson-http-content-signature-00 (work in | |||
| progress), July 2015. | progress), July 2015. | |||
| [CORS] van Kesteren, A., "Cross-Origin Resource Sharing", W3C | [CORS] van Kesteren, A., "Cross-Origin Resource Sharing", W3C | |||
| Recommendation REC-cors-20140116, January 2014, | Recommendation REC-cors-20140116, January 2014, | |||
| <http://www.w3.org/TR/2014/REC-cors-20140116/>. | <http://www.w3.org/TR/2014/REC-cors-20140116/>. | |||
| Latest version available at <http://www.w3.org/TR/cors/>. | Latest version available at <http://www.w3.org/TR/cors/>. | |||
| [MICE] Thomson, M., "Merkle Integrity Content Encoding", draft- | [MICE] Thomson, M., "Merkle Integrity Content Encoding", draft- | |||
| thomson-http-mice-02 (work in progress), October 2016. | thomson-http-mice-02 (work in progress), October 2016. | |||
| [RFC2017] Freed, N. and K. Moore, "Definition of the URL MIME | [RFC2017] Freed, N. and K. Moore, "Definition of the URL MIME | |||
| External-Body Access-Type", RFC 2017, | External-Body Access-Type", RFC 2017, | |||
| DOI 10.17487/RFC2017, October 1996, | DOI 10.17487/RFC2017, October 1996, | |||
| <http://www.rfc-editor.org/info/rfc2017>. | <https://www.rfc-editor.org/info/rfc2017>. | |||
| [RFC4483] Burger, E., "A Mechanism for Content Indirection in | [RFC4483] Burger, E., "A Mechanism for Content Indirection in | |||
| Session Initiation Protocol (SIP) Messages", RFC 4483, | Session Initiation Protocol (SIP) Messages", RFC 4483, | |||
| DOI 10.17487/RFC4483, May 2006, | DOI 10.17487/RFC4483, May 2006, | |||
| <http://www.rfc-editor.org/info/rfc4483>. | <https://www.rfc-editor.org/info/rfc4483>. | |||
| [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data | [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data | |||
| Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, | Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, | |||
| <http://www.rfc-editor.org/info/rfc4648>. | <https://www.rfc-editor.org/info/rfc4648>. | |||
| [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security | [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security | |||
| (TLS) Protocol Version 1.2", RFC 5246, | (TLS) Protocol Version 1.2", RFC 5246, | |||
| DOI 10.17487/RFC5246, August 2008, | DOI 10.17487/RFC5246, August 2008, | |||
| <http://www.rfc-editor.org/info/rfc5246>. | <https://www.rfc-editor.org/info/rfc5246>. | |||
| [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, | |||
| <http://www.rfc-editor.org/info/rfc6454>. | <https://www.rfc-editor.org/info/rfc6454>. | |||
| [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
| Protocol (HTTP/1.1): Conditional Requests", RFC 7232, | Protocol (HTTP/1.1): Conditional Requests", RFC 7232, | |||
| DOI 10.17487/RFC7232, June 2014, | DOI 10.17487/RFC7232, June 2014, | |||
| <http://www.rfc-editor.org/info/rfc7232>. | <https://www.rfc-editor.org/info/rfc7232>. | |||
| [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., | [RFC7233] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., | |||
| "Hypertext Transfer Protocol (HTTP/1.1): Range Requests", | "Hypertext Transfer Protocol (HTTP/1.1): Range Requests", | |||
| RFC 7233, DOI 10.17487/RFC7233, June 2014, | RFC 7233, DOI 10.17487/RFC7233, June 2014, | |||
| <http://www.rfc-editor.org/info/rfc7233>. | <https://www.rfc-editor.org/info/rfc7233>. | |||
| [RFC8188] Thomson, M., "Encrypted Content-Encoding for HTTP", | [RFC8188] Thomson, M., "Encrypted Content-Encoding for HTTP", | |||
| RFC 8188, DOI 10.17487/RFC8188, June 2017, | RFC 8188, DOI 10.17487/RFC8188, June 2017, | |||
| <http://www.rfc-editor.org/info/rfc8188>. | <https://www.rfc-editor.org/info/rfc8188>. | |||
| [RMAP] Eriksson, G., Holmberg, C., Sarker, Z., and J. Reschke, | [RMAP] Eriksson, G., Holmberg, C., Sarker, Z., and J. Reschke, | |||
| "Resource Maps", draft-eriksson-http-resource-map-00 (work | "Resource Maps", draft-eriksson-http-resource-map-00 (work | |||
| in progress), October 2016. | in progress), October 2016. | |||
| [SCD] Thomson, M., Eriksson, G., and C. Holmberg, "An | [SCD] Thomson, M., Eriksson, G., and C. Holmberg, "An | |||
| Architecture for Secure Content Delegation using HTTP", | Architecture for Secure Content Delegation using HTTP", | |||
| draft-thomson-http-scd-02 (work in progress), October | draft-thomson-http-scd-02 (work in progress), October | |||
| 2016. | 2016. | |||
| skipping to change at page 24, line 40 ¶ | skipping to change at page 24, line 40 ¶ | |||
| Updated reference for ENCRYPTENC: instead of using Crypto-Key | Updated reference for ENCRYPTENC: instead of using Crypto-Key | |||
| response header field move the key material into the OOB payload. | response header field move the key material into the OOB payload. | |||
| D.12. Changes since draft-reschke-http-oob-encoding-11 | D.12. Changes since draft-reschke-http-oob-encoding-11 | |||
| Removed note about registration of purl URIs for link relations. | Removed note about registration of purl URIs for link relations. | |||
| Updated reference for ENCRYPTENC (now RFC 8188). | Updated reference for ENCRYPTENC (now RFC 8188). | |||
| D.13. Changes since draft-reschke-http-oob-encoding-12 | ||||
| None yet. | ||||
| Acknowledgements | Acknowledgements | |||
| Thanks to Christer Holmberg, Daniel Lindstrom, Erik Nygren, Goran | Thanks to Christer Holmberg, Daniel Lindstrom, Erik Nygren, Goran | |||
| Eriksson, John Mattsson, Kevin Smith, Magnus Westerlund, Mark | Eriksson, John Mattsson, Kevin Smith, Magnus Westerlund, Mark | |||
| Nottingham, Martin Thomson, and Roland Zink for feedback on this | Nottingham, Martin Thomson, and Roland Zink for feedback on this | |||
| document. | document. | |||
| Authors' Addresses | Authors' Addresses | |||
| Julian F. Reschke | Julian F. Reschke | |||
| greenbytes GmbH | greenbytes GmbH | |||
| Hafenweg 16 | Hafenweg 16 | |||
| Muenster, NW 48155 | Muenster, NW 48155 | |||
| Germany | Germany | |||
| EMail: julian.reschke@greenbytes.de | EMail: julian.reschke@greenbytes.de | |||
| URI: http://greenbytes.de/tech/webdav/ | URI: http://greenbytes.de/tech/webdav/ | |||
| Salvatore Loreto | Salvatore Loreto | |||
| End of changes. 28 change blocks. | ||||
| 26 lines changed or deleted | 32 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/ | ||||