Using CBOR Web Tokens (CWTs) in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
draft-tschofenig-tls-cwt-01
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-04
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
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 H. Tschofenig
Internet-Draft M. Brossard
Intended status: Standards Track Arm Limited
Expires: May 7, 2020 November 04, 2019
Using CBOR Web Tokens (CWTs) in Transport Layer Security (TLS) and
Datagram Transport Layer Security (DTLS)
draft-tschofenig-tls-cwt-01
Abstract
The TLS protocol supports different credentials, including pre-shared
keys, raw public keys, and X.509 certificates. For use with public
key cryptography developers have to decide between raw public keys,
which require out-of-band agreement and full-fletched X.509
certificates. For devices where the reduction of code size is
important it is desirable to minimize the use of X.509-related
libraries. With the CBOR Web Token (CWT) a structure has been
defined that allows CBOR-encoded claims to be protected with CBOR
Object Signing and Encryption (COSE).
This document registers a new value to the "TLS Certificate Types"
sub-registry to allow TLS and DTLS to use CWTs. Conceptually, CWTs
can be seen as a certificate format (when with public key
cryptography) or a Kerberos ticket (when used with symmetric key
cryptography).
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 https://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 May 7, 2020.
Tschofenig & Brossard Expires May 7, 2020 [Page 1]
Internet-Draft CWTs in TLS/DTLS November 2019
Copyright Notice
Copyright (c) 2019 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
(https://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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
3. The CWT Certificate Type . . . . . . . . . . . . . . . . . . 3
4. Representation and Verification the Identity of Application
Services . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security and Privacy Considerations . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. History . . . . . . . . . . . . . . . . . . . . . . 8
Appendix B. Working Group Information . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The CBOR Web Token (CWT) [RFC8392] was defined as the CBOR-based
version of the JSON Web Token (JWT) [RFC7519]. JWT is used
extensively on Web application and for use with Internet of Things
Tschofenig & Brossard Expires May 7, 2020 [Page 2]
Internet-Draft CWTs in TLS/DTLS November 2019
environments the believe is that a more lightweight encoding, namely
Show full document text