Browse Prior Art Database

Encrypted Content-Encoding for HTTP (RFC8188)

IP.com Disclosure Number: IPCOM000250300D
Original Publication Date: 2017-Jun-01
Included in the Prior Art Database: 2017-Jun-24
Document File: 32 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Thomson: AUTHOR

Abstract

It is sometimes desirable to encrypt the contents of an HTTP message (request or response) so that when the payload is stored (e.g., with an HTTP PUT), only someone with the appropriate key can read it.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                        M. Thomson Request for Comments: 8188                                       Mozilla Category: Standards Track                                      June 2017 ISSN: 2070-1721

                   Encrypted Content-Encoding for HTTP

Abstract

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

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8188.

Copyright Notice

   Copyright (c) 2017 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                      Standards Track                    [Page 1]
 RFC 8188                 HTTP Encryption Coding                June 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3

   2.  The "aes128gcm" HTTP Content Coding . . . . . . . . . . . . .   3

     2.1.  Encryption Content-Coding Header  . . . . . . . . . . . .   5

     2.2.  Content-Encryption Key Derivation . . . . . . . . . . . .   6

     2.3.  Nonce Derivation  . . . . . . . . . . . . . . . . . . . .   6

   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7

     3.1.  Encryption of a Response  . . . . . . . . . . . . . . . .   7

     3.2.  Encryption with Multiple Records  . . . . . . . . . . . .   8

   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8

     4.1.  Automatic Decryption  . . . . . . . . . . . . . . . . . .   9

     4.2.  Message T...