CMS Content Types for CBOR
draft-schaad-cbor-content-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-26
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                          J. Schaad
Internet-Draft                                            August Cellars
Intended status: Informational                             26 March 2019
Expires: 27 September 2019

                       CMS Content Types for CBOR
                      draft-schaad-cbor-content-00

Abstract

   CBOR is becoming a widely used method of doing content encoding.  CMS
   is still a widely used method of doing message based security.  THis
   document defines a set of content types for CMS that hold CBOR
   content.

Contributing to this document

   The source for this draft is being maintained in GitHub.  Suggested
   changes should be submitted as pull requests at TBD.  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 27 September 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.

Table of Contents

   1.  Introduction
   2.  CBOR Content Type
   3.  CBOR Sequence Content Type
   4.  ASN.1 Module
   5.  IANA Considerations
   6.  Security Considerations
   7.  Normative References
   Author's Address

1.  Introduction

   CBOR [CBOR] is a compact self describing binary encoding formation
   that is starting to be used in many different applications.  One of
   the primary uses of CBOR is in the Internet of Things where the
   constrained nature means that having minimal size of encodings
   becomes very important.  The use of the Cryptographic Message System
   (CMS) [CMS] is still the most common method for providing message
   based security, although in many cases the CBOR Object Signing and
   Encryption (COSE) message based security system is starting to be
   used.  Given that CBOR is going to be transported using CMS, it makes
   sense to define CMS content types for the purpose of denoting that
   the embedded content is CBOR.  This document defines two new content
   types.

2.  CBOR Content Type

   The following object identifier identifies the CBOR content type:

   id-ct-cbor OBJECT IDENTIFIER ::= { iso(1) member-body(2) usa(840)
                   rsadsi(113549) pkcs(1) pkcs7(7) (x) TBD }

   The CBOR content type is intended to refer to a single object encoded
   using the CBOR encoding format.  Nothing is stated about the specific
   CBOR object that is included.  CBOR can always be decoded to a tree
   as the encoding is self descriptive.

   The CBOR content type is intended to be encapsulated in the signed
   data and auth-enveloped data, but can be included in any CMS wrapper.
   It cannot be predicted if the compressed CMS encapsulation will
   provide compression as the content may be binary rather than text.

3.  CBOR Sequence Content Type

   The following object identifier identifies the CBOR Sequence content
   type:

   id-ct-cborSequence OBJECT IDENTIFIER ::= { iso(1) member-body(2) usa(840)
           rsadsi(113549) pkcs(1) pkcs9(9) smime(16) ct(1) TBD }

   The CBOR Sequence content type is intended to refer to a sequence of
   objects encoded using the CBOR encoding format.  The objects are
   concatenated without any markers delimiting the individual CBOR
   objects.  Nothing is stated about the specific CBOR objects that are
   included.  CBOR can always be decoded to a tree as the encoding is
   self descriptive.

   The CBOR Sequence content type is intended to be encapsulated in the
   signed data and auth-enveloped data, but can be included in any CMS
   wrapper.  It cannot be predicted if the compressed CMS encapsulation
   will provide compression as the content may be binary rather than
   text.

4.  ASN.1 Module
Show full document text