Remote APDU Call Secure (RACS)
draft-urien-core-racs-09

Document Type Active Internet-Draft (individual)
Last updated 2017-06-09
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)
CORE Working Group                                           P. Urien 
  Internet Draft                                      Telecom ParisTech 
  Intended status: Experimental                                         
                                                                        
                                                              June 2017 
  Expires: December 2017 
 
                           Remote APDU Call Secure (RACS) 
                           draft-urien-core-racs-09.txt 
    
    
Abstract 
    
   This document describes the Remote APDU Call Protocol Secure (RACS) 
   protocol, dedicated to Grid of Secure Elements (GoSE). These servers 
   host Secure Elements (SE), i.e. tamper resistant chips offering 
   secure storage and cryptographic resources. 
    
   Secure Elements are microcontrollers whose chip area is about 25mm2; 
   they deliver trusted computing services in constrained environments. 
    
   RACS supports commands for GoSE inventory and data exchange with 
   secure elements. It is designed according to the representational 
   State Transfer (REST) architecture. RACS resources are identified by 
   dedicated URIs. An HTTP interface is also supported. 
    
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. 
    
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 December 2017. 
    
   . 

   Urien                       Expires June 2017            [Page 1] 

    

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 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. 
    
    

   Urien                     Expires December 2017             [page 2] 

 
                                  RACS                        June 2017 
 
Table of Contents 
   Abstract........................................................... 1 
   Requirements Language.............................................. 1 
   Status of this Memo................................................ 1 
   Copyright Notice................................................... 2 
   1 Overview......................................................... 5 
      1.1 What is a Secure Element.................................... 5 
      1.2 Grid Of Secure Elements (GoSE).............................. 6 
      1.3 Secure Element Identifier (SEID)............................ 7 
          1.3.1 SlotID example ....................................... 7 
          1.3.2 SEID for Secure Elements ............................. 8 
      1.4 APDUs....................................................... 9 
          1.4.1 ISO7816 APDU request ................................. 9 
          1.4.2 ISO7816 APDU response ................................ 9 
   2 The RACS protocol............................................... 10 
      2.1 Structure of RACS request.................................. 10 
      2.2 Structure of a RACS response............................... 11 
          2.2.1 BEGIN Header ........................................ 11 
          2.2.2 END Header .......................................... 11 
          2.2.3 Status line ......................................... 11 
          2.2.4 Examples of RACS responses: ......................... 12 
      2.3 RACS request commands...................................... 12 
          2.3.1 BEGIN ............................................... 12 
          2.3.2 END ................................................. 12 
          2.3.3 The APPEND parameter ................................ 13 
Show full document text