Encrypted Content-Encoding for HTTP
draft-ietf-httpbis-encryption-encoding-03

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2016-10-09
Replaces draft-thomson-http-encryption
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Mark Nottingham
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Mark Nottingham" <mnot@mnot.net>
HTTP Working Group                                            M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                         October 9, 2016
Expires: April 12, 2017

                  Encrypted Content-Encoding for HTTP
               draft-ietf-httpbis-encryption-encoding-03

Abstract

   This memo introduces a content coding for HTTP that allows message
   payloads to be encrypted.

Note to Readers

   Discussion of this draft takes place on the HTTP working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   https://lists.w3.org/Archives/Public/ietf-http-wg/ .

   Working Group information can be found at http://httpwg.github.io/ ;
   source code and issues list for this draft can be found at
   https://github.com/httpwg/http-extensions/labels/encryption .

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 April 12, 2017.

Copyright Notice

   Copyright (c) 2016 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

Thomson                  Expires April 12, 2017                 [Page 1]
Internet-Draft           HTTP encryption coding             October 2016

   (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
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  The "aesgcm" HTTP Content Coding  . . . . . . . . . . . . . .   4
   3.  The Encryption HTTP Header Field  . . . . . . . . . . . . . .   6
     3.1.  Encryption Header Field Parameters  . . . . . . . . . . .   6
     3.2.  Content Encryption Key Derivation . . . . . . . . . . . .   7
     3.3.  Nonce Derivation  . . . . . . . . . . . . . . . . . . . .   8
   4.  Crypto-Key Header Field . . . . . . . . . . . . . . . . . . .   8
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Encryption of a Response  . . . . . . . . . . . . . . . .   9
     5.2.  Encryption with Multiple Records  . . . . . . . . . . . .  10
     5.3.  Encryption and Compression  . . . . . . . . . . . . . . .  10
     5.4.  Encryption with More Than One Key . . . . . . . . . . . .  11
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
     6.1.  Key and Nonce Reuse . . . . . . . . . . . . . . . . . . .  11
     6.2.  Data Encryption Limits  . . . . . . . . . . . . . . . . .  12
     6.3.  Content Integrity . . . . . . . . . . . . . . . . . . . .  12
     6.4.  Leaking Information in Headers  . . . . . . . . . . . . .  12
     6.5.  Poisoning Storage . . . . . . . . . . . . . . . . . . . .  13
     6.6.  Sizing and Timing Attacks . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  The "aesgcm" HTTP Content Coding  . . . . . . . . . . . .  13
     7.2.  Encryption Header Fields  . . . . . . . . . . . . . . . .  14
     7.3.  The HTTP Encryption Parameter Registry  . . . . . . . . .  14
       7.3.1.  keyid . . . . . . . . . . . . . . . . . . . . . . . .  15
       7.3.2.  salt  . . . . . . . . . . . . . . . . . . . . . . . .  15
       7.3.3.  rs  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     7.4.  The HTTP Crypto-Key Parameter Registry  . . . . . . . . .  15
       7.4.1.  keyid . . . . . . . . . . . . . . . . . . . . . . . .  16
       7.4.2.  aesgcm  . . . . . . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Appendix A.  JWE Mapping  . . . . . . . . . . . . . . . . . . . .  18
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .  19
Show full document text