The Entity Attestation Token (EAT)
draft-ietf-rats-eat-08

Document Type Active Internet-Draft (rats WG)
Authors Giridhar Mandyam  , Laurence Lundblade  , Miguel Ballesteros  , Jeremy O'Donoghue 
Last updated 2021-02-04
Replaces draft-mandyam-rats-eat
Stream Internent Engineering Task Force (IETF)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Mar 2021 - Submit EAT draft to ... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
RATS Working Group                                            G. Mandyam
Internet-Draft                                Qualcomm Technologies Inc.
Intended status: Standards Track                            L. Lundblade
Expires: August 8, 2021                              Security Theory LLC
                                                          M. Ballesteros
                                                           J. O'Donoghue
                                              Qualcomm Technologies Inc.
                                                       February 04, 2021

                   The Entity Attestation Token (EAT)
                         draft-ietf-rats-eat-08

Abstract

   An Entity Attestation Token (EAT) provides a signed (attested) set of
   claims that describe state and characteristics of an entity,
   typically a device like a phone or an IoT device.  These claims are
   used by a relying party to determine how much it wishes to trust the
   entity.

   An EAT is either a CWT or JWT with some attestation-oriented claims.
   To a large degree, all this document does is extend CWT and JWT.

Contributing

   TBD

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 August 8, 2021.

Mandyam, et al.          Expires August 8, 2021                 [Page 1]
Internet-Draft                     EAT                     February 2021

Copyright Notice

   Copyright (c) 2021 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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  CWT, JWT and UCCS . . . . . . . . . . . . . . . . . . . .   5
     1.2.  CDDL  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Entity Overview . . . . . . . . . . . . . . . . . . . . .   6
     1.4.  EAT Operating Models  . . . . . . . . . . . . . . . . . .   6
     1.5.  What is Not Standardized  . . . . . . . . . . . . . . . .   8
       1.5.1.  Transmission Protocol . . . . . . . . . . . . . . . .   8
       1.5.2.  Signing Scheme  . . . . . . . . . . . . . . . . . . .   8
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   9
   3.  The Claims  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Token ID Claim (cti and jti)  . . . . . . . . . . . . . .  10
     3.2.  Timestamp claim (iat) . . . . . . . . . . . . . . . . . .  10
     3.3.  Nonce Claim (nonce) . . . . . . . . . . . . . . . . . . .  10
       3.3.1.  nonce CDDL  . . . . . . . . . . . . . . . . . . . . .  11
     3.4.  Universal Entity ID Claim (ueid)  . . . . . . . . . . . .  11
       3.4.1.  ueid CDDL . . . . . . . . . . . . . . . . . . . . . .  13
     3.5.  Origination Claim (origination) . . . . . . . . . . . . .  13
       3.5.1.  origination CDDL  . . . . . . . . . . . . . . . . . .  14
     3.6.  OEM Identification by IEEE (oemid)  . . . . . . . . . . .  14
       3.6.1.  oemid CDDL  . . . . . . . . . . . . . . . . . . . . .  14
     3.7.  Hardware Version Claims (hardware-version-claims) . . . .  14
     3.8.  Software Description and Version  . . . . . . . . . . . .  16
     3.9.  The Security Level Claim (security-level) . . . . . . . .  16
       3.9.1.  security-level CDDL . . . . . . . . . . . . . . . . .  17
     3.10. Secure Boot Claim (secure-boot) . . . . . . . . . . . . .  17
       3.10.1.  secure-boot CDDL . . . . . . . . . . . . . . . . . .  18
     3.11. Debug Status Claim (debug-status) . . . . . . . . . . . .  18
       3.11.1.  Enabled  . . . . . . . . . . . . . . . . . . . . . .  19
       3.11.2.  Disabled . . . . . . . . . . . . . . . . . . . . . .  19
       3.11.3.  Disabled Since Boot  . . . . . . . . . . . . . . . .  19
       3.11.4.  Disabled Permanently . . . . . . . . . . . . . . . .  19
Show full document text