The Qualcomm Wireless Edge Services (QWES) Attestation Token
draft-mandyam-rats-qwestoken-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda rats at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Rats Working Group                                            G. Mandyam
Internet-Draft                                                 V. Sekhar
Intended status: Informational                               S. Mohammed
Expires: May 3, 2020                          Qualcomm Technologies Inc.
                                                        October 31, 2019

      The Qualcomm Wireless Edge Services (QWES) Attestation Token
                    draft-mandyam-rats-qwestoken-00

Abstract

   An attestation format based on the Entity Attestation Token (EAT) is
   described.  The Qualcomm Wireless Edge Services (QWES) token is used
   in the context of device onboarding and authentication.  It is
   verified in the same manner as any CBOR Web Token (CWT).

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 May 3, 2020.

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.

Mandyam, et al.            Expires May 3, 2020                  [Page 1]
Internet-Draft                  QWESToken                   October 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  EAT Compliant Claims in QWES Token  . . . . . . . . . . . . .   2
     2.1.  OEM ID  . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.2.  nonce . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  QWES Token Augmentation to EAT  . . . . . . . . . . . . . . .   3
     3.1.  DevID . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  HWVer . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  Context . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.4.  PKHash  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.5.  SPID  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.6.  QSEEVersion . . . . . . . . . . . . . . . . . . . . . . .   3
     3.7.  FWVersion . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.8.  Security State  . . . . . . . . . . . . . . . . . . . . .   4
     3.9.  CSR . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.10. AppData . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   A description of the Qualcomm Wireless Edge Services (QWES)
   attestation token is provided.  QWES allows for service providers to
   manage devices that implement Qualcomm semiconductor solutions.
   Based on the EAT-compliant attestation token (see [I-D.ietf-rats-
   eat]) produced in a trusted execution environment (TEE), a service
   provider can verify the device identity in addition to several other
   security-impacting characteristics.

2.  EAT Compliant Claims in QWES Token

   Certain claims defined for EAT are leveraged in the QWES token.

2.1.  OEM ID

   The QWES token makes use of an OEM ID.  However, the type is a uint
   (not a bstr as per the EAT specification).

2.2.  nonce

   The QWES token can carry a nonce.  The nonce is a bstr.

Mandyam, et al.            Expires May 3, 2020                  [Page 2]
Internet-Draft                  QWESToken                   October 2019

3.  QWES Token Augmentation to EAT

   Several claims have been defined that are not currently present in
   the EAT base set to complete the QWES token.

3.1.  DevID

   The DevID is a 256-bit bstr that serves as a device identifier.  It
   differs from the ueid (Universal Entity ID) defined in the EAT
   specificaation.  A specific device ID can be created for ISV's based
Show full document text