Reference Terminology for Attestation Procedures
draft-birkholz-attestation-terminology-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
Replaced by draft-birkholz-rats-architecture
Stream (None)
Intended RFC status (None)
Formats plain text 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: Informational                                M. Wiseman
Expires: January 5, 2018                              GE Global Research
                                                           H. Tschofenig
                                                                ARM Ltd.
                                                           July 04, 2017

            Reference Terminology for Attestation Procedures
               draft-birkholz-attestation-terminology-00

Abstract

   This document is intended to illustrate and remediate the impedance
   mismatch of terms related to attestation procedures used in different
   domains today.  New terms defined by this document provide a
   consolidated basis to support future work on attestation procedures
   in the IETF and beyond.

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 http://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, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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

Birkholz, et al.         Expires January 5, 2018                [Page 1]
Internet-Draft              term-attestation                   July 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  Basic Attestation Roles . . . . . . . . . . . . . . . . . . .   3
   3.  Computing Context . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Formal Semantic Relationships . . . . . . . . . . . . . .   5
     3.2.  Characteristics of a computing context  . . . . . . . . .   6
   4.  Computing Context Identity  . . . . . . . . . . . . . . . . .   6
   5.  Attestation Workflow  . . . . . . . . . . . . . . . . . . . .   7
   6.  Reference Use Cases . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  The Lying Endpoint Problem  . . . . . . . . . . . . . . .   9
     6.2.  Who am I a talking to?  . . . . . . . . . . . . . . . . .  10
   7.  Trustworthiness . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Remote Attestation  . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Building Block Terms  . . . . . . . . . . . . . . . . . .  11
   9.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  12
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   12. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     13.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Over the years, the term attestation has been used in multiple
   contexts and multiple scopes and therefore accumulated various
   connotations with slightly different semantic meaning.

   In order to better understand and grasp the intend and meaning of
   specific attestation procedures in the security area - including the
   requirements that are addressed by them - this document provides an
   overview of existing work, its background, and common terminology.
   As the contribution, from that state-of-the-art a set of terms that
   provides a stable basis for future work on attestation procedures in
   the IETF is derived.

   The primary application of attestation procedures is to increase the
   trust and confidence in the integrity of the characteristics and
   properties of an entity that intends to provide data to other
Show full document text