Resource Digests for HTTP
draft-ietf-httpbis-digest-headers-00

Document Type Active Internet-Draft (httpbis WG)
Last updated 2019-07-04
Stream IETF
Intended RFC status (None)
Formats plain text xml 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)
HTTP                                                            R. Polli
Internet-Draft                         Team Digitale, Italian Government
Intended status: Standards Track                               L. Pardue
Expires: January 5, 2020                                      Cloudflare
                                                           July 04, 2019

                       Resource Digests for HTTP
                  draft-ietf-httpbis-digest-headers-00

Abstract

   This document defines the Digest and Want-Digest header fields for
   HTTP, thus allowing client and server to negotiate an integrity
   checksum of the exchanged resource representation data.

   This document obsoletes RFC 3230.  It replaces the term "instance"
   with "representation", which makes it consistent with the HTTP
   Semantic and Context defined in RFC 7231.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   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/ [1].

   The source code and issues list for this draft can be found at
   https://github.com/httpwg/http-extensions [2].

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 https://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 January 5, 2020.

Polli & Pardue           Expires January 5, 2020                [Page 1]
Internet-Draft          Resource Digests for HTTP              July 2019

Copyright Notice

   Copyright (c) 2019 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
   (https://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.  Brief history of integrity headers  . . . . . . . . . . .   4
     1.2.  This proposal . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Notational Conventions  . . . . . . . . . . . . . . . . .   5
   2.  Resource representation and representation-data . . . . . . .   5
   3.  Digest Algorithm values . . . . . . . . . . . . . . . . . . .   7
     3.1.  Representation digest . . . . . . . . . . . . . . . . . .   9
       3.1.1.  digest-algorithm encoding examples  . . . . . . . . .   9
   4.  Header Specifications . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Want-Digest . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Digest  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  Deprecate Negotiation of Content-MD5  . . . . . . . . . . . .  11
   6.  Broken cryptographic algorithms are NOT RECOMMENDED . . . . .  11
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Unsolicited Digest response . . . . . . . . . . . . . . .  11
       7.1.1.  Representation data is fully contained in the payload  11
       7.1.2.  Representation data is not contained in the payload .  12
       7.1.3.  Representation data is partially contained in the
               payload i.e. range request  . . . . . . . . . . . . .  12
       7.1.4.  Digest in both Request and Response. Returned value
               depends on representation metadata  . . . . . . . . .  13
     7.2.  Want-Digest solicited digest responses  . . . . . . . . .  13
       7.2.1.  Client request data is fully contained in the payload  13
       7.2.2.  A client requests an unsupported Digest, the server
               MAY reply with an unsupported digest  . . . . . . . .  14
       7.2.3.  A client requests an unsupported Digest, the server
               MAY reply with a 400  . . . . . . . . . . . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     8.1.  Digest does not protect the full HTTP message . . . . . .  14
Show full document text