CBOR Object Signing and Encryption (COSE): Headers for carrying and referencing X.509 certificates
draft-ietf-cose-x509-01
Network Working Group J. Schaad
Internet-Draft August Cellars
Intended status: Informational March 11, 2019
Expires: September 12, 2019
CBOR Object Signing and Encryption (COSE): Headers for carrying and
referencing X.509 certificates
draft-ietf-cose-x509-01
Abstract
The CBOR Signing And Encrypted Message (COSE) structure syntax uses
the COSE Key structure for placing keys in a message. This document
extends the way that keys can be identified and transported by
providing attributes that refer to or contain X.509 certificates.
Contributing to this document
The source for this draft is being maintained in GitHub. Suggested
changes should be submitted as pull requests at <https://github.com/
cose-wg/X509>. Instructions are on that page as well. Editorial
changes can be managed in GitHub, but any substantial issues need to
be discussed on the COSE mailing list.
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 September 12, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Schaad Expires September 12, 2019 [Page 1]
Internet-Draft COSE X.509 March 2019
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Terminology . . . . . . . . . . . . . . . . 3
1.2. Open Questions . . . . . . . . . . . . . . . . . . . . . 3
2. X.509 COSE Headers . . . . . . . . . . . . . . . . . . . . . 3
3. X.509 certificates and static-static ECDH . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4.1. COSE Header Parameter Registry . . . . . . . . . . . . . 7
4.2. COSE Header Algorithm Parameter Registry . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
In the process of writing [RFC8152] discussions where held on the
question of X.509 certificates [RFC5280] and if there was a needed to
provide for them. At the time there were no use cases presented that
appeared to have a sufficient need for these attributes. Since that
time a number of cases where X.509 certificate support is necessary
have been defined. This document provides a set of attributes that
will allow applications to transport and refer to X.509 certificates
in a consistent manner.
Some of the constrained device situations are being used where an
X.509 PKI is already installed. One of these situations is the 6tish
environment for enrollment of devices where the certificates are
installed at the factory. The [I-D.selander-ace-cose-ecdhe] draft
was also written with the idea that long term certificates could be
used to provide for authentication of devices and uses them to
establish session keys. A final scenario is the use of COSE as a
messaging application where long term existence of keys can be used
along with a central authentication authority. The use of
certificates in this scenario allows for key management to be used
which is well understood.
Schaad Expires September 12, 2019 [Page 2]
Internet-Draft COSE X.509 March 2019
Show full document text