TLS and DTLS Security Modules
draft-urien-uta-tls-dtls-security-module-03

Document Type Active Internet-Draft (individual)
Last updated 2016-12-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)
UTA Working Group                                            P. Urien 
  Internet Draft                                      Telecom ParisTech 
  Intended status: Experimental                                         
                                                                        
                                                        December 8 2016 
  Expires: June 2017 
 
                          TLS and DTLS Security Modules 
                    draft-urien-uta-tls-dtls-security-module-03.txt 
    
    
Abstract 
    
   Security and trust are very critical topics in the context of the 
   anywhere, anytime, anything internet connectivity. TLS and DTLS are 
   two major IETF protocols widely used to secure IP exchanges. 
   According to CoAP, DTLS is the protocol used by constraint nodes in 
   the Internet of Things (IoT) context. 
    
   In this draft we specify an ISO7816 interface for TLS and DTLS 
   secure modules based on ISO7816 secure chips, which are today 
   manufactured per billions every year. 
    
   Secure elements are cheap secure microcontrollers whose size is 
   about 25mm2 and whose security is ranked by evaluations typically 
   according to Common Criteria (CC) standards.  
    
   The support of TLS and DTLS is based on the EAP-TLS protocol, and 
   the IETF draft "EAP Support in smartcard" describing EAP-TLS support 
   for secure elements. First implementation demonstrates that such low 
   cost security modules are realistic, with a setup time for handshake 
   completion under the second. 
    
    
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. 

   Urien                   Expires June 2017               [page 1] 

 
                     TLS and DTLS Security Modules     December 2016 
 
    
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 June 2017. 
    
    
Copyright Notice 
    
   Copyright (c) 2016 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 June 2017            [Page 2] 

 
                     TLS and DTLS Security Modules     December 2016 
 
Table of Contents 
    
   Abstract........................................................... 1 
   Requirements Language.............................................. 1 
   Status of this Memo................................................ 2 
   Copyright Notice................................................... 2 
   1 Overview......................................................... 4 
   2 The EAP-TLS Smartcard............................................ 4 
      2.1 The EAP-TLS protocol........................................ 4 
      2.2 The EAP-TLS Smartcard....................................... 6 
   4 The TLS Security Module.......................................... 6 
      4.1 EAP-TLS for TLS Security Module............................. 6 
      4.2 The TLS / EAP-TLS Software Bridge........................... 8 
      4.3 The TLS Security Module Encryption and Decryption procedures 8 
   5 The DTLS Security Module........................................ 10 
      5.1 EAP-TLS for DTLS Security Module........................... 10 
      5.2 The DTLS / EAP-TLS Software Bridge......................... 11 
      5.3 The DTLS Security Module Encryption and Decryption procedures
      ............................................................... 12 
   6 Example of TLS processing by the TLS security module............ 14 
Show full document text