Secure Element for TLS Version 1.3
draft-urien-tls-se-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Pascal Urien
|
|
Last updated |
|
2020-09-25
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
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)
|
TLS Working Group P. Urien
Internet Draft Telecom Paris
Intended status: Experimental
September 25 2020
Expires: March 2021
Secure Element for TLS Version 1.3
draft-urien-tls-se-01.txt
Abstract
This draft presents ISO7816 interface for TLS1.3 stack running in
secure element. It presents supported cipher suites and key exchange
modes, and describes embedded software architecture. TLS 1.3 is the
de facto security stack for emerging Internet of Things (IoT)
devices. Some of them are constraint nodes, with limited computing
resources. Furthermore cheap System on Chip (SoC) components usually
provide tamper resistant features, so private or pre shared keys are
exposed to hacking. According to the technology state of art, some
ISO7816 secure elements are able to process TLS 1.3, but with a
limited set of cipher suites. There are two benefits for TLS-SE;
first fully tamper resistant processing of TLS protocol, which
increases the security level insurance; second embedded software
component ready for use, which relieves the software of the burden
of cryptographic libraries and associated attacks. TLS-SE devices
may also embed standalone applications, which are accessed via
internet node, using a routing procedure based on SNI extension.
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 March 2021.
Urien Expires March 2021 [Page 1]
Copyright Notice
Copyright (c) 2020 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 March 2021 [page 2]
Secure Element for TLS Version 1.3 September 2020
Table of Contents
Abstract........................................................... 1
Requirements Language.............................................. 1
Status of this Memo................................................ 1
Copyright Notice................................................... 2
1 Overview......................................................... 4
2 About Secure Elements............................................ 5
3 Software components for TLS-SE................................... 5
3.1 Cryptographic resources..................................... 6
3.2 Data exchange............................................... 6
3.2.1 Receiving Record Packet .............................. 6
3.2.2 Sending Record Packet ................................ 7
3.2.4 RECV and SEND procedure for open application AEAD .... 9
3.3 TLS state machine........................................... 9
3.4 TLS library................................................ 10
4 ISO7816 interface............................................... 11
5 ISO 7816 Use Case............................................... 12
5 TLS-SE Name..................................................... 14
Show full document text