Use cases for Remote Attestation common encodings
draft-richardson-rats-usecases-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
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)
RATS Working Group                                         M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Informational                            March 11, 2019
Expires: September 12, 2019

           Use cases for Remote Attestation common encodings
                   draft-richardson-rats-usecases-00

Abstract

   This document details mechanisms created for performing Remote
   Attestation that have been used in a number of industries.  The
   document intially focuses on existing industry verticals, mapping
   terminology used in those specifications to the more abstract
   terminology used by RATS.

   The document (aspires) goes on to go on to describe possible future
   use cases that would be enabled by common formats.

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 September 12, 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

Richardson             Expires September 12, 2019               [Page 1]
Internet-Draft                 useful RATS                    March 2019

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   4.  Overview of Sources of Use Cases  . . . . . . . . . . . . . .   3
   5.  Use case summaries  . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Trusted Computing Group (TCG) . . . . . . . . . . . . . .   3
     5.2.  Android Keystore system . . . . . . . . . . . . . . . . .   4
     5.3.  Fast IDentity Online (FIDO) Alliance  . . . . . . . . . .   5
   6.  Privacy Considerations. . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The recently chartered IETF RATS WG intends to create a system of
   attestations that can be shared across a multitude of different
   users.

   This document exists as place to collect use cases in support of the
   IETF RATS charter point 1.  This document is not expected to be
   published as an RFC, but remain open as a working document.  It could
   become an appendix to provide motivation for a protocol standards
   document.

2.  Terminology

   Critical to dealing with and constrasting different technologies is
   to collect terms with are compatible, to distinguish those terms
   which are similar but used in different ways.

   This section will grow to include forward and external references to
   terms which have been seen.  When terms need to be disambiguated they
   will be prefixed with their source, such as "TCG(claim)" or
   "FIDO(relying party)"

Richardson             Expires September 12, 2019               [Page 2]
Internet-Draft                 useful RATS                    March 2019

3.  Requirements Language

   This document is not a standards track document and does not make any
   normative protocol requirements using terminology described in
   [RFC2119].

4.  Overview of Sources of Use Cases

   The following specifications have been convered in this document:

   o  The Trusted Computing Group "Network Attestation System" (private
      document)

   o  Android Keystore
Show full document text