'Out-Of-Band' Content Coding for HTTP
draft-reschke-http-oob-encoding-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-06-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Reschke
Internet-Draft                                                greenbytes
Intended status: Standards Track                               S. Loreto
Expires: December 6, 2015                                       Ericsson
                                                            June 4, 2015

                 'Out-Of-Band' Content Coding for HTTP
                   draft-reschke-http-oob-encoding-00

Abstract

   This document describes an Hypertext Transfer Protocol (HTTP) content
   coding that can be used to describe the location of a secondary
   resource that contans the payload.

Editorial Note (To be removed by RFC Editor before publication)

   Distribution of this document is unlimited.  Although this is not a
   work item of the HTTPbis Working Group, comments should be sent to
   the Hypertext Transfer Protocol (HTTP) mailing list at
   ietf-http-wg@w3.org [1], which may be joined by sending a message
   with subject "subscribe" to ietf-http-wg-request@w3.org [2].

   Discussions of the HTTPbis Working Group are archived at
   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.

   XML versions, latest edits, and issue tracking for this document are
   available from <https://github.com/reschke/oobencoding> and
   <http://greenbytes.de/tech/webdav/#draft-reschke-http-oob-encoding>.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 6, 2015.

Reschke & Loreto        Expires December 6, 2015                [Page 1]
Internet-Draft    'Out-Of-Band' Content Coding for HTTP        June 2015

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  3
   3.  'Out-Of-Band' Content Coding . . . . . . . . . . . . . . . . .  3
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  4
     3.3.  Examples . . . . . . . . . . . . . . . . . . . . . . . . .  5
       3.3.1.  Basic Example  . . . . . . . . . . . . . . . . . . . .  5
       3.3.2.  Example involving an encryted resource . . . . . . . .  7
   4.  Feature Discovery  . . . . . . . . . . . . . . . . . . . . . .  8
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
     5.1.  Use in Requests  . . . . . . . . . . . . . . . . . . . . .  8
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  9
   Appendix A.  Alternatives, or: why not a new Status Code?  . . . . 10
   Appendix B.  Open Issues . . . . . . . . . . . . . . . . . . . . . 10
     B.1.  Range Requests . . . . . . . . . . . . . . . . . . . . . . 10
   Appendix C.  Acknowledgements  . . . . . . . . . . . . . . . . . . 10

Reschke & Loreto        Expires December 6, 2015                [Page 2]
Internet-Draft    'Out-Of-Band' Content Coding for HTTP        June 2015

1.  Introduction

   This document describes an Hypertext Transfer Protocol (HTTP) content
   coding (Section 3.1.2.1 of [RFC7231]) that can be used to describe
   the location of a secondary resource that contans the payload.

   The primary use case for this content coding is to enable origin
   servers to delegate the delivery of content to a secondary server
   that might be "closer" to the client (with respect to network
   topology) and/or able to cache content, leveraging content encrytion,
Show full document text