You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: draft-ietf-cose-hash-envelope.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,23 +79,23 @@ The terms COSE, CDDL, and EDN are defined in {{-COSE}}, {{-CDDL}}, {{-EDN}} resp
79
79
80
80
This document specifies the following new header parameters commonly used alongside hashes to identify resources:
81
81
82
-
TBD_1:
82
+
258:
83
83
: the hash algorithm used to produce the payload.
84
84
85
-
TBD_2:
85
+
259:
86
86
: the content type of the bytes that were hashed (preimage) to produce the payload, given as a content-format number ({{Section 12.3 of RFC7252}}) or as a media-type name optionally with parameters ({{Section 8.3 of RFC9110}}).
87
87
88
-
TBD_3:
88
+
260:
89
89
: an identifier enabling retrieval of the original resource (preimage) identified by the payload.
- Label `TBD_1` (payload hash alg) MUST be present in the protected header and MUST NOT be present in the unprotected header.
118
-
- Label `TBD_2` (content type of the preimage of the payload) MAY be present in the protected header or unprotected header.
119
-
- Label `TBD_3` (payload_location) MAY be added to the protected header and MUST NOT be presented in the unprotected header.
117
+
- Label `258` (payload hash alg) MUST be present in the protected header and MUST NOT be present in the unprotected header.
118
+
- Label `259` (content type of the preimage of the payload) MAY be present in the protected header or unprotected header.
119
+
- Label `260` (payload_location) MAY be added to the protected header and MUST NOT be presented in the unprotected header.
120
120
- Label `3` (content_type) MUST NOT be present in the protected or unprotected headers.
121
121
122
-
Label `3` is easily confused with label `TBD_2` payload_preimage_content_type.
122
+
Label `3` is easily confused with label `259` payload_preimage_content_type.
123
123
The difference between content_type (3) and payload_preimage_content_type (TBD2) is content_type is used to identify the content format associated with payload, whereas payload_preimage_content_type is used to identify the content format of the bytes which are hashed to produce the payload.
124
124
125
-
Profiles that rely on this specification MAY choose to mark TBD_1, TBD_2, TBD_3 (or other header parameters) critical, see {{Section C.1.3 of RFC9052}} for more details.
125
+
Profiles that rely on this specification MAY choose to mark 258, 259, 260 (or other header parameters) critical, see {{Section C.1.3 of RFC9052}} for more details.
126
126
127
127
# Envelope EDN
128
128
@@ -134,10 +134,10 @@ The following informative example demonstrates how to construct a hash envelope
134
134
/ signature alg / 1: -35,# ES384
135
135
/ key identifier / 4: h'75726e3a...32636573',
136
136
/ cose sign1 type / 16: "application/example+cose",
| `payload-hash-alg` | TBD_1 | int | (2) | The hash algorithm used to produce the payload of a COSE_Sign1 | {{&SELF}}, {{param-spec}} |
194
-
| `preimagecontenttype` | TBD_2 | uint / tstr | (3) | The content-format number or content-type (media-type name) of data that has been hashed to produce the payload of the COSE_Sign1 | {{&SELF}}, {{param-spec}} |
195
-
| `payload-location` | TBD_3 | tstr | (none) | The string or URI hint for the location of the data hashed to produce the payload of a COSE_Sign1 | {{&SELF}}, {{param-spec}} |
193
+
| `payload-hash-alg` | 258 | int | (2) | The hash algorithm used to produce the payload of a COSE_Sign1 | {{&SELF}}, {{param-spec}} |
194
+
| `preimage-content-type` | 259 | uint / tstr | (3) | The content-format number or content-type (media-type name) of data that has been hashed to produce the payload of the COSE_Sign1 | {{&SELF}}, {{param-spec}} |
195
+
| `payload-location` | 260 | tstr | (none) | The string or URI hint for the location of the data hashed to produce the payload of a COSE_Sign1 | {{&SELF}}, {{param-spec}} |
0 commit comments