Cryptographic Message System (CMS) Content Types for Concise Binary Object Representation (CBOR)
draft-schaad-cbor-content-02

Document Type Active Internet-Draft (individual in sec area)
Last updated 2019-12-05 (latest revision 2019-12-04)
Stream IETF
Intended RFC status Informational
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd Sean Turner
Shepherd write-up Show (last changed 2019-10-13)
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to Sean Turner <sean+ietf@sn3rd.com>
IANA IANA review state Version Changed - Review Needed
IANA expert review state Need IANA Expert(s)
IANA expert review comments Designated expert for CMS Inner Content Types has been requested. Other registrations have been approved.
Network Working Group                                          J. Schaad
Internet-Draft                                            August Cellars
Intended status: Informational                           4 December 2019
Expires: 6 June 2020

  Cryptographic Message System (CMS) Content Types for Concise Binary
                      Object Representation (CBOR)
                      draft-schaad-cbor-content-02

Abstract

   Concise Binary Object Representation (CBOR) is becoming a widely used
   method of doing content encoding.  Cryptographic Message System (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.

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 6 June 2020.

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.

Schaad                     Expires 6 June 2020                  [Page 1]
Internet-DraftCryptographic Message System (CMS) Content TyDecember 2019

Table of Contents

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

1.  Introduction

   Concise Binary Object Representation (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 one of the most
   common method for providing message-based security, although in many
   cases the CBOR Object Signing and Encryption (COSE) [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: CBOR Content
   Type and CBOR Sequence Content Type [CBOR-SEQ].

2.  CBOR Content Type

   [CBOR] defines an encoded CBOR item.  This section defines a new
   content type for wrapping an encoded CBOR item in a CMS object.

   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) pkcs9(9) smime(16) ct(1) TBD1 }

   The CBOR content type is intended to refer to a single object encoded
   using the CBOR encoding format [CBOR].  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.

Schaad                     Expires 6 June 2020                  [Page 2]
Internet-DraftCryptographic Message System (CMS) Content TyDecember 2019

   [RFC7193] defined an optional parameter "innerContent" to allow for
   identification of what the inner content is for an application/cms
Show full document text