Data At Rest Encryption Part 1: DARE Message Syntax
draft-hallambaker-dare-message-02

Document Type Active Internet-Draft (individual)
Last updated 2018-08-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    P. Hallam-Baker
Internet-Draft                                         Comodo Group Inc.
Intended status: Informational                           August 27, 2018
Expires: February 28, 2019

          Data At Rest Encryption Part 1: DARE Message Syntax
                   draft-hallambaker-dare-message-02

Abstract

   This document describes the Data At Rest Encryption (DARE) message
   syntax.  This syntax is used to digitally sign, digest, authenticate,
   or encrypt arbitrary message content.

   This document is also available online at
   http://mathmesh.com/Documents/draft-hallambaker-dare-message.html [1]
   .

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 February 28, 2019.

Copyright Notice

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

Hallam-Baker            Expires February 28, 2019               [Page 1]
Internet-Draft                DARE Message                   August 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Encryption and Integrity  . . . . . . . . . . . . . . . .   3
       1.1.1.  Key Exchange  . . . . . . . . . . . . . . . . . . . .   4
       1.1.2.  Data Erasure  . . . . . . . . . . . . . . . . . . . .   5
     1.2.  Signature . . . . . . . . . . . . . . . . . . . . . . . .   5
       1.2.1.  Signing Individual Plaintext Messages . . . . . . . .   6
       1.2.2.  Signing Individual Encrypted Messages . . . . . . . .   6
       1.2.3.  Signing Sequences of Messages . . . . . . . . . . . .   6
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Related Specifications  . . . . . . . . . . . . . . . . .   7
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   7
     2.3.  Defined terms . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Processing Considerations . . . . . . . . . . . . . . . .   9
     3.2.  Content Metadata and Annotations  . . . . . . . . . . . .  10
     3.3.  Encoded Data Sequence . . . . . . . . . . . . . . . . . .  11
     3.4.  Encryption and Integrity  . . . . . . . . . . . . . . . .  12
       3.4.1.  Key Exchange  . . . . . . . . . . . . . . . . . . . .  13
       3.4.2.  Key Identifiers . . . . . . . . . . . . . . . . . . .  14
       3.4.3.  Salt Derivation . . . . . . . . . . . . . . . . . . .  14
       3.4.4.  Key Derivation  . . . . . . . . . . . . . . . . . . .  15
     3.5.  Signature . . . . . . . . . . . . . . . . . . . . . . . .  16
   4.  Algorithms  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     4.1.  Field: kwd  . . . . . . . . . . . . . . . . . . . . . . .  16
   5.  Reference . . . . . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  Message Classes . . . . . . . . . . . . . . . . . . . . .  17
       5.1.1.  Structure: DAREMessageSequence  . . . . . . . . . . .  17
     5.2.  Header and Trailer Classes  . . . . . . . . . . . . . . .  17
       5.2.1.  Structure: DARETrailer  . . . . . . . . . . . . . . .  17
       5.2.2.  Structure: DAREHeader . . . . . . . . . . . . . . . .  18
     5.3.  Cryptographic Data  . . . . . . . . . . . . . . . . . . .  18
       5.3.1.  Structure: DARESigner . . . . . . . . . . . . . . . .  19
       5.3.2.  Structure: X509Certificate  . . . . . . . . . . . . .  19
       5.3.3.  Structure: DARESignature  . . . . . . . . . . . . . .  19
       5.3.4.  Structure: DARERecipient  . . . . . . . . . . . . . .  19
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
     6.1.  Encryption/Signature nesting  . . . . . . . . . . . . . .  20
     6.2.  Side channel  . . . . . . . . . . . . . . . . . . . . . .  20
Show full document text