draft-ietf-httpbis-encryption-encoding-09.txt   draft-ietf-httpbis-encryption-encoding-latest.txt 
HTTP Working Group M. Thomson HTTP Working Group M. Thomson
Internet-Draft Mozilla Internet-Draft Mozilla
Intended status: Standards Track April 18, 2017 Intended status: Standards Track August 9, 2017
Expires: October 20, 2017 Expires: February 10, 2018
Encrypted Content-Encoding for HTTP Encrypted Content-Encoding for HTTP
draft-ietf-httpbis-encryption-encoding-09 draft-ietf-httpbis-encryption-encoding-latest
Abstract Abstract
This memo introduces a content coding for HTTP that allows message This memo introduces a content coding for HTTP that allows message
payloads to be encrypted. payloads to be encrypted.
Note to Readers Note to Readers
Discussion of this draft takes place on the HTTP working group Discussion of this draft takes place on the HTTP working group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 October 20, 2017. This Internet-Draft will expire on February 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 2, line 51 skipping to change at page 2, line 51
1. Introduction 1. Introduction
It is sometimes desirable to encrypt the contents of a HTTP message It is sometimes desirable to encrypt the contents of a HTTP message
(request or response) so that when the payload is stored (e.g., with (request or response) so that when the payload is stored (e.g., with
a HTTP PUT), only someone with the appropriate key can read it. a HTTP PUT), only someone with the appropriate key can read it.
For example, it might be necessary to store a file on a server For example, it might be necessary to store a file on a server
without exposing its contents to that server. Furthermore, that same without exposing its contents to that server. Furthermore, that same
file could be replicated to other servers (to make it more resistant file could be replicated to other servers (to make it more resistant
to server or network failure), downloaded by clients (to make it to server or network failure), downloaded by clients (to make it
available offline), etc. without exposing its contents. available offline), etc. without exposing its contents.
These uses are not met by the use of TLS [RFC5246], since it only These uses are not met by the use of TLS [RFC5246], since it only
encrypts the channel between the client and server. encrypts the channel between the client and server.
This document specifies a content coding (Section 3.1.2 of [RFC7231]) This document specifies a content coding (Section 3.1.2 of [RFC7231])
for HTTP to serve these and other use cases. for HTTP to serve these and other use cases.
This content coding is not a direct adaptation of message-based This content coding is not a direct adaptation of message-based
encryption formats - such as those that are described by [RFC4880], encryption formats - such as those that are described by [RFC4880],
[RFC5652], [RFC7516], and [XMLENC] - which are not suited to stream [RFC5652], [RFC7516], and [XMLENC] - which are not suited to stream
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 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/