draft-ietf-cose-msg-22.txt   draft-ietf-cose-msg-23.txt 
COSE Working Group J. Schaad COSE Working Group J. Schaad
Internet-Draft August Cellars Internet-Draft August Cellars
Intended status: Standards Track October 16, 2016 Intended status: Standards Track October 18, 2016
Expires: April 19, 2017 Expires: April 21, 2017
CBOR Object Signing and Encryption (COSE) CBOR Object Signing and Encryption (COSE)
draft-ietf-cose-msg-22 draft-ietf-cose-msg-23
Abstract Abstract
Concise Binary Object Representation (CBOR) is data format designed Concise Binary Object Representation (CBOR) is data format designed
for small code size and small message size. There is a need for the 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. ability to have basic security services defined for this data format.
This document defines the CBOR Object Signing and Encryption (COSE) This document defines the CBOR Object Signing and Encryption (COSE)
specification. This specification describes how to create and specification. This specification describes how to create and
process signature, message authentication codes and encryption using process signature, message authentication codes and encryption using
CBOR for serialization. This specification additionally specifies CBOR for serialization. This specification additionally specifies
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 19, 2017. This Internet-Draft will expire on April 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 13, line 39 skipping to change at page 13, line 39
The header parameter values indicated by 'crit' can be processed The header parameter values indicated by 'crit' can be processed
by either the security library code or by an application using a by either the security library code or by an application using a
security library; the only requirement is that the parameter is security library; the only requirement is that the parameter is
processed. If the 'crit' value list includes a value for which processed. If the 'crit' value list includes a value for which
the parameter is not in the protected bucket, this is a fatal the parameter is not in the protected bucket, this is a fatal
error in processing the message. error in processing the message.
content type: This parameter is used to indicate the content type of content type: This parameter is used to indicate the content type of
the data in the payload or cipher text fields. Integers are from the data in the payload or cipher text fields. Integers are from
the "CoAP Content-Formats" IANA registry table [COAP.Formats]. the "CoAP Content-Formats" IANA registry table [COAP.Formats].
Text values following the syntax of Content-Type defined in Text values following the syntax of "<type-name>/<subtype-name>"
Section 4.2 of [RFC6838] omitting the prefix string "Content- where <type-name> and <subtype-name> are defined in Section 4.2 of
Type:". Leading and trailing whitespace is also omitted. Textual [RFC6838]. Leading and trailing whitespace is also omitted.
content values along with parameters and subparameters can be Textual content values along with parameters and subparameters can
located using the IANA "Media Types" registry. Applications be located using the IANA "Media Types" registry. Applications
SHOULD provide this parameter if the content structure is SHOULD provide this parameter if the content structure is
potentially ambiguous. potentially ambiguous.
kid: This parameter identifies one piece of data that can be used as kid: This parameter identifies one piece of data that can be used as
input to find the needed cryptographic key. The value of this input to find the needed cryptographic key. The value of this
parameter can be matched against the 'kid' member in a COSE_Key parameter can be matched against the 'kid' member in a COSE_Key
structure. Other methods of key distribution can define an structure. Other methods of key distribution can define an
equivalent field to be matched. Applications MUST NOT assume that equivalent field to be matched. Applications MUST NOT assume that
'kid' values are unique. There may be more than one key with the 'kid' values are unique. There may be more than one key with the
same 'kid' value, so all of the keys associated with this 'kid' same 'kid' value, so all of the keys associated with this 'kid'
 End of changes. 4 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/