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

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2015-12-23
Replaces draft-thomson-http-encryption
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         M. Thomson
Internet-Draft                                                   Mozilla
Intended status: Standards Track                       December 22, 2015
Expires: June 24, 2016

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

Abstract

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

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 June 24, 2016.

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.

Thomson                   Expires June 24, 2016                 [Page 1]
Internet-Draft           HTTP encryption coding            December 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  The "aesgcm128" HTTP Content Encoding . . . . . . . . . . . .   3
   3.  The Encryption HTTP Header Field  . . . . . . . . . . . . . .   5
     3.1.  Encryption Header Field Parameters  . . . . . . . . . . .   6
     3.2.  Content Encryption Key Derivation . . . . . . . . . . . .   6
     3.3.  Nonce Derivation  . . . . . . . . . . . . . . . . . . . .   7
   4.  Crypto-Key Header Field . . . . . . . . . . . . . . . . . . .   8
     4.1.  Explicit Key  . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Diffie-Hellman  . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Pre-shared Authentication Secrets . . . . . . . . . . . .  10
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.1.  Successful GET Response . . . . . . . . . . . . . . . . .  11
     5.2.  Encryption and Compression  . . . . . . . . . . . . . . .  11
     5.3.  Encryption with More Than One Key . . . . . . . . . . . .  11
     5.4.  Encryption with Explicit Key  . . . . . . . . . . . . . .  12
     5.5.  Diffie-Hellman Encryption . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
     6.1.  Key and Nonce Reuse . . . . . . . . . . . . . . . . . . .  13
     6.2.  Content Integrity . . . . . . . . . . . . . . . . . . . .  13
     6.3.  Leaking Information in Headers  . . . . . . . . . . . . .  14
     6.4.  Poisoning Storage . . . . . . . . . . . . . . . . . . . .  14
     6.5.  Sizing and Timing Attacks . . . . . . . . . . . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     7.1.  The "aesgcm128" HTTP Content Encoding . . . . . . . . . .  15
     7.2.  Encryption Header Fields  . . . . . . . . . . . . . . . .  15
     7.3.  The HTTP Encryption Parameter Registry  . . . . . . . . .  16
       7.3.1.  keyid . . . . . . . . . . . . . . . . . . . . . . . .  16
       7.3.2.  salt  . . . . . . . . . . . . . . . . . . . . . . . .  16
       7.3.3.  rs  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     7.4.  The HTTP Crypto-Key Parameter Registry  . . . . . . . . .  17
       7.4.1.  keyid . . . . . . . . . . . . . . . . . . . . . . . .  17
       7.4.2.  aesgcm128 . . . . . . . . . . . . . . . . . . . . . .  17
       7.4.3.  dh  . . . . . . . . . . . . . . . . . . . . . . . . .  18
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  19
   Appendix A.  JWE Mapping  . . . . . . . . . . . . . . . . . . . .  20
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .  21
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   It is sometimes desirable to encrypt the contents of a HTTP message
Show full document text