Architecture and Reference Terminology for Remote Attestation Procedures
draft-birkholz-rats-architecture-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-23
Replaces draft-birkholz-attestation-terminology
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                                        H. Birkholz
Internet-Draft                                            Fraunhofer SIT
Intended status: Standards Track                              M. Wiseman
Expires: April 27, 2019                               GE Global Research
                                                           H. Tschofenig
                                                                ARM Ltd.
                                                                N. Smith
                                                                   Intel
                                                        October 24, 2018

Architecture and Reference Terminology for Remote Attestation Procedures
                  draft-birkholz-rats-architecture-00

Abstract

   Remote ATtestation ProcedureS (RATS), such as Remote Integrity
   VERification (RIVER), the creation of Entity Attestation Tokens
   (EAT), software integrity Measurement And ATtestation (MAAT), or the
   attestation of device characteristics, in general, are based on
   specific operations and qualities provided by hardware and software.
   The RATS architecture maps corresponding functions and operation
   capabilities to specific RATS roles.  The goal is to enable an
   appropriate conveyance of believable evidence about device health or
   trusted claims about device capabilities via network protocols.  The
   flows of data between these roles depend on the composition of RATS
   roles and their location with respect to devices or services.  The
   RATS architecture provides these roles as building blocks to enable
   suitable composition, while remaining hardware-agnostic.  This
   flexibility is intended to address a significant majority of use
   cases or usage scenarios in the domain of RATS.  Examples include,
   but are not limited to: financial transactions, voting machines,
   critical safety systems, network equipment health, or trustworthy
   end-user device management.

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

Birkholz, et al.         Expires April 27, 2019                 [Page 1]
Internet-Draft              RATS Arch & Terms               October 2018

   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 April 27, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  RATS Architecture . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Roles, Devices, and Services  . . . . . . . . . . . . . .   4
     2.2.  Trust and Trustworthiness . . . . . . . . . . . . . . . .   5
     2.3.  Claims and Evidence . . . . . . . . . . . . . . . . . . .   6
     2.4.  RATS Roles  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.5.  Exemplary Composition of Roles  . . . . . . . . . . . . .   8
       2.5.1.  Conveyance of Trusted Claim Sets Validated by
               Signature . . . . . . . . . . . . . . . . . . . . . .   8
       2.5.2.  Conveyance of Attestation Evidence Appraised by a
               Verifier  . . . . . . . . . . . . . . . . . . . . . .   9
     2.6.  The Scope of RATS . . . . . . . . . . . . . . . . . . . .   9
       2.6.1.  The Lying Endpoint Problem  . . . . . . . . . . . . .  10
       2.6.2.  How the RATS Architecture Addresses the Lying
               Endpoint Problem  . . . . . . . . . . . . . . . . . .  11
   3.  RATS Terminology  . . . . . . . . . . . . . . . . . . . . . .  11
     3.1.  Computing Context . . . . . . . . . . . . . . . . . . . .  12
       3.1.1.  Characteristics of a Computing Context  . . . . . . .  13
       3.1.2.  Computing Context Semantic Relationships  . . . . . .  14
Show full document text