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 10, 2018 Ericsson
June 24, 2017 July 9, 2017
'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 http://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 10, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (http://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
skipping to change at page 3, line 27 skipping to change at page 3, line 27
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 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. 8 change blocks. 
6 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/