Open Trust Protocol CBOR Encoding
draft-liu-opentrustprotocol-cbor-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-12
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)
Network Working Group                                             D. Liu
Internet-Draft                                                   Q. Fang
Intended status: Standards Track                           Alibaba Group
Expires: September 14, 2017                               March 13, 2017

                   Open Trust Protocol CBOR Encoding
                draft-liu-opentrustprotocol-cbor-00.txt

Abstract

   This document specifies the Open Trust Protocol (OTrP) using RFC 7049
   Concise Binary Object Representation(CBOR).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 September 14, 2017.

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

Liu & Fang             Expires September 14, 2017               [Page 1]
Internet-Draft           opentrustprotocol-CBOR               March 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
   2.  Scenario of using CBOR  . . . . . . . . . . . . . . . . . . .   3
   3.  OTrP Agent  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  API getTAInformation  . . . . . . . . . . . . . . . . . .   3
     3.2.  OTrP Messages using CBOR Encoding . . . . . . . . . . . .   4
       3.2.1.  Request and Response Message Template . . . . . . . .   4
       3.2.2.  Signed Request and Response Message Structure . . . .   5
     3.3.  Detailed Messages Specification-8 . . . . . . . . . . . .   6
       3.3.1.  GetDeviceState-8.1  . . . . . . . . . . . . . . . . .   6
       3.3.2.  Security Domain Management-8.2  . . . . . . . . . . .  10
       3.3.3.  Trusted Application Management-8.3  . . . . . . . . .  13
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     4.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   This document uses CBOR to encode the operations in OTrP.  The goal
   is to improve the efficiency of information transmission in
   bandwidth-constrained scenarios.  This document will not change the
   OTrP entity and the trust model.

   This document will re-use the TA remote security mechanism as defined
   in [draft-pei-opentrustprotocol].

   This document uses CBOR to encode the contents of JSON data as
   defined in [draft-pei-opentrustprotocol].

   [draft-pei-opentrustprotocol]uses JOSE for JSON content encryption,
   signatures and Message Authentication Code (MAC) operations.  This
   document uses the CBOR Object Encryption and Signing (COSE) standard
   which does the similar thing for CBOR encoding format.

   This document uses CDDL as defined in
   [draft-greevenbosch-appsawg-cbor-cddl]to describe the CBOR content
   defined in this document.

Liu & Fang             Expires September 14, 2017               [Page 2]
Internet-Draft           opentrustprotocol-CBOR               March 2017

2.  Scenario of using CBOR

   In bandwidth constrained scenario, using JSON/JOSE to encode OTrP
   message may not efficient.  Using CBOR as encoding scheme can improve
Show full document text