Identity Module for TLS Version 1.3
draft-urien-tls-im-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-07-11
|
|
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
July 11 2020
Expires: January 2020
Identity Module for TLS Version 1.3
draft-urien-tls-im-02.txt
Abstract
TLS 1.3 will be deployed in the Internet of Things ecosystem. In
many IoT frameworks, TLS or DTLS protocols, based on pre-shared key
(PSK), are used for device authentication. So PSK tamper resistance,
is a critical market request, in order to prevent hijacking issues.
If DH exchange is used with certificate bound to DH ephemeral public
key, there is also a benefit to protect its signature procedure. The
TLS identity module (im) MAY be based on secure element; it realizes
some HKDF operations bound to PSK, and cryptographic signature if
certificates are used. Secure Element form factor could be
standalone chip, or embedded in SOC like eSIM.
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 January 2020.
.
Urien Expires January 2020 [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 January 2020 [page 2]
Identity Module for TLS Version 1.3 July 2020
Table of Contents
Abstract........................................................... 1
Requirements Language.............................................. 1
Status of this Memo................................................ 1
Copyright Notice................................................... 2
1 Overview......................................................... 4
2 Protecting the Key Schedule for PSK.............................. 4
2.1 Context..................................................... 4
2.2 Identity Module Procedures.................................. 5
2.3 KSGS: Keys Secure Generation and Storage.................... 5
2.4 Identity Module Key Procedures (IMKP)....................... 5
2.4.1 CETS: Client Early Traffic Secret .................... 5
2.4.2 EEMS: Early Exporter Master Secret ................... 6
2.4.3 HEDSK: HKDF-Extract from Derived Secret Key .......... 6
2.4.4 HBSK: HMAC from Binder Key Secret .................... 6
3. Asymmetric Signature............................................ 6
3.1 GENKEY...................................................... 6
3.2 GETPUB...................................................... 7
3.3 SIGN........................................................ 7
4. Secure Element as Identity Module............................... 8
4.1 Administrative mode......................................... 8
4.2 User Mode................................................... 8
4.3 KSGS: Keys Secure Generation and Storage.................... 8
4.3.1 Example .............................................. 9
Show full document text