decrypt-structure.md

Decrypt Structure

Version

1.1.0

Changelog

• 1.1.0

  • Update for simplified structured encryption

• 1.0.0

  • Initial record

Definitions

Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Overview

This document describes the behavior by which a Structured Data which has been encrypted is decrypted. We define decryption over this Structured Data to mean that we obtain back the original Structured Data, and ensure integrity and authenticity is ensured over a set of Terminal Data.

Input

The following inputs to this behavior are REQUIRED:

• Table Name
• Authenticate Schema
• Cryptographic Materials Manager (CMM)
• Encrypted Structured Data

The following inputs to this behavior MUST be OPTIONAL:

• Encryption Context

Output

This operation MUST output the following:

• Structured Data
• Crypto Schema: The Crypto Schema for each signed Terminal, calculated using the Crypto Legend in the header, the signature scope used for decryption, and the data in the input structure.
• Parsed Header

Behavior

The input Structured Data and Authenticate Schema MUST refer to the same set of locations.

The input Structured Data and Authenticate Schema MUST be combined into a single Auth List.

Decrypt Structure MUST then behave as Decrypt Path Structure

The output Crypto List produced by Decrypt Path Structure MUST be split into Structured Data and Crypto Schema maps.