Browse Prior Art Database

CBOR Object Signing and Encryption (COSE) (RFC8152)

IP.com Disclosure Number: IPCOM000250367D
Original Publication Date: 2017-Jul-01
Included in the Prior Art Database: 2017-Jul-06

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Schaad: AUTHOR

Abstract

There has been an increased focus on small, constrained devices that make up the Internet of Things (IoT). One of the standards that has come out of this process is "Concise Binary Object Representation (CBOR)" [RFC7049]. CBOR extended the data model of the JavaScript Object Notation (JSON) [RFC7159] by allowing for binary data, among other changes. CBOR is being adopted by several of the IETF working groups dealing with the IoT world as their encoding of data structures. CBOR was designed specifically to be both small in terms of messages transport and implementation size and be a schema-free decoder. A need exists to provide message security services for IoT, and using CBOR as the message-encoding format makes sense.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Internet Engineering Task Force (IETF)                         J. Schaad Request for Comments: 8152                                August Cellars Category: Standards Track                                      July 2017 ISSN: 2070-1721

                CBOR Object Signing and Encryption (COSE)

Abstract

   Concise Binary Object Representation (CBOR) is a data format designed    for small code size and small message size.  There is a need for the    ability to have basic security services defined for this data format.    This document defines the CBOR Object Signing and Encryption (COSE)    protocol.  This specification describes how to create and process    signatures, message authentication codes, and encryption using CBOR    for serialization.  This specification additionally describes how to    represent cryptographic keys using CBOR.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8152.

Copyright Notice

   Copyright (c) 2017 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.

 Schaad                       Standards Track                    [Page 1]
 RFC 8152        CBOR Object Signing and Encryption (COSE)      July 2017

 Table of Contents

   1. Introduction ....................................................4

      1.1. Design Changes from JOSE ...................................5

      1.2. Requirements Terminology ...................................6

      1.3. CBOR Grammar ...............................................6

      1.4. CBOR-Related Terminology ...................................7

      1.5. Document Terminology ........................................