Time-Based Uni-Directional Attestation
draft-birkholz-rats-tuda-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

RATS Working Group                                              A. Fuchs
Internet-Draft                                               H. Birkholz
Intended status: Standards Track                          Fraunhofer SIT
Expires: March 15, 2020                                      I. McDonald
                                                          High North Inc
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                      September 12, 2019

                 Time-Based Uni-Directional Attestation
                      draft-birkholz-rats-tuda-01

Abstract

   This documents defines the method and bindings used to conduct Time-
   based Uni-Directional Attestation (TUDA) between two RATS (Remote
   ATtestation procedureS) Principals over the Internet.  TUDA does not
   require a challenge-response handshake and thereby does not rely on
   the conveyance of a nonce to prove freshness of remote attestation
   Evidence.  Conversely, TUDA enables the creation of Secure Audit Logs
   that can constitute Evidence about current and past operational
   states of an Attester.  As a prerequisite for TUDA, every RATS
   Principal requires access to a trusted and synchronized time-source.
   Per default, in TUDA this is a Time Stamp Authority (TSA) issuing
   signed Time Stamp Tokens (TST).

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 March 15, 2020.

Fuchs, et al.            Expires March 15, 2020                 [Page 1]
Internet-Draft                    TUDA                    September 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.  Requirements Notation . . . . . . . . . . . . . . . . . .   4
     1.2.  Evidence  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Creating Evidence about Software Component Integrity  . .   5
       1.3.1.  Data Items  . . . . . . . . . . . . . . . . . . . . .   5
       1.3.2.  System Components . . . . . . . . . . . . . . . . . .   5
       1.3.3.  Operations  . . . . . . . . . . . . . . . . . . . . .   6
     1.4.  Remote Attestation Principles . . . . . . . . . . . . . .   6
     1.5.  System Component Requirements . . . . . . . . . . . . . .   7
     1.6.  Evidence Appraisal  . . . . . . . . . . . . . . . . . . .   7
     1.7.  Activities and Actions  . . . . . . . . . . . . . . . . .   8
     1.8.  Attestation and Verification  . . . . . . . . . . . . . .   8
     1.9.  Information Elements and Conveyance . . . . . . . . . . .   8
     1.10. TUDA Objectives . . . . . . . . . . . . . . . . . . . . .   9
     1.11. Hardware Dependencies . . . . . . . . . . . . . . . . . .  10
   2.  TUDA Core Concept . . . . . . . . . . . . . . . . . . . . . .  10
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .  11
     3.1.  Universal Terms . . . . . . . . . . . . . . . . . . . . .  11
     3.2.  Roles . . . . . . . . . . . . . . . . . . . . . . . . . .  13
       3.2.1.  General Types . . . . . . . . . . . . . . . . . . . .  13
       3.2.2.  RoT specific terms  . . . . . . . . . . . . . . . . .  13
     3.3.  Certificates  . . . . . . . . . . . . . . . . . . . . . .  13
   4.  Time-Based Uni-Directional Attestation  . . . . . . . . . . .  13
     4.1.  TUDA Information Elements Update Cycles . . . . . . . . .  15
   5.  Sync Base Protocol  . . . . . . . . . . . . . . . . . . . . .  17
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  18