idnits 2.17.1 draft-ietf-cose-cbor-encoded-cert-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. == There are 39 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 12, 2021) is 1018 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Address' is mentioned on line 599, but not defined == Missing Reference: '-24' is mentioned on line 1728, but not defined -- Looks like a reference, but probably isn't: '23' on line 1728 == Missing Reference: '-256' is mentioned on line 854, but not defined -- Looks like a reference, but probably isn't: '255' on line 854 == Missing Reference: '-65536' is mentioned on line 855, but not defined -- Looks like a reference, but probably isn't: '65535' on line 855 -- Looks like a reference, but probably isn't: '1' on line 2360 -- Looks like a reference, but probably isn't: '2' on line 2360 == Outdated reference: A later version (-08) exists of draft-ietf-cbor-tags-oid-06 == Outdated reference: A later version (-09) exists of draft-ietf-cose-x509-08 ** Downref: Normative reference to an Informational RFC: RFC 2986 ** Obsolete normative reference: RFC 8152 (Obsoleted by RFC 9052, RFC 9053) -- Possible downref: Non-RFC (?) normative reference: ref. 'SECG' == Outdated reference: A later version (-21) exists of draft-ietf-emu-eap-tls13-18 == Outdated reference: A later version (-23) exists of draft-ietf-lake-edhoc-06 == Outdated reference: A later version (-10) exists of draft-ietf-tls-ctls-01 == Outdated reference: A later version (-09) exists of draft-ietf-uta-tls13-iot-profile-01 Summary: 2 errors (**), 0 flaws (~~), 13 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Preuss Mattsson 3 Internet-Draft G. Selander 4 Intended status: Standards Track Ericsson AB 5 Expires: January 13, 2022 S. Raza 6 J. Hoeglund 7 RISE AB 8 M. Furuhed 9 Nexus Group 10 July 12, 2021 12 CBOR Encoded X.509 Certificates (C509 Certificates) 13 draft-ietf-cose-cbor-encoded-cert-02 15 Abstract 17 This document specifies a CBOR encoding of X.509 certificates. The 18 resulting certificates are called C509 Certificates. The CBOR 19 encoding supports a large subset of RFC 5280 and all certificates 20 compatible with the RFC 7925, IEEE 802.1AR (DevID), CNSA, RPKI, GSMA 21 eUICC, and CA/Browser Forum Baseline Requirements profiles. When 22 used to re-encode DER encoded X.509 certificates, the CBOR encoding 23 can in many cases reduce the size of RFC 7925 profiled certificates 24 with over 50%. The CBOR encoded structure can alternatively be 25 signed directly ("natively signed"), which does not require re- 26 encoding for the signature to be verified. The document also 27 specifies C509 COSE headers, a C509 TLS certificate type, and a C509 28 file format. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at https://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on January 13, 2022. 47 Copyright Notice 49 Copyright (c) 2021 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (https://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4 66 3. C509 Certificate . . . . . . . . . . . . . . . . . . . . . . 5 67 3.1. Message Fields . . . . . . . . . . . . . . . . . . . . . 5 68 3.2. Encoding of subjectPublicKey and issuerSignatureValue . . 8 69 3.3. Encoding of Extensions . . . . . . . . . . . . . . . . . 9 70 4. C509 Certificate Signing Request . . . . . . . . . . . . . . 14 71 5. C509 Certificate Revocation List . . . . . . . . . . . . . . 15 72 6. C509 Online Certificate Status Protocol . . . . . . . . . . . 16 73 7. C509 Processing and Certificate Issuance . . . . . . . . . . 16 74 8. Legacy Considerations . . . . . . . . . . . . . . . . . . . . 17 75 9. Expected Certificate Sizes . . . . . . . . . . . . . . . . . 17 76 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 77 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 78 11.1. C509 Certificate Types Registry . . . . . . . . . . . . 19 79 11.2. C509 Attributes Registry . . . . . . . . . . . . . . . . 20 80 11.3. C509 Extensions Registry . . . . . . . . . . . . . . . . 23 81 11.4. C509 Certificate Policies Registry . . . . . . . . . . . 26 82 11.5. C509 Policies Qualifiers Registry . . . . . . . . . . . 29 83 11.6. C509 Information Access Registry . . . . . . . . . . . . 29 84 11.7. C509 Extended Key Usages Registry . . . . . . . . . . . 32 85 11.8. C509 General Names Registry . . . . . . . . . . . . . . 33 86 11.9. C509 Signature Algorithms Registry . . . . . . . . . . . 35 87 11.10. C509 Public Key Algorithms Registry . . . . . . . . . . 38 88 11.11. COSE Header Parameters Registry . . . . . . . . . . . . 41 89 11.12. TLS Certificate Types Registry . . . . . . . . . . . . . 42 90 11.13. CBOR Tags Registry . . . . . . . . . . . . . . . . . . . 43 91 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 92 12.1. Normative References . . . . . . . . . . . . . . . . . . 43 93 12.2. Informative References . . . . . . . . . . . . . . . . . 44 94 Appendix A. Example C509 Certificates . . . . . . . . . . . . . 47 95 A.1. Example RFC 7925 profiled X.509 Certificate . . . . . . . 47 96 A.2. Example IEEE 802.1AR profiled X.509 Certificate . . . . . 50 97 A.3. Example CAB Baseline ECDSA HTTPS X.509 Certificate . . . 50 98 A.4. Example CAB Baseline RSA HTTPS X.509 Certificate . . . . 54 99 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 57 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 102 1. Introduction 104 One of the challenges with deploying a Public Key Infrastructure 105 (PKI) for the Internet of Things (IoT) is the size and parsing of 106 X.509 public key certificates [RFC5280], since those are not 107 optimized for constrained environments [RFC7228]. Large certificate 108 chains are also problematic in non-constrained protocols such as EAP- 109 TLS [I-D.ietf-emu-eap-tls13] [I-D.ietf-emu-eaptlscert] where 110 authenticators typically drop an EAP session after only 40 - 50 111 round-trips, QUIC [RFC9000] where the latency increases significantly 112 unless the server sends less than three times as many bytes as 113 received prior to validating the client address, and RPKI [RFC6487] 114 where a single certificate can be very large. More compact 115 certificate representations are therefore desirable in many use 116 cases. Due to the current PKI usage of DER encoded X.509 117 certificates, keeping compatibility with DER encoded X.509 is 118 necessary at least for a transition period. However, the use of a 119 more compact encoding with the Concise Binary Object Representation 120 (CBOR) [RFC8949] reduces the certificate size significantly which has 121 known performance benefits in terms of decreased communication 122 overhead, power consumption, latency, storage, etc. 124 CBOR is a data format designed for small code size and small message 125 size. CBOR builds on the JSON data model but extends it by e.g. 126 encoding binary data directly without base64 conversion. In addition 127 to the binary CBOR encoding, CBOR also has a diagnostic notation that 128 is readable and editable by humans. The Concise Data Definition 129 Language (CDDL) [RFC8610] provides a way to express structures for 130 protocol messages and APIs that use CBOR. RFC 8610 also extends the 131 diagnostic notation. 133 CBOR data items are encoded to or decoded from byte strings using a 134 type-length-value encoding scheme, where the three highest order bits 135 of the initial byte contain information about the major type. CBOR 136 supports several different types of data items, in addition to 137 integers (int, uint), simple values (e.g. null), byte strings (bstr), 138 and text strings (tstr), CBOR also supports arrays [] of data items, 139 maps {} of pairs of data items, and sequences of data items. For a 140 complete specification and examples, see [RFC8949], [RFC8610], and 141 [RFC8742]. We recommend implementors to get used to CBOR by using 142 the CBOR playground [CborMe]. 144 CAB Baseline Requirements [CAB-TLS], RFC 7925 [RFC7925], IEEE 802.1AR 145 [IEEE-802.1AR], and CNSA [RFC8603] specify certificate profiles which 146 can be applied to certificate based authentication with, e.g., TLS 147 [RFC8446], QUIC [RFC9000], DTLS [I-D.ietf-tls-dtls13], COSE 148 [RFC8152], EDHOC [I-D.ietf-lake-edhoc], or Compact TLS 1.3 149 [I-D.ietf-tls-ctls]. RFC 7925 [RFC7925], RFC7925bis 150 [I-D.ietf-uta-tls13-iot-profile], and IEEE 802.1AR [IEEE-802.1AR] 151 specifically target Internet of Things deployments. This document 152 specifies a CBOR encoding based on [X.509-IoT], which can support 153 large parts of RFC 5280. The encoding supports all RFC 7925, IEEE 154 802.1AR, CAB Baseline [CAB-TLS], [CAB-Code], RPKI [RFC6487], eUICC 155 [GSMA-eUICC] profiled X.509 certificates. The resulting certificates 156 are called C509 Certificates. This document does not specify a 157 certificate profile. Two variants are defined using the same CBOR 158 encoding and differing only in what is being signed: 160 1. An invertible CBOR re-encoding of DER encoded X.509 certificates 161 [RFC5280], which can be reversed to obtain the original DER 162 encoded X.509 certificate. 164 2. Natively signed C509 certificates, where the signature is 165 calculated over the CBOR encoding instead of over the DER 166 encoding as in 1. This removes the need for ASN.1 and DER 167 parsing and the associated complexity but they are not backwards 168 compatible with implementations requiring DER encoded X.509. 170 Natively signed C509 certificates can be applied in devices that are 171 only required to authenticate to natively signed C509 certificate 172 compatible servers, which is not a major restriction for many IoT 173 deployments where the parties issuing and verifying certificates can 174 be a restricted ecosystem. 176 This document specifies COSE headers for use of the C509 certificates 177 with COSE, see Section 11.11. The document also specifies a TLS 178 certificate type for use of the C509 certificates with TLS and QUIC 179 (with or without additional TLS certificate compression), see 180 Section 11.12. 182 2. Notational Conventions 184 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 185 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 186 "OPTIONAL" in this document are to be interpreted as described in BCP 187 14 [RFC2119] [RFC8174] when, and only when, they appear in all 188 capitals, as shown here. 190 This specification makes use of the terminology in [RFC5280], 191 [RFC7228], [RFC8610], and [RFC8949]. When referring to CBOR, this 192 specification always refers to Deterministically Encoded CBOR as 193 specified in Sections 4.2.1 and 4.2.2 of [RFC8949]. 195 3. C509 Certificate 197 This section specifies the content and encoding for C509 198 certificates, with the overall objective to produce a very compact 199 representation supporting large parts of [RFC5280], and everything in 200 [RFC7925], [IEEE-802.1AR], RPKI [RFC6487], GSMA eUICC [GSMA-eUICC], 201 and CAB Baseline [CAB-TLS] [CAB-Code]. In the CBOR encoding, static 202 fields are elided, elliptic curve points and time values are 203 compressed, OID are replaced with short integers, and redundant 204 encoding is removed. Combining these different components reduces 205 the certificate size significantly, which is not possible with 206 general purpose compression algorithms, see Figure 5. 208 The C509 certificate can be either a CBOR re-encoding of a DER 209 encoded X.509 certificate, in which case the signature is calculated 210 on the DER encoded ASN.1 data in the X.509 certificate, or a natively 211 signed C509 certificate, in which case the signature is calculated 212 directly on the CBOR encoded data. In both cases the certificate 213 content is adhering to the restrictions given by [RFC5280]. The re- 214 encoding is known to work with DER encoded certificates but might 215 work with other canonical encodings. The re-encoding does not work 216 for BER encoded certificates. 218 In the encoding described below, the order of elements in arrays are 219 always encoded in the same order as the elements or the corresponding 220 SEQUENCE or SET in the DER encoding. 222 3.1. Message Fields 224 The X.509 fields and their CBOR encodings are listed below, and used 225 in the definition of C509 certificates, see Figure 1. 227 C509 certificates are defined in terms of DER encoded [RFC5280] X.509 228 certificates: 230 o version. The 'version' field is encoded in the 231 'c509CertificateType' CBOR int. The field 'c509CertificateType' 232 also indicates the type of the C509 certificate. Currently, the 233 type can be a natively signed C509 certificate following X.509 v3 234 (c509CertificateType = 0) or a CBOR re-encoded X.509 v3 DER 235 certificate (c509CertificateType = 1), see Section 11.1. 237 o serialNumber. The 'serialNumber' INTEGER value field is encoded 238 as the unwrapped CBOR unsigned bignum (~biguint) 239 'certificateSerialNumber'. Any leading 0x00 byte (to indicate 240 that the number is not negative) is therefore omitted. 242 o signature. The 'signature' field is always the same as the 243 'signatureAlgorithm' field and therefore omitted from the CBOR 244 encoding. 246 o issuer. In the general case, the sequence of 247 'RelativeDistinguishedName' is encoded as a CBOR array of CBOR 248 arrays of Attributes. Typically, each RelativeDistinguishedName 249 only contains a single attribute and the sequence is then encoded 250 as a CBOR array of Attributes. Each Attribute is encoded as a 251 (CBOR int, CBOR text string) pair or as a (unwrapped CBOR OID, 252 CBOR bytes) pair. The absolute value of the CBOR int (see 253 Figure 7) encodes the attribute type and the sign is used to 254 represent the character string type; positive for Utf8String, 255 negative for PrintableString. The Attribute Email Address is 256 always an IA5String. In natively signed C509 certificates all 257 text strings are UTF-8 encoded and all attributeType SHALL have be 258 non-negative. Text strings SHALL still adhere to any X.509 259 restrictions, i.e., serialNumber SHALL only contain the 74 260 character subset of ASCII allowed by PrintableString and 261 countryName SHALL have length 2. The string types teletexString, 262 universalString, and bmpString are not supported. If Name 263 contains a single Attribute containing an utf8String encoded 264 'common name' it is encoded as a CBOR text string. If the text 265 string contains an EUI-64 of the form "HH-HH-HH-HH-HH-HH-HH-HH" 266 where 'H' is one of the symbols '0'-'9' or 'A'-'F' it is encoded 267 as a CBOR byte string of length 8 instead. EUI-64 mapped from a 268 48-bit MAC address (i.e., of the form "HH-HH-HH-FF-FE-HH-HH-HH) is 269 encoded as a CBOR byte string of length 6. 271 o validity. The 'notBefore' and 'notAfter' fields are encoded as 272 unwrapped CBOR epoch-based date/time (~time) where the tag content 273 is an unsigned integer. In POSIX time, leap seconds are ignored, 274 with a leap second having the same POSIX time as the second before 275 it. Compression of X.509 certificates with the time 23:59:60 UTC 276 is therefore not supported. Note that RFC 5280 mandates encoding 277 of dates through the year 2049 as UTCTime, and later dates as 278 GeneralizedTime. The value "99991231235959Z" (no expiration date) 279 is encoded as CBOR null. 281 o subject. The 'subject' is encoded exactly like issuer. 283 o subjectPublicKeyInfo. The 'AlgorithmIdentifier' field including 284 parameters is encoded as the CBOR int 'subjectPublicKeyAlgorithm' 285 (see Section 11.10) or as an array with an unwrapped CBOR OID tag 286 [I-D.ietf-cbor-tags-oid] optionally followed by the parameters 287 encoded as a CBOR byte string. In general, the 'subjectPublicKey' 288 BIT STRING value field is encoded as a CBOR byte string. This 289 specification assumes the BIT STRING has zero unused bits and the 290 unused bits byte is omitted. For rsaEncryption and id- 291 ecPublicKey, the encoding of subjectPublicKey is further optimized 292 as described in Section 3.2. 294 o issuerUniqueID. Not supported. 296 o subjectUniqueID. Not supported. 298 o extensions. The 'extensions' field is encoded as a CBOR array 299 where each extension is encoded as either a CBOR int (see 300 Section 11.3) followed by an optional CBOR item of any type or an 301 unwrapped CBOR OID tag [I-D.ietf-cbor-tags-oid] followed by a CBOR 302 bool encoding 'critical' and the DER encoded value of the 303 'extnValue' encoded as a CBOR byte string. If the array contains 304 exactly two ints and the absolute value of the first int is 2 305 (corresponding to keyUsage), the array is omitted and the 306 extensions is encoded as a single CBOR int with the absolute value 307 of the second int and the sign of the first int. Extensions are 308 encoded as specified in Section 3.3. The extensions mandated to 309 be supported by [RFC7925] and [IEEE-802.1AR] are given special 310 treatment. An omitted 'extensions' field is encoded as an empty 311 CBOR array. 313 o signatureAlgorithm. The 'signatureAlgorithm' field including 314 parameters is encoded as a CBOR int (see Section 11.9) or as an 315 array with an unwrapped CBOR OID tag [I-D.ietf-cbor-tags-oid] 316 optionally followed by the parameters encoded as a CBOR byte 317 string. 319 o signatureValue. In general, the 'signatureValue' BIT STRING value 320 field is encoded as the CBOR byte string issuerSignatureValue. 321 This specification assumes the BIT STRING has zero unused bits and 322 the unused bits byte is omitted. For natively signed C509 323 certificates the signatureValue is calculated over the CBOR 324 sequence TBSCertificate. For ECDSA, the encoding of 325 issuerSignatureValue is further optimized as described in 326 Section 3.2 328 The following Concise Data Definition Language (CDDL) defines the 329 CBOR array C509Certificate and the CBOR sequence [RFC8742] 330 TBSCertificate. The member names therefore only have documentary 331 value. Applications not requiring a CBOR item MAY represent C509 332 certificates with the CBOR sequence ~C509Certificate (unwrapped 333 C509Certificate). 335 C509Certificate = [ 336 TBSCertificate, 337 issuerSignatureValue : any, 338 ] 340 ; The elements of the following group are used in a CBOR Sequence: 341 TBSCertificate = ( 342 c509CertificateType: int, 343 certificateSerialNumber: CertificateSerialNumber, 344 issuer: Name, 345 validityNotBefore: Time, 346 validityNotAfter: Time, 347 subject: Name, 348 subjectPublicKeyAlgorithm: AlgorithmIdentifier, 349 subjectPublicKey: any, 350 extensions: Extensions, 351 issuerSignatureAlgorithm: AlgorithmIdentifier, 352 ) 354 CertificateSerialNumber = ~biguint 356 Name = [ * RelativeDistinguishedName ] / text / bytes 358 RelativeDistinguishedName = Attribute / [ 2* Attribute ] 360 Attribute = ( attributeType: int, attributeValue: text ) // 361 ( attributeType: ~oid, attributeValue: bytes ) 363 Time = ~time / null 365 AlgorithmIdentifier = int / ~oid / 366 [ algorithm: ~oid, parameters: bytes ] 368 Extensions = [ * Extension ] / int 370 Extension = ( extensionID: int, extensionValue: any ) // 371 ( extensionID: ~oid, ? critical: true, 372 extensionValue: bytes ) 374 Figure 1: CDDL for C509Certificate. 376 3.2. Encoding of subjectPublicKey and issuerSignatureValue 378 3.2.1. Encoding of subjectPublicKey 380 For RSA public keys (rsaEncryption), the SEQUENCE and INTEGER type 381 and length fields are omitted and the two INTEGER value fields 382 (modulus, exponent) are encoded as an array of two unwrapped CBOR 383 unsigned bignum (~biguint), i.e. [ modulus : ~biguint, exponent : 384 ~biguint ]. If the exponent is 65537, the array and the exponent is 385 omitted and subjectPublicKey consist of only the modulus encoded as 386 an unwrapped CBOR unsigned bignum (~biguint). 388 For elliptic curve public keys in Weierstrass form (id-ecPublicKey), 389 uncompressed keys are point compressed as defined in Section 2.3.3 of 390 [SECG]. If a DER encoded certificate with a point compressed public 391 key of type id-ecPublicKey is CBOR encoded, the octets 0xfe and 0xfd 392 are used instead of 0x02 and 0x03 in the CBOR encoding to represent 393 even and odd y-coordinate, respectively. 395 3.2.2. Encoding of issuerSignatureValue 397 For ECDSA signatures, the SEQUENCE and INTEGER type and length fields 398 as well as the any leading 0x00 byte (to indicate that the number is 399 not negative) are omitted. If the two INTEGER value fields have 400 different lengths, the shortest INTEGER value field is padded with 401 zeroes so that the two fields have the same length. The resulting 402 byte string is encoded as a CBOR byte string. 404 3.3. Encoding of Extensions 406 This section details the encoding of the 'extensions' field. The 407 'extensions' field is encoded as a CBOR array where each extensionID 408 is encoded as either a CBOR int or an unwrapped CBOR OID tag. If 409 'extensionID' is encoded an int (see Section 11.3), the sign is used 410 to encode if the extension is critical and the 'critical' field is 411 omitted. Critical extensions are encoded with a negative sign and 412 non-critical extensions are encoded with a positive sign. 414 The 'extnValue' OCTET STRING value field is encoded as the CBOR byte 415 string 'extensionValue' except for the extensions specified below. 416 For some extensions, only commonly used parts are supported by the 417 CBOR encoding. If unsupported parts are used, the CBOR encoding 418 cannot be used. 420 CBOR encoding of the following extension values are fully supported: 422 o Subject Key Identifier (subjectKeyIdentifier). The extensionValue 423 is encoded as follows: 425 KeyIdentifier = bytes 426 SubjectKeyIdentifier = KeyIdentifier 428 o Key Usage (keyUsage). The 'KeyUsage' BIT STRING is interpreted as 429 an unsigned integer in network byte order and encoded as a CBOR 430 int. See Section 3.1 for special encoding in case keyUsage is the 431 only extension present. 433 KeyUsage = int 435 o Policy Mappings (policyMappings). extensionValue is encoded as 436 follows: 438 PolicyMappings = [ 439 + (issuerDomainPolicy: ~oid, subjectDomainPolicy: ~oid) 440 ] 442 o Basic Constraints (basicConstraints). If 'cA' = false then 443 extensionValue = -2, if 'cA' = true and 'pathLenConstraint' is not 444 present then extensionValue = -1, and if 'cA' = true and 445 'pathLenConstraint' is present then extensionValue = 446 pathLenConstraint. 448 BasicConstraints = int 450 o Policy Constraints (policyConstraints). extensionValue is encoded 451 as follows: 453 PolicyConstraints = [ 454 requireExplicitPolicy: uint / null, 455 inhibitPolicyMapping: uint / null, 456 ] 458 o Extended Key Usage (extKeyUsage). extensionValue is encoded as an 459 array of CBOR ints (see Section 11.7 or unwrapped CBOR OID tags 460 [I-D.ietf-cbor-tags-oid] where each int or OID tag encodes a key 461 usage purpose. If the array contains a single KeyPurposeId, the 462 array is omitted. 464 KeyPurposeId = int / ~oid 465 ExtKeyUsageSyntax = [ 2* KeyPurposeId ] / KeyPurposeId 467 o Inhibit anyPolicy (inhibitAnyPolicy). extensionValue is encoded as 468 follows: 470 InhibitAnyPolicy = uint 472 CBOR encoding of the following extension values are partly supported: 474 o Subject Alternative Name (subjectAltName). If the subject 475 alternative name only contains general names registered in 476 Section 11.8 the extension value can be CBOR encoded. 477 extensionValue is encoded as an array of (int, any) pairs where 478 each pair encodes a general name (see Section 11.8). If 479 subjectAltName contains exactly one dNSName, the array and the int 480 are omitted and extensionValue is the dNSName encoded as a CBOR 481 text string. In addition to the general names defined in 482 [RFC5280], the hardwareModuleName type of otherName has been given 483 its own int due to its mandatory use in IEEE 802.1AR. When 484 'otherName + hardwareModuleName' is used, then [ oid, bytes ] is 485 used to identify the pair ( hwType, hwSerialEntries ) directly as 486 specified in [RFC4108]. Only the general names in Section 11.8 487 are supported. 489 GeneralName = ( GeneralNameType : int, GeneralNameValue : any ) 490 GeneralNames = [ + GeneralName ] 491 SubjectAltName = GeneralNames / text 493 o Issuer Alternative Name (issuerAltName). extensionValue is encoded 494 exactly like subjectAltName. 496 IssuerAltName = GeneralNames / text 498 o CRL Distribution Points (cRLDistributionPoints). If the CRL 499 Distribution Points is a sequence of DistributionPointName, where 500 each DistributionPointName only contains 501 uniformResourceIdentifiers, the extension value can be CBOR 502 encoded. extensionValue is encoded as follows: 504 DistributionPointName = [ 2* text ] / text 505 CRLDistributionPoints = [ + DistributionPointName ] 507 o Freshest CRL (freshestCRL). extensionValue is encoded exactly like 508 cRLDistributionPoints. 510 FreshestCRL = CRLDistributionPoints 512 o Authority Information Access (authorityInfoAccess). If all the 513 GeneralNames in authorityInfoAccess are of type 514 uniformResourceIdentifier, the extension value can be CBOR 515 encoded. Each accessMethod is encoded as an CBOR ints (see 516 Section 11.6) or unwrapped CBOR OID tags [I-D.ietf-cbor-tags-oid]. 517 The uniformResourceIdentifiers are encoded as CBOR text strings. 519 AccessDescription = ( accessMethod: int / ~oid , uri: text ) 520 AuthorityInfoAccessSyntax = [ + AccessDescription ] 522 o Subject Information Access (subjectInfoAccess). Encoded exactly 523 like authorityInfoAccess. 525 SubjectInfoAccessSyntax = AuthorityInfoAccessSyntax 527 o Authority Key Identifier (authorityKeyIdentifier). If the 528 authority key identifier contains all of keyIdentifier, 529 certIssuer, and certSerialNumberm or if only keyIdentifier is 530 present the extension value can be CBOR encoded. If all three are 531 present a CBOR array is used, if only keyIdentifier is present, 532 the array is omitted: 534 KeyIdentifierArray = [ 535 keyIdentifier: KeyIdentifier, 536 authorityCertIssuer: GeneralNames, 537 authorityCertSerialNumber: CertificateSerialNumber 538 ] 539 AuthorityKeyIdentifier = KeyIdentifierArray / KeyIdentifier 541 o Certificate Policies (certificatePolicies). If noticeRef is not 542 used and any explicitText are encoded as UTF8String, the extension 543 value can be CBOR encoded. OIDs registered in Section 11.4 are 544 encoded as an int. The policyQualifierId is encoded as an CBOR 545 int (see Section 11.5) or an unwrapped CBOR OID tag 546 [I-D.ietf-cbor-tags-oid]. 548 PolicyIdentifier = int / ~oid 549 PolicyQualifierInfo = ( 550 policyQualifierId: int / ~oid, 551 qualifier: text, 552 ) 553 CertificatePolicies = [ 554 + ( PolicyIdentifier, ? [ + PolicyQualifierInfo ] ) 555 ] 557 o Name Constraints (nameConstraints). If the name constraints only 558 contains general names registered in Section 11.8 the extension 559 value can be CBOR encoded. 561 GeneralSubtree = [ GeneralName, minimum: uint, ? maximum: uint ] 562 NameConstraints = [ 563 permittedSubtrees: GeneralSubtree, 564 excludedSubtrees: GeneralSubtree, 565 ] 567 o Subject Directory Attributes (subjectDirectoryAttributes). 568 Encoded as attributes in issuer and subject with the difference 569 that there can be more than one attributeValue. 571 Attributes = ( attributeType: int, attributeValue: [+text] ) // 572 ( attributeType: ~oid, attributeValue: [+bytes] ) 573 SubjectDirectoryAttributes = Attributes 575 o AS Resources (autonomousSysIds). If rdi is not present, the 576 extension value can be CBOR encoded. Each ASId is encoded as an 577 uint. With the exception of the first ASId, the ASid is encoded 578 as the difference to the previous ASid. 580 AsIdsOrRanges = uint / [uint, uint] 581 ASIdentifiers = [ + AsIdsOrRanges ] / null 583 o AS Resources v2 (id-pe-ipAddrBlocks-v2). Encoded exactly like 584 autonomousSysIds. 586 o IP Resources (id-pe-ipAddrBlocks). If rdi and SAFI is not 587 present, the extension value can be CBOR encoded. Each 588 AddressPrefix is encoded as a CBOR bytes string (without the 589 unused bits octet) followed by the number of unused bits encoded 590 as a CBOR uint. Each AddressRange is encoded as an array of two 591 CBOR byte strings. The unused bits for min and max are omitted, 592 but the unused bits in max IPAddress is set to ones. With the 593 exception of the first Address, if the byte string has the same 594 length as the previous ASid, the Addess is encoded as an uint with 595 the the difference to the previous Addess. 597 Address = bytes / uint, 598 AddressPrefix = (Address, unusedBits: uint) 599 AddressRange = [Address, Address] 600 IPAddressOrRange = AddressPrefix / AddressRange 601 IPAddressChoice = [ + IPAddressOrRange ] / null 602 IPAddrBlocks = [ AFI: uint, IPAddressChoice ] 604 o IP Resources v2 (id-pe-ipAddrBlocks-v2). Encoded exactly like id- 605 pe-ipAddrBlocks. 607 o Signed Certificate Timestamp. If all the SCTs are version 1, and 608 there are no SCT extensions, the extension value can be CBOR 609 encoded. LogIDs are encoded as CBOR byte strings, the timestamp 610 is encoded as and CBOR int (milliseconds since validityNotBefore), 611 and the signature is encoded with an (AlgorithmIdentifier, any) 612 pair in the same way as issuerSignatureAlgorithm and 613 issuerSignatureValue. 615 SignedCerticateTimestamp = ( 616 logID: bytes, 617 timestamp: int, 618 sigAlg: AlgorithmIdentifier, 619 sigValue: any, 620 ) 621 SignedCertificateTimestamps = [ + SignedCerticateTimestamp ] 623 3.3.1. Example Encoding of Extensions 625 The examples below use values from Section 11.3, Section 11.7, and 626 Section 11.8: 628 o A critical basicConstraints ('cA' = true) without 629 pathLenConstraint is encoded as the two CBOR ints -4, -1. 631 o A non-critical keyUsage with digitalSignature and keyAgreement 632 asserted is encoded as the two CBOR ints 2, 17 (2^0 + 2^4 = 17). 634 o A non-critical extKeyUsage containing id-kp-codeSigning and id-kp- 635 OCSPSigning is encoded as the CBOR int 8 followed by the CBOR 636 array [ 3, 6 ]. 638 o A non-critical subjectAltName containing only the dNSName 639 example.com is encoded as the CBOR int 3 followed by the CBOR text 640 string "example.com". 642 Thus, the extension field of a certificate containing all of the 643 above extensions in the given order would be encoded as the CBOR 644 array [ -4, -1, 2, 17, 8, [ 3, 6 ], 3, "example.com" ]. 646 4. C509 Certificate Signing Request 648 The section defines the C509 Certificate Signing Request (CSR) format 649 based on and compatible with RFC 2986 [RFC2986] reusing the 650 formatting for C509 certificates defined in Section 3. There are 651 currently two c509CertificateSigningRequestType values defined, 652 c509CertificateSigningRequestType = 0 requests a c509CertificateType 653 = 0 and c509CertificateSigningRequestType = 1 requests a 654 c509CertificateType = 1 . subjectProofOfPossessionAlgorithm can be a 655 C509 signature algorithm or a non-signature Proof-of-Possession 656 Algorithm as defined in e.g. RFC 6955. CSR attributes other than 657 extensionRequest are not supported. 659 C509CertificateSigningRequest = [ 660 TBSCertificateSigningRequest, 661 subjectProofOfPossessionValue: any, 662 ] 664 ; The elements of the following group are used in a CBOR Sequence: 665 TBSCertificateSigningRequest = ( 666 c509CertificateSigningRequestType: int, 667 subject: Name, 668 subjectPublicKeyAlgorithm: AlgorithmIdentifier, 669 subjectPublicKey: any, 670 extensionsRequest : Extensions, 671 subjectProofOfPossessionAlgorithm: AlgorithmIdentifier, 672 ) 674 Figure 2: CDDL for C509CertificateSigningRequest. 676 After verifying the subjectProofOfPossessionValue, the CA MAY 677 transform the C509CertificateSigningRequest into a RFC 2985 678 CertificationRequestInfo for compatibility with existing procedures 679 and code. 681 5. C509 Certificate Revocation List 683 The section defines the C509 Certificate Revocation List (CRL) format 684 based on and compatible with [RFC5280] reusing the formatting for 685 C509 certificates defined in Section 3. 687 C509CertificateRevocationList = [ 688 TBSCertificateRevocationList, 689 issuerSignatureValue : any, 690 ] 692 ; The elements of the following group are used in a CBOR Sequence: 693 TBSCertificateSigningRequest = ( 694 C509CertificateRevocationListType: int, 695 issuer: Name, 696 thisUpdate: Time, 697 nextUpdate: Time, 698 revokedCertificates: RevokedCertificates, 699 crlExtensions: Extensions, 700 issuerSignatureAlgorithm: AlgorithmIdentifier, 701 ) 703 RevokedCertificates = [ 704 userCertificate: CertificateSerialNumber, 705 revocationDate: Time, 706 crlEntryExtensions: Extensions, 707 ] 709 Figure 3: CDDL for C509CertificateRevocationList. 711 6. C509 Online Certificate Status Protocol 713 TODO 715 7. C509 Processing and Certificate Issuance 717 It is straightforward to integrate the C509 format into legacy X.509 718 processing during certificate issuance. C509 processing can be 719 performed as an isolated function of the CA, or as a separate 720 function trusted by the CA. 722 The CSR format defined in Section 4 follows the PKCS#10 format to 723 enable a direct mapping to the certification request information, see 724 Section 4.1 of [RFC2986]. 726 When a certificate request is received the CA, or function trusted by 727 the CA, needs to perform some limited C509 processing and verify the 728 proof of possession of the public key, before normal certificate 729 generation can take place. 731 In the reverse direction, in case c509CertificateType = 1 was 732 requested, a separate C509 processing function can perform the 733 conversion from a generated X.509 certificate to C509 as a bump-in- 734 the-wire. In case c509CertificateType = 0 was requested, the C509 735 processing needs to be performed before signing the certificate, in 736 which case a tighter integration with CA may be needed. 738 8. Legacy Considerations 740 C509 certificates can be deployed with legacy X.509 certificates and 741 CA infrastructure. In order to verify the signature, the C509 742 certificate is used to recreate the original X.509 data structure to 743 be able to verify the signature. 745 For protocols like TLS/DTLS 1.2, where the handshake is sent 746 unencrypted, the actual encoding and compression can be done at 747 different locations depending on the deployment setting. For 748 example, the mapping between C509 certificate and standard X.509 749 certificate can take place in a 6LoWPAN border gateway which allows 750 the server side to stay unmodified. This case gives the advantage of 751 the low overhead of a C509 certificate over a constrained wireless 752 links. The conversion to X.509 within an IoT device will incur a 753 computational overhead, however, measured in energy this is likely to 754 be negligible compared to the reduced communication overhead. 756 For the setting with constrained server and server-only 757 authentication, the server only needs to be provisioned with the C509 758 certificate and does not perform the conversion to X.509. This 759 option is viable when client authentication can be asserted by other 760 means. 762 For protocols like IKEv2, TLS/DTLS 1.3, and EDHOC, where certificates 763 are encrypted, the proposed encoding needs to be done fully end-to- 764 end, through adding the encoding/decoding functionality to the 765 server. 767 9. Expected Certificate Sizes 769 The CBOR encoding of the sample certificate chains given in 770 Appendix A results in the numbers shown in Figure 4 and Figure 5. 771 COSE_X509 is defined in [I-D.ietf-cose-x509] and COSE_C509 is defined 772 in Section 11.11. After RFC 7925 profiling, most duplicated 773 information has been removed, and the remaining text strings are 774 minimal in size. Therefore, the further size reduction reached with 775 general compression mechanisms such as Brotli will be small, mainly 776 corresponding to making the ASN.1 encoding more compact. CBOR 777 encoding can however significantly compress RFC 7925 profiled 778 certificates. For the example HTTPS certificate chains (www.ietf.org 779 and tools.ietf.org) both C509 and Brotli perform well complementing 780 each other. C509 use dedicated information to compress individual 781 certificates, while Brotli can compress duplicate information in the 782 entire chain. Note that C509 certificates of type 0 and 1 have the 783 same size. For Brotli [RFC7932], the Rust crate Brotli 3.3.0 was 784 used with compression level 11 and window size 22. 786 +---------------------------------------+-----------+-----------+ 787 | | COSE_X509 | COSE_C509 | 788 +---------------------------------------+-----------+-----------+ 789 | RFC 7925 profiled IoT Certificate (1) | 317 | 139 | 790 +---------------------------------------+-----------+-----------+ 791 | ECDSA HTTPS Certificate Chain (2) | 2193 | 1394 | 792 +---------------------------------------+-----------+-----------+ 793 | RSA HTTPS Certificate Chain (4) | 5175 | 3934 | 794 +---------------------------------------+-----------+-----------+ 796 Figure 4: Comparing Sizes of Certificate Chains in COSE. Number of 797 bytes (length of certificate chain). 799 +-------------------+-------+---------------+------+---------------+ 800 | | X509 | X509 + Brotli | C509 | C509 + Brotli | 801 +-------------------+-------+---------------+------+---------------+ 802 | RFC 7925 Cert (1) | 327 | 324 | 151 | 167 | 803 +-------------------+-------+---------------+------+---------------+ 804 | RPKI Cert (1) | 20991 | 9134 | 8660 | 5668 | 805 +-------------------+-------+---------------+------+---------------+ 806 | HTTPS Chain (2) | 2204 | 1455 | 1414 | 1063 | 807 +-------------------+-------+---------------+------+---------------+ 808 | HTTPS Chain (4) | 5190 | 3244 | 3958 | 2845 | 809 +-------------------+-------+---------------+------+---------------+ 810 | HTTPS Bag (8) | 11578 | 3979 | 8882 | 3519 | 811 +-------------------+-------+---------------+------+---------------+ 813 Figure 5: Comparing Sizes of Certificate Chains with TLS. Number of 814 bytes (length of certificate chain). X509 and C509 are Certificate 815 messages. X509 + Brotli and C509 + Brotli are CompressedCertificate 816 messages. 818 10. Security Considerations 820 The CBOR profiling of X.509 certificates does not change the security 821 assumptions needed when deploying standard X.509 certificates but 822 decreases the number of fields transmitted, which reduces the risk 823 for implementation errors. 825 The use of natively signed C509 certificates removes the need for 826 ASN.1 encoding, which is a rich source of security vulnerabilities. 828 Conversion between the certificate formats can be made in constant 829 time to reduce risk of information leakage through side channels. 831 The mechanism in this draft does not reveal any additional 832 information compared to X.509. Because of difference in size, it 833 will be possible to detect that this profile is used. The gateway 834 solution described in Section 8 requires unencrypted certificates and 835 is not recommended. 837 11. IANA Considerations 839 This document creates several new registries under the new heading 840 "C509 Certificate". For all items, the 'Reference' field points to 841 this document. 843 The expert reviewers for the registries defined in this document are 844 expected to ensure that the usage solves a valid use case that could 845 not be solved better in a different way, that it is not going to 846 duplicate one that is already registered, and that the registered 847 point is likely to be used in deployments. They are furthermore 848 expected to check the clarity of purpose and use of the requested 849 code points. Experts should take into account the expected usage of 850 entries when approving point assignment, and the length of the 851 encoded value should be weighed against the number of code points 852 left that encode to that size and how constrained the systems it will 853 be used on are. Values in the interval [-24, 23] have a 1 byte 854 encodings, other values in the interval [-256, 255] have a 2 byte 855 encodings, and the remaining values in the interval [-65536, 65535] 856 have 3 byte encodings. 858 11.1. C509 Certificate Types Registry 860 IANA has created a new registry titled "C509 Certificate Types" under 861 the new heading "C509 Certificate". The columns of the registry are 862 Value, Description, and Reference, where Value is an integer, and the 863 other columns are text strings. For values in the interval [-24, 23] 864 the registration procedure is "IETF Review" and "Expert Review". For 865 all other values the registration procedure is "Expert Review". The 866 initial contents of the registry are: 868 +-------+-----------------------------------------------------------+ 869 | Value | Description | 870 +=======+===========================================================+ 871 | 0 | Natively Signed C509 Certificate following X.509 v3 | 872 +-------+-----------------------------------------------------------+ 873 | 1 | CBOR re-encoding of X.509 v3 Certificate | 874 +-------+-----------------------------------------------------------+ 876 Figure 6: C509 Certificate Types 878 11.2. C509 Attributes Registry 880 IANA has created a new registry titled "C509 Attributes" under the 881 new heading "CBOR Encoded X509 Certificates (C509 Certificates)". 882 The columns of the registry are Value, Name, Identifiers, OID, DER, 883 Comments, and Reference, where Value is an non-negative integer, and 884 the other columns are text strings. For values in the interval [0, 885 23] the registration procedure is "IETF Review" and "Expert Review". 886 For all other values the registration procedure is "Expert Review". 887 The initial contents of the registry are: 889 +-------+-----------------------------------------------------------+ 890 | Value | Attribute | 891 +=======+===========================================================+ 892 | 0 | Name: Email Address | 893 | | Identifiers: emailAddress, e-mailAddress | 894 | | OID: 1.2.840.113549.1.9.1 | 895 | | DER: 06 09 2A 86 48 86 F7 0D 01 09 01 | 896 | | Comments: | 897 +-------+-----------------------------------------------------------+ 898 | 1 | Name: Common Name | 899 | | Identifiers: commonName, cn | 900 | | OID: 2.5.4.3 | 901 | | DER: 06 03 55 04 03 | 902 | | Comments: | 903 +-------+-----------------------------------------------------------+ 904 | 2 | Name: Surname | 905 | | Identifiers: surname, sn | 906 | | OID: 2.5.4.4 | 907 | | DER: 06 03 55 04 04 | 908 | | Comments: | 909 +-------+-----------------------------------------------------------+ 910 | 3 | Name: Serial Number | 911 | | Identifiers: serialNumber | 912 | | OID: 2.5.4.5 | 913 | | DER: 06 03 55 04 05 | 914 | | Comments: | 915 +-------+-----------------------------------------------------------+ 916 | 4 | Name: Country | 917 | | Identifiers: countryName, c | 918 | | OID: 2.5.4.6 | 919 | | DER: 06 03 55 04 06 | 920 | | Comments: | 921 +-------+-----------------------------------------------------------+ 922 | 5 | Name: Locality | 923 | | Identifiers: localityName, locality, l | 924 | | OID: 2.5.4.7 | 925 | | DER: 06 03 55 04 07 | 926 | | Comments: | 927 +-------+-----------------------------------------------------------+ 928 | 6 | Name: State or Province | 929 | | Identifiers: stateOrProvinceName, st | 930 | | OID: 2.5.4.8 | 931 | | DER: 06 03 55 04 08 | 932 | | Comments: | 933 +-------+-----------------------------------------------------------+ 934 | 7 | Name: Street Address | 935 | | Identifiers: streetAddress, street | 936 | | OID: 2.5.4.9 | 937 | | DER: 06 03 55 04 09 | 938 | | Comments: | 939 +-------+-----------------------------------------------------------+ 940 | 8 | Name: Organization | 941 | | Identifiers: organizationName, o | 942 | | OID: 2.5.4.10 | 943 | | DER: 06 03 55 04 0A | 944 | | Comments: | 945 +-------+-----------------------------------------------------------+ 946 | 9 | Name: Organizational Unit | 947 | | Identifiers: organizationalUnitName, ou | 948 | | OID: 2.5.4.11 | 949 | | DER: 06 03 55 04 0B | 950 | | Comments: | 951 +-------+-----------------------------------------------------------+ 952 | 10 | Name: Title | 953 | | Identifiers: title | 954 | | OID: 2.5.4.12 | 955 | | DER: 06 03 55 04 0C | 956 | | Comments: | 957 +-------+-----------------------------------------------------------+ 958 | 11 | Name: Business Category | 959 | | Identifiers: businessCategory | 960 | | OID: 2.5.4.15 | 961 | | DER: 06 03 55 04 0F | 962 | | Comments: | 963 +-------+-----------------------------------------------------------+ 964 | 12 | Name: Postal Code | 965 | | Identifiers: postalCode | 966 | | OID: 2.5.4.17 | 967 | | DER: 06 03 55 04 11 | 968 | | Comments: | 969 +-------+-----------------------------------------------------------+ 970 | 13 | Name: Given Name | 971 | | Identifiers: givenName | 972 | | OID: 2.5.4.42 | 973 | | DER: 06 03 55 04 2A | 974 | | Comments: | 975 +-------+-----------------------------------------------------------+ 976 | 14 | Name: Initials | 977 | | Identifiers: initials | 978 | | OID: 2.5.4.43 | 979 | | DER: 06 03 55 04 2B | 980 | | Comments: | 981 +-------+-----------------------------------------------------------+ 982 | 15 | Name: Generation Qualifier | 983 | | Identifiers: generationQualifier | 984 | | OID: 2.5.4.44 | 985 | | DER: 06 03 55 04 2C | 986 | | Comments: | 987 +-------+-----------------------------------------------------------+ 988 | 16 | Name: DN Qualifier | 989 | | Identifiers: dnQualifier | 990 | | OID: 2.5.4.46 | 991 | | DER: 06 03 55 04 2E | 992 | | Comments: | 993 +-------+-----------------------------------------------------------+ 994 | 17 | Name: Pseudonym | 995 | | Identifiers: pseudonym | 996 | | OID: 2.5.4.65 | 997 | | DER: 06 03 55 04 41 | 998 | | Comments: | 999 +-------+-----------------------------------------------------------+ 1000 | 18 | Name: Organization Identifier | 1001 | | Identifiers: organizationIdentifier | 1002 | | OID: 2.5.4.97 | 1003 | | DER: 06 03 55 04 61 | 1004 | | Comments: | 1005 +-------+-----------------------------------------------------------+ 1006 | 19 | Name: Inc. Locality | 1007 | | Identifiers: jurisdictionOfIncorporationLocalityName | 1008 | | OID: 1.3.6.1.4.1.311.60.2.1.1 | 1009 | | DER: 06 0B 2B 06 01 04 01 82 37 3C 02 01 01 | 1010 | | Comments: | 1011 +-------+-----------------------------------------------------------+ 1012 | 20 | Name: Inc. State or Province | 1013 | | Identifiers: jurisdictionOfIncorporation | 1014 | | StateOrProvinceName | 1015 | | OID: 1.3.6.1.4.1.311.60.2.1.2 | 1016 | | DER: 06 0B 2B 06 01 04 01 82 37 3C 02 01 02 | 1017 | | Comments: | 1018 +-------+-----------------------------------------------------------+ 1019 | 21 | Name: Inc. Country | 1020 | | Identifiers: jurisdictionOfIncorporationCountryName | 1021 | | OID: 1.3.6.1.4.1.311.60.2.1.3 | 1022 | | DER: 06 0B 2B 06 01 04 01 82 37 3C 02 01 03 | 1023 | | Comments: | 1024 +-------+-----------------------------------------------------------+ 1025 | 21 | Name: Domain Component | 1026 | | Identifiers: domainComponent, dc | 1027 | | OID: 0.9.2342.19200300.100.1.25 | 1028 | | DER: 06 0A 09 92 26 89 93 F2 2C 64 01 19 | 1029 | | Comments: | 1030 +-------+-----------------------------------------------------------+ 1032 Figure 7: C509 Attributes 1034 11.3. C509 Extensions Registry 1036 IANA has created a new registry titled "C509 Extensions Registry" 1037 under the new heading "CBOR Encoded X509 Certificates (C509 1038 Certificates)". The columns of the registry are Value, Name, 1039 Identifiers, OID, DER, Comments, extensionValue, and Reference, where 1040 Value is an positive integer, and the other columns are text strings. 1041 For values in the interval [1, 23] the registration procedure is 1042 "IETF Review" and "Expert Review". For all other values the 1043 registration procedure is "Expert Review". The initial contents of 1044 the registry are: 1046 +-------+-----------------------------------------------------------+ 1047 | Value | Extension | 1048 +=======+===========================================================+ 1049 | 1 | Name: Subject Key Identifier | 1050 | | Identifiers: subjectKeyIdentifier | 1051 | | OID: 2.5.29.14 | 1052 | | DER: 06 03 55 1D 0E | 1053 | | Comments: | 1054 | | extensionValue: SubjectKeyIdentifier | 1055 +-------+-----------------------------------------------------------+ 1056 | 2 | Name: Key Usage | 1057 | | Identifiers: keyUsage | 1058 | | OID: 2.5.29.15 | 1059 | | DER: 06 03 55 1D 0F | 1060 | | Comments: | 1061 | | AttributeValue: KeyUsage | 1062 +-------+-----------------------------------------------------------+ 1063 | 3 | Name: Subject Alternative Name | 1064 | | Identifiers: subjectAltName | 1065 | | OID: 2.5.29.17 | 1066 | | DER: 06 03 55 1D 11 | 1067 | | Comments: | 1068 | | extensionValue: SubjectAltName | 1069 +-------+-----------------------------------------------------------+ 1070 | 4 | Name: Basic Constraints | 1071 | | Identifiers: basicConstraints | 1072 | | OID: 2.5.29.19 | 1073 | | DER: 06 03 55 1D 13 | 1074 | | Comments: | 1075 | | extensionValue: BasicConstraints | 1076 +-------+-----------------------------------------------------------+ 1077 | 5 | Name: CRL Distribution Points | 1078 | | Identifiers: cRLDistributionPoints | 1079 | | OID: 2.5.29.31 | 1080 | | DER: 06 03 55 1D 1F | 1081 | | Comments: | 1082 | | extensionValue: CRLDistributionPoints | 1083 +-------+-----------------------------------------------------------+ 1084 | 6 | Name: Certificate Policies | 1085 | | Identifiers: certificatePolicies | 1086 | | OID: 2.5.29.32 | 1087 | | DER: 06 03 55 1D 20 | 1088 | | Comments: | 1089 | | extensionValue: CertificatePolicies | 1090 +-------+-----------------------------------------------------------+ 1091 | 7 | Name: Authority Key Identifier | 1092 | | Identifiers: authorityKeyIdentifier | 1093 | | OID: 2.5.29.35 | 1094 | | DER: 06 03 55 1D 23 | 1095 | | Comments: | 1096 | | extensionValue: AuthorityKeyIdentifier | 1097 +-------+-----------------------------------------------------------+ 1098 | 8 | Name: Extended Key Usage | 1099 | | Identifiers: extKeyUsage | 1100 | | OID: 2.5.29.37 | 1101 | | DER: 06 03 55 1D 25 | 1102 | | Comments: | 1103 | | extensionValue: ExtKeyUsageSyntax | 1104 +-------+-----------------------------------------------------------+ 1105 | 9 | Name: Authority Information Access | 1106 | | Identifiers: authorityInfoAccess | 1107 | | OID: 1.3.6.1.5.5.7.1.1 | 1108 | | DER: 06 08 2B 06 01 05 05 07 01 01 | 1109 | | Comments: | 1110 | | extensionValue: AuthorityInfoAccessSyntax | 1111 +-------+-----------------------------------------------------------+ 1112 | 10 | Name: Signed Certificate Timestamp List | 1113 | | Identifiers: | 1114 | | OID: 1.3.6.1.4.1.11129.2.4.2 | 1115 | | DER: 06 0A 2B 06 01 04 01 D6 79 02 04 02 | 1116 | | Comments: | 1117 | | extensionValue: SignedCertificateTimestamps | 1118 +-------+-----------------------------------------------------------+ 1119 | 24 | Name: Subject Directory Attributes | 1120 | | Identifiers: subjectDirectoryAttributes | 1121 | | OID: 2.5.29.9 | 1122 | | DER: 06 03 55 1D 09 | 1123 | | Comments: | 1124 | | extensionValue: SubjectDirectoryAttributes | 1125 +-------+-----------------------------------------------------------+ 1126 | 25 | Name: Issuer Alternative Name | 1127 | | Identifiers: issuerAltName | 1128 | | OID: 2.5.29.18 | 1129 | | DER: 06 03 55 1D 12 | 1130 | | Comments: | 1131 | | extensionValue: IssuerAltName | 1132 +-------+-----------------------------------------------------------+ 1133 | 26 | Name: Name Constraints | 1134 | | Identifiers: nameConstraints | 1135 | | OID: 2.5.29.30 | 1136 | | DER: 06 03 55 1D 1E | 1137 | | Comments: | 1138 | | extensionValue: NameConstraints | 1139 +-------+-----------------------------------------------------------+ 1140 | 27 | Name: Policy Mappings | 1141 | | Identifiers: policyMappings | 1142 | | OID: 2.5.29.33 | 1143 | | DER: 06 03 55 1D 21 | 1144 | | Comments: | 1145 | | extensionValue: PolicyMappings | 1146 +-------+-----------------------------------------------------------+ 1147 | 28 | Name: Policy Constraints | 1148 | | Identifiers: policyConstraints | 1149 | | OID: 2.5.29.36 | 1150 | | DER: 06 03 55 1D 24 | 1151 | | Comments: | 1152 | | extensionValue: PolicyConstraints | 1153 +-------+-----------------------------------------------------------+ 1154 | 29 | Name: Freshest CRL | 1155 | | Identifiers: freshestCRL | 1156 | | OID: 2.5.29.46 | 1157 | | DER: 06 03 55 1D 2E | 1158 | | Comments: | 1159 | | extensionValue: FreshestCRL | 1160 +-------+-----------------------------------------------------------+ 1161 | 30 | Name: Inhibit anyPolicy | 1162 | | Identifiers: inhibitAnyPolicy | 1163 | | OID: 2.5.29.54 | 1164 | | DER: 06 03 55 1D 36 | 1165 | | Comments: | 1166 | | extensionValue: InhibitAnyPolicy | 1167 +-------+-----------------------------------------------------------+ 1168 | 31 | Name: Subject Information Access | 1169 | | Identifiers: subjectInfoAccess | 1170 | | OID: 1.3.6.1.5.5.7.1.11 | 1171 | | DER: 06 08 2B 06 01 05 05 07 01 0B | 1172 | | Comments: | 1173 | | extensionValue: SubjectInfoAccessSyntax | 1174 +-------+-----------------------------------------------------------+ 1175 | 32 | Name: IP Resources | 1176 | | Identifiers: ipAddrBlocks | 1177 | | OID: 1.3.6.1.5.5.7.1.7 | 1178 | | DER: 06 08 2B 06 01 05 05 07 01 07 | 1179 | | Comments: | 1180 | | extensionValue: IPAddrBlocks | 1181 +-------+-----------------------------------------------------------+ 1182 | 33 | Name: AS Resources | 1183 | | Identifiers: autonomousSysIds | 1184 | | OID: 1.3.6.1.5.5.7.1.8 | 1185 | | DER: 06 08 2B 06 01 05 05 07 01 08 | 1186 | | Comments: | 1187 | | extensionValue: ASIdentifiers | 1188 +-------+-----------------------------------------------------------+ 1189 | 34 | Name: IP Resources v2 | 1190 | | Identifiers: ipAddrBlocks-v2 | 1191 | | OID: 1.3.6.1.5.5.7.1.28 | 1192 | | DER: 06 08 2B 06 01 05 05 07 01 1C | 1193 | | Comments: | 1194 | | extensionValue: IPAddrBlocks | 1195 +-------+-----------------------------------------------------------+ 1196 | 35 | Name: AS Resources v2 | 1197 | | Identifiers: autonomousSysIds-v2 | 1198 | | OID: 1.3.6.1.5.5.7.1.29 | 1199 | | DER: 06 08 2B 06 01 05 05 07 01 1D | 1200 | | Comments: | 1201 | | extensionValue: ASIdentifiers | 1202 +-------+-----------------------------------------------------------+ 1204 Figure 8: C509 Extensions 1206 11.4. C509 Certificate Policies Registry 1208 IANA has created a new registry titled "C509 Certificate Policies 1209 Registry" under the new heading "CBOR Encoded X509 Certificates (C509 1210 Certificates)". The columns of the registry are Value, Name, 1211 Identifiers, OID, DER, Comments, and Reference, where Value is an 1212 integer, and the other columns are text strings. For values in the 1213 interval [-24, 23] the registration procedure is "IETF Review" and 1214 "Expert Review". For all other values the registration procedure is 1215 "Expert Review". The initial contents of the registry are: 1217 +-------+-----------------------------------------------------------+ 1218 | Value | Certificate Policy | 1219 +=======+===========================================================+ 1220 | 0 | Name: Any Policy | 1221 | | Identifiers: anyPolicy | 1222 | | OID: 2.5.29.32.0 | 1223 | | DER: 06 04 55 1D 20 00 | 1224 | | Comments: | 1225 +-------+-----------------------------------------------------------+ 1226 | 1 | Name: Domain Validation (DV) | 1227 | | Identifiers: domain-validated | 1228 | | OID: 2.23.140.1.2.1 | 1229 | | DER: 06 06 67 81 0C 01 02 01 | 1230 | | Comments: | 1231 +-------+-----------------------------------------------------------+ 1232 | 2 | Name: Organization Validation (OV) | 1233 | | Identifiers: organization-validated | 1234 | | OID: 2.23.140.1.2.2 | 1235 | | DER: 06 06 67 81 0C 01 02 02 | 1236 | | Comments: | 1237 +-------+-----------------------------------------------------------+ 1238 | 3 | Name: Individual Validation (IV) | 1239 | | Identifiers: individual-validated | 1240 | | OID: 2.23.140.1.2.3 | 1241 | | DER: 06 06 67 81 0C 01 02 03 | 1242 | | Comments: | 1243 +-------+-----------------------------------------------------------+ 1244 | 4 | Name: Extended Validation (EV) | 1245 | | Identifiers: ev-guidelines | 1246 | | OID: 2.23.140.1.1 | 1247 | | DER: 06 05 67 81 0C 01 01 | 1248 | | Comments: | 1249 +-------+-----------------------------------------------------------+ 1250 | 7 | Name: Resource PKI (RPKI) | 1251 | | Identifiers: id-cp-ipAddr-asNumber | 1252 | | OID: 1.3.6.1.5.5.7.14.2 | 1253 | | DER: 06 08 2B 06 01 05 05 07 0E 02 | 1254 | | Comments: | 1255 +-------+-----------------------------------------------------------+ 1256 | 8 | Name: Resource PKI (RPKI) (Alternative) | 1257 | | Identifiers: id-cp-ipAddr-asNumber-v2 | 1258 | | OID: 1.3.6.1.5.5.7.14.3 | 1259 | | DER: 06 08 2B 06 01 05 05 07 0E 03 | 1260 | | Comments: | 1261 +-------+-----------------------------------------------------------+ 1262 | 10 | Name: Remote SIM Provisioning Role | 1263 | | Certificate Issuer | 1264 | | Identifiers: id-rspRole-ci | 1265 | | OID: 2.23.146.1.2.1.0 | 1266 | | DER: 06 07 67 81 12 01 02 01 00 | 1267 | | Comments: | 1268 +-------+-----------------------------------------------------------+ 1269 | 11 | Name: Remote SIM Provisioning Role | 1270 | | eUICC | 1271 | | Identifiers: id-rspRole-euicc | 1272 | | OID: 2.23.146.1.2.1.1 | 1273 | | DER: 06 07 67 81 12 01 02 01 01 | 1274 | | Comments: | 1275 +-------+-----------------------------------------------------------+ 1276 | 12 | Name: Remote SIM Provisioning Role | 1277 | | eUICC Manufacturer | 1278 | | Identifiers: id-rspRole-eum | 1279 | | OID: 2.23.146.1.2.1.2 | 1280 | | DER: 06 07 67 81 12 01 02 01 02 | 1281 | | Comments: | 1282 +-------+-----------------------------------------------------------+ 1283 | 13 | Name: Remote SIM Provisioning Role | 1284 | | SM-DP+ TLS | 1285 | | Identifiers: id-rspRole-dp-tls | 1286 | | OID: 2.23.146.1.2.1.3 | 1287 | | DER: 06 07 67 81 12 01 02 01 03 | 1288 | | Comments: | 1289 +-------+-----------------------------------------------------------+ 1290 | 14 | Name: Remote SIM Provisioning Role | 1291 | | SM-DP+ Authentication | 1292 | | Identifiers: id-rspRole-dp-auth | 1293 | | OID: 2.23.146.1.2.1.4 | 1294 | | DER: 06 07 67 81 12 01 02 01 04 | 1295 | | Comments: | 1296 +-------+-----------------------------------------------------------+ 1297 | 15 | Name: Remote SIM Provisioning Role | 1298 | | SM-DP+ Profile Binding | 1299 | | Identifiers: id-rspRole-dp-pb | 1300 | | OID: 2.23.146.1.2.1.5 | 1301 | | DER: 06 07 67 81 12 01 02 01 05 | 1302 | | Comments: | 1303 +-------+-----------------------------------------------------------+ 1304 | 16 | Name: Remote SIM Provisioning Role | 1305 | | SM-DS TLS | 1306 | | Identifiers: id-rspRole-ds-tls | 1307 | | OID: 2.23.146.1.2.1.6 | 1308 | | DER: 06 07 67 81 12 01 02 01 06 | 1309 | | Comments: | 1310 +-------+-----------------------------------------------------------+ 1311 | 17 | Name: Remote SIM Provisioning Role | 1312 | | SM-DS Authentication | 1313 | | Identifiers: id-rspRole-ds-auth | 1314 | | OID: 2.23.146.1.2.1.7 | 1315 | | DER: 06 07 67 81 12 01 02 01 07 | 1316 | | Comments: | 1317 +-------+-----------------------------------------------------------+ 1319 Figure 9: C509 Certificate Policies 1321 11.5. C509 Policies Qualifiers Registry 1323 IANA has created a new registry titled "C509 Policies Qualifiers 1324 Registry" under the new heading "CBOR Encoded X509 Certificates (C509 1325 Certificates)". The columns of the registry are Value, Name, 1326 Identifiers, OID, DER, Comments, and Reference, where Value is an 1327 integer, and the other columns are text strings. For values in the 1328 interval [-24, 23] the registration procedure is "IETF Review" and 1329 "Expert Review". For all other values the registration procedure is 1330 "Expert Review". The initial contents of the registry are: 1332 +-------+-----------------------------------------------------------+ 1333 | Value | Certificate Policy | 1334 +=======+===========================================================+ 1335 | 1 | Name: Certification Practice Statement | 1336 | | Identifiers: id-qt-cps, cps | 1337 | | OID: 1.3.6.1.5.5.7.2.1 | 1338 | | DER: 06 08 2B 06 01 05 05 07 02 01 | 1339 | | Comments: | 1340 +-------+-----------------------------------------------------------+ 1341 | 2 | Name: User Notice | 1342 | | Identifiers: id-qt-unotice, unotice | 1343 | | OID: 1.3.6.1.5.5.7.2.2 | 1344 | | DER: 06 08 2B 06 01 05 05 07 02 02 | 1345 | | Comments: | 1346 +-------+-----------------------------------------------------------+ 1348 Figure 10: C509 Policies Qualifiers 1350 11.6. C509 Information Access Registry 1352 IANA has created a new registry titled "C509 Information Access 1353 Registry" under the new heading "CBOR Encoded X509 Certificates (C509 1354 Certificates)". The columns of the registry are Value, Name, 1355 Identifiers, OID, DER, Comments, and Reference, where Value is an 1356 integer, and the other columns are text strings. For values in the 1357 interval [-24, 23] the registration procedure is "IETF Review" and 1358 "Expert Review". For all other values the registration procedure is 1359 "Expert Review". The initial contents of the registry are: 1361 +-------+-----------------------------------------------------------+ 1362 | Value | Information Access | 1363 +=======+===========================================================+ 1364 | 1 | Name: OCSP | 1365 | | Identifiers: id-ad-ocsp, id-pkix-ocsp | 1366 | | OID: 1.3.6.1.5.5.7.48.1 | 1367 | | DER: 06 08 2B 06 01 05 05 07 30 01 | 1368 | | Comments: | 1369 +-------+-----------------------------------------------------------+ 1370 | 2 | Name: CA Issuers | 1371 | | Identifiers: id-ad-caIssuers, caIssuers | 1372 | | OID: 1.3.6.1.5.5.7.48.2 | 1373 | | DER: 06 08 2B 06 01 05 05 07 30 02 | 1374 | | Comments: | 1375 +-------+-----------------------------------------------------------+ 1376 | 3 | Name: Time Stamping | 1377 | | Identifiers: id-ad-timeStamping, timeStamping | 1378 | | OID: 1.3.6.1.5.5.7.48.3 | 1379 | | DER: 06 08 2B 06 01 05 05 07 30 03 | 1380 | | Comments: | 1381 +-------+-----------------------------------------------------------+ 1382 | 5 | Name: CA Repository | 1383 | | Identifiers: id-ad-caRepository | 1384 | | OID: 1.3.6.1.5.5.7.48.5 | 1385 | | DER: 06 08 2B 06 01 05 05 07 30 05 | 1386 | | Comments: | 1387 +-------+-----------------------------------------------------------+ 1388 | 10 | Name: RPKI Manifest | 1389 | | Identifiers: id-ad-rpkiManifest | 1390 | | OID: 1.3.6.1.5.5.7.48.10 | 1391 | | DER: 06 08 2B 06 01 05 05 07 30 0A | 1392 | | Comments: RFC 6487 | 1393 +-------+-----------------------------------------------------------+ 1394 | 11 | Name: Signed Object | 1395 | | Identifiers: id-ad-signedObject | 1396 | | OID: 1.3.6.1.5.5.7.48.11 | 1397 | | DER: 06 08 2B 06 01 05 05 07 30 0B | 1398 | | Comments: RFC 6487 | 1399 +-------+-----------------------------------------------------------+ 1400 | 13 | Name: RPKI Notify | 1401 | | Identifiers: id-ad-rpkiNotify | 1402 | | OID: 1.3.6.1.5.5.7.48.13 | 1403 | | DER: 06 08 2B 06 01 05 05 07 30 0D | 1404 | | Comments: RFC 8182 | 1405 +-------+-----------------------------------------------------------+ 1407 Figure 11: C509 Information Accesses 1409 11.7. C509 Extended Key Usages Registry 1411 IANA has created a new registry titled "C509 Extended Key Usages 1412 Registry" under the new heading "CBOR Encoded X509 Certificates (C509 1413 Certificates)". The columns of the registry are Value, Name, 1414 Identifiers, OID, DER, Comments, and Reference, where Value is an 1415 integer, and the other columns are text strings. For values in the 1416 interval [-24, 23] the registration procedure is "IETF Review" and 1417 "Expert Review". For all other values the registration procedure is 1418 "Expert Review". The initial contents of the registry are: 1420 +-------+---------------------------------------------------------+ 1421 | Value | Extended Key Usage | 1422 +=======+=========================================================+ 1423 | 0 | Name: Any Extended Key Usage | 1424 | | Identifiers: anyExtendedKeyUsage | 1425 | | OID: 2.5.29.37.0 | 1426 | | DER: 06 04 55 1D 25 00 | 1427 | | Comments: RFC 5280 | 1428 +-------+---------------------------------------------------------+ 1429 | 1 | Name: TLS Server authentication | 1430 | | Identifiers: id-kp-serverAuth | 1431 | | OID: 1.3.6.1.5.5.7.3.1 | 1432 | | DER: 06 08 2B 06 01 05 05 07 03 01 | 1433 | | Comments: RFC 5280 | 1434 +-------+---------------------------------------------------------+ 1435 | 2 | Name: TLS Client Authentication | 1436 | | Identifiers: id-kp-clientAuth | 1437 | | OID: 1.3.6.1.5.5.7.3.2 | 1438 | | DER: 06 08 2B 06 01 05 05 07 03 02 | 1439 | | Comments: RFC 5280 | 1440 +-------+---------------------------------------------------------+ 1441 | 3 | Name: Code Signing | 1442 | | Identifiers: id-kp-codeSigning | 1443 | | OID: 1.3.6.1.5.5.7.3.3 | 1444 | | DER: 06 08 2B 06 01 05 05 07 03 03 | 1445 | | Comments: RFC 5280 | 1446 +-------+---------------------------------------------------------+ 1447 | 4 | Name: Email protection (S/MIME) | 1448 | | Identifiers: id-kp-emailProtection | 1449 | | OID: 1.3.6.1.5.5.7.3.4 | 1450 | | DER: 06 08 2B 06 01 05 05 07 03 04 | 1451 | | Comments: RFC 5280 | 1452 +-------+---------------------------------------------------------+ 1453 | 8 | Name: Time Stamping | 1454 | | Identifiers: id-kp-timeStamping, timestamping | 1455 | | OID: 1.3.6.1.5.5.7.3.8 | 1456 | | DER: 06 08 2B 06 01 05 05 07 03 08 | 1457 | | Comments: | 1458 +-------+---------------------------------------------------------+ 1459 | 9 | Name: OCSP Signing | 1460 | | Identifiers: id-kp-OCSPSigning | 1461 | | OID: 1.3.6.1.5.5.7.3.9 | 1462 | | DER: 06 08 2B 06 01 05 05 07 03 09 | 1463 | | Comments: RFC 5280 | 1464 +-------+---------------------------------------------------------+ 1465 | 10 | Name: Kerberos PKINIT Client Auth | 1466 | | Identifiers: id-pkinit-KPClientAuth | 1467 | | OID: 1.3.6.1.5.2.3.4 | 1468 | | DER: 06 07 2B 06 01 05 02 03 04 | 1469 | | Comments: RFC 4556 | 1470 +-------+---------------------------------------------------------+ 1471 | 11 | Name: Kerberos PKINIT KDC | 1472 | | Identifiers: id-pkinit-KPKdc | 1473 | | OID: 1.3.6.1.5.2.3.5 | 1474 | | DER: 06 07 2B 06 01 05 02 03 05 | 1475 | | Comments: RFC 4556 | 1476 +-------+---------------------------------------------------------+ 1477 | 12 | Name: SSH Client | 1478 | | Identifiers: id-kp-secureShellClient | 1479 | | OID: 1.3.6.1.5.5.7.3.21 | 1480 | | DER: 06 08 2B 06 01 05 05 07 03 15 | 1481 | | Comments: RFC 6187 | 1482 +-------+---------------------------------------------------------+ 1483 | 13 | Name: Kerberos PKINIT KDC | 1484 | | Identifiers: id-pkinit-KPKdc | 1485 | | OID: 1.3.6.1.5.5.7.3.22 | 1486 | | DER: 06 08 2B 06 01 05 05 07 03 16 | 1487 | | Comments: RFC 6187 | 1488 +-------+---------------------------------------------------------+ 1490 Figure 12: C509 Extended Key Usages 1492 11.8. C509 General Names Registry 1494 IANA has created a new registry titled "C509 General Names Registry" 1495 under the new heading "CBOR Encoded X509 Certificates (C509 1496 Certificates)". The columns of the registry are Value, General Name, 1497 and Reference, where Value is an integer, and the other columns are 1498 text strings. For values in the interval [-24, 23] the registration 1499 procedure is "IETF Review" and "Expert Review". For all other values 1500 the registration procedure is "Expert Review". The initial contents 1501 of the registry are: 1503 +-------+-----------------------------------------------------------+ 1504 | Value | General Names | 1505 +=======+===========================================================+ 1506 | -2 | Name: otherName with SmtpUTF8Mailbox | 1507 | | Comments: id-on-SmtpUTF8Mailbox | 1508 | | (1.3.6.1.5.5.7.8.9) | 1509 | | 06 08 2B 06 01 05 05 07 08 09 | 1510 | | Value: text | 1511 +-------+-----------------------------------------------------------+ 1512 | -1 | Name: otherName with hardwareModuleName | 1513 | | Comments: id-on-hardwareModuleNamee | 1514 | | (1.3.6.1.5.5.7.8.4) | 1515 | | 06 08 2B 06 01 05 05 07 08 04 | 1516 | | Value: [ ~oid, bytes ] | 1517 +-------+-----------------------------------------------------------+ 1518 | 0 | Name: otherName | 1519 | | Comments: | 1520 | | Value: [ ~oid, bytes ] | 1521 +-------+-----------------------------------------------------------+ 1522 | 1 | Name: rfc822Name | 1523 | | Comments: | 1524 | | Value: text | 1525 +-------+-----------------------------------------------------------+ 1526 | 2 | Name: dNSName | 1527 | | Comments: | 1528 | | Value: text | 1529 +-------+-----------------------------------------------------------+ 1530 | 4 | Name: directoryName | 1531 | | Comments: | 1532 | | Value: Name | 1533 +-------+-----------------------------------------------------------+ 1534 | 6 | Name: uniformResourceIdentifier | 1535 | | Comments: | 1536 | | Value: text | 1537 +-------+-----------------------------------------------------------+ 1538 | 7 | Name: iPAddress | 1539 | | Comments: | 1540 | | Value: bytes | 1541 +-------+-----------------------------------------------------------+ 1542 | 8 | Name: registeredID | 1543 | | Comments: | 1544 | | Value: ~oid | 1545 +-------+-----------------------------------------------------------+ 1547 Figure 13: C509 General Names 1549 11.9. C509 Signature Algorithms Registry 1551 IANA has created a new registry titled "C509 Signature Algorithms" 1552 under the new heading "CBOR Encoded X509 Certificates (C509 1553 Certificates)". The columns of the registry are Value, Name, 1554 Identifiers, OID, Parameters, DER, Comments, and Reference, where 1555 Value is an integer, and the other columns are text strings. For 1556 values in the interval [-24, 23] the registration procedure is "IETF 1557 Review" and "Expert Review". For all other values the registration 1558 procedure is "Expert Review". The initial contents of the registry 1559 are: 1561 +-------+-----------------------------------------------------------+ 1562 | Value | X.509 Signature Algorithms | 1563 +=======+===========================================================+ 1564 | -256 | Name: RSASSA-PKCS1-v1_5 with SHA-1 | 1565 | | Identifiers: sha1-with-rsa-signature, | 1566 | | sha1WithRSAEncryption, | 1567 | | sha-1WithRSAEncryption | 1568 | | OID: 1.2.840.113549.1.1.5 | 1569 | | Parameters: NULL | 1570 | | DER: 30 0D 06 09 2A 86 48 86 F7 0D 01 01 05 05 00 | 1571 | | Comments: Don't use | 1572 +-------+-----------------------------------------------------------+ 1573 | -255 | Name: ECDSA with SHA-1 | 1574 | | Identifiers: ecdsa-with-SHA1 | 1575 | | OID: 1.2.840.10045.4.1 | 1576 | | Parameters: Absent | 1577 | | DER: 30 09 06 07 2A 86 48 CE 3D 04 01 | 1578 | | Comments: Don't use. Compressed signature value | 1579 +-------+-----------------------------------------------------------+ 1580 | 0 | Name: ECDSA with SHA-256 | 1581 | | Identifiers: ecdsa-with-SHA256 | 1582 | | OID: 1.2.840.10045.4.3.2 | 1583 | | Parameters: Absent | 1584 | | DER: 30 0A 06 08 2A 86 48 CE 3D 04 03 02 | 1585 | | Comments: Compressed signature value | 1586 +-------+-----------------------------------------------------------+ 1587 | 1 | Name: ECDSA with SHA-384 | 1588 | | Identifiers: ecdsa-with-SHA384 | 1589 | | OID: 1.2.840.10045.4.3.3 | 1590 | | Parameters: Absent | 1591 | | DER: 30 0A 06 08 2A 86 48 CE 3D 04 03 03 | 1592 | | Comments: Compressed signature value | 1593 +-------+-----------------------------------------------------------+ 1594 | 2 | Name: ECDSA with SHA-512 | 1595 | | Identifiers: ecdsa-with-SHA512 | 1596 | | OID: 1.2.840.10045.4.3.4 | 1597 | | Parameters: Absent | 1598 | | DER: 30 0A 06 08 2A 86 48 CE 3D 04 03 04 | 1599 | | Comments: Compressed signature value | 1600 +-------+-----------------------------------------------------------+ 1601 | 3 | Name: ECDSA with SHAKE128 | 1602 | | Identifiers: id-ecdsa-with-shake128 | 1603 | | OID: 1.3.6.1.5.5.7.6.32 | 1604 | | Parameters: Absent | 1605 | | DER: 30 0A 06 08 2B 06 01 05 05 07 06 20 | 1606 | | Comments: Compressed signature value | 1607 +-------+-----------------------------------------------------------+ 1608 | 4 | Name: ECDSA with SHAKE256 | 1609 | | Identifiers: id-ecdsa-with-shake256 | 1610 | | OID: 1.3.6.1.5.5.7.6.33 | 1611 | | Parameters: Absent | 1612 | | DER: 30 0A 06 08 2B 06 01 05 05 07 06 21 | 1613 | | Comments: Compressed signature value | 1614 +-------+-----------------------------------------------------------+ 1615 | 12 | Name: Ed25519 | 1616 | | Identifiers: id-Ed25519, id-EdDSA25519 | 1617 | | OID: 1.3.101.112 | 1618 | | Parameters: Absent | 1619 | | DER: 30 05 06 03 2B 65 70 | 1620 | | Comments: | 1621 +-------+-----------------------------------------------------------+ 1622 | 13 | Name: Ed448 | 1623 | | Identifiers: id-Ed448, id-EdDSA448 | 1624 | | OID: 1.3.101.113 | 1625 | | Parameters: Absent | 1626 | | DER: 30 05 06 03 2B 65 71 | 1627 | | Comments: | 1628 +-------+-----------------------------------------------------------+ 1629 | 23 | Name: RSASSA-PKCS1-v1_5 with SHA-256 | 1630 | | Identifiers: sha256WithRSAEncryption | 1631 | | OID: 1.2.840.113549.1.1.11 | 1632 | | Parameters: NULL | 1633 | | DER: 30 0B 06 09 2A 86 48 86 F7 0D 01 01 0B 05 00 | 1634 | | Comments: | 1635 +-------+-----------------------------------------------------------+ 1636 | 24 | Name: RSASSA-PKCS1-v1_5 with SHA-384 | 1637 | | Identifiers: sha384WithRSAEncryption | 1638 | | OID: 1.2.840.113549.1.1.12 | 1639 | | Parameters: NULL | 1640 | | DER: 30 0B 06 09 2A 86 48 86 F7 0D 01 01 0C 05 00 | 1641 | | Comments: | 1642 +-------+-----------------------------------------------------------+ 1643 | 25 | Name: RSASSA-PKCS1-v1_5 with SHA-512 | 1644 | | Identifiers: sha512WithRSAEncryption | 1645 | | OID: 1.2.840.113549.1.1.13 | 1646 | | Parameters: NULL | 1647 | | DER: 30 0B 06 09 2A 86 48 86 F7 0D 01 01 0D 05 00 | 1648 | | Comments: | 1649 +-------+-----------------------------------------------------------+ 1650 | 26 | Name: RSASSA-PSS with SHA-256 | 1651 | | Identifiers: rsassa-pss, id-RSASSA-PSS | 1652 | | OID: 1.2.840.113549.1.1.10 | 1653 | | Parameters: SHA-256, MGF-1 with SHA-256, saltLength = 32 | 1654 | | DER: 30 41 06 09 2A 86 48 86 F7 0D 01 01 0A 30 34 | 1655 | | A0 0F 30 0D 06 09 60 86 48 01 65 03 04 02 01 | 1656 | | 05 00 A1 1C 30 1A 06 09 2A 86 48 86 F7 0D 01 | 1657 | | 01 08 30 0D 06 09 60 86 48 01 65 03 04 02 01 | 1658 | | 05 00 a2 03 02 01 20 | 1659 | | Comments: | 1660 +-------+-----------------------------------------------------------+ 1661 | 27 | Name: RSASSA-PSS with SHA-384 | 1662 | | Identifiers: rsassa-pss, id-RSASSA-PSS | 1663 | | OID: 1.2.840.113549.1.1.10 | 1664 | | Parameters: SHA-384, MGF-1 with SHA-384, saltLength = 48 | 1665 | | DER: 30 41 06 09 2A 86 48 86 F7 0D 01 01 0A 30 34 | 1666 | | A0 0F 30 0D 06 09 60 86 48 01 65 03 04 02 02 | 1667 | | 05 00 A1 1C 30 1A 06 09 2A 86 48 86 F7 0D 01 | 1668 | | 01 08 30 0D 06 09 60 86 48 01 65 03 04 02 02 | 1669 | | 05 00 A2 03 02 01 30 | 1670 | | Comments: | 1671 +-------+-----------------------------------------------------------+ 1672 | 28 | Name: RSASSA-PSS with SHA-512 | 1673 | | Identifiers: rsassa-pss, id-RSASSA-PSS | 1674 | | OID: 1.2.840.113549.1.1.10 | 1675 | | Parameters: SHA-512, MGF-1 with SHA-512, saltLength = 64 | 1676 | | DER: 30 41 06 09 2A 86 48 86 F7 0D 01 01 0A 30 34 | 1677 | | A0 0F 30 0D 06 09 60 86 48 01 65 03 04 02 03 | 1678 | | 05 00 A1 1C 30 1A 06 09 2A 86 48 86 F7 0D 01 | 1679 | | 01 08 30 0D 06 09 60 86 48 01 65 03 04 02 03 | 1680 | | 05 00 A2 03 02 01 40 | 1681 | | Comments: | 1682 +-------+-----------------------------------------------------------+ 1683 | 29 | Name: RSASSA-PSS with SHAKE128 | 1684 | | Identifiers: id-RSASSA-PSS-SHAKE128 | 1685 | | OID: 1.3.6.1.5.5.7.6.30 | 1686 | | Parameters: Absent | 1687 | | DER: 30 0A 06 08 2B 06 01 05 05 07 06 1E | 1688 | | Comments: | 1689 +-------+-----------------------------------------------------------+ 1690 | 30 | Name: RSASSA-PSS with SHAKE256 | 1691 | | Identifiers: id-RSASSA-PSS-SHAKE256 | 1692 | | OID: 1.3.6.1.5.5.7.6.31 | 1693 | | Parameters: Absent | 1694 | | DER: 30 0A 06 08 2B 06 01 05 05 07 06 1F | 1695 | | Comments: | 1696 +-------+-----------------------------------------------------------+ 1697 | 42 | Name: HSS / LMS | 1698 | | Identifiers: id-alg-hss-lms-hashsig, id-alg-mts-hashsig | 1699 | | OID: 1.2.840.113549.1.9.16.3.17 | 1700 | | Parameters: Absent | 1701 | | DER: 30 0D 06 0B 2A 86 48 86 F7 0D 01 09 10 03 11 | 1702 | | Comments: | 1703 +-------+-----------------------------------------------------------+ 1704 | 43 | Name: XMSS | 1705 | | Identifiers: id_alg_xmss | 1706 | | OID: 0.4.0.127.0.15.1.1.13.0 | 1707 | | Parameters: Absent | 1708 | | DER: 30 0B 06 09 04 00 7F 00 0F 01 01 0D 00 | 1709 | | Comments: | 1710 +-------+-----------------------------------------------------------+ 1711 | 44 | Name: XMSS^MT | 1712 | | Identifiers: id_alg_xmssmt | 1713 | | OID: 0.4.0.127.0.15.1.1.14.0 | 1714 | | Parameters: Absent | 1715 | | DER: 30 0B 06 09 04 00 7F 00 0F 01 01 0E 00 | 1716 | | Comments: | 1717 +-------+-----------------------------------------------------------+ 1719 Figure 14: C509 Signature Algorithms 1721 11.10. C509 Public Key Algorithms Registry 1723 IANA has created a new registry titled "C509 Public Key Algorithms" 1724 under the new heading "CBOR Encoded X509 Certificates (C509 1725 Certificates)". The columns of the registry are Value, Name, 1726 Identifiers, OID, Parameters, DER, Comments, and Reference, where 1727 Value is an integer, and the other columns are text strings. For 1728 values in the interval [-24, 23] the registration procedure is "IETF 1729 Review" and "Expert Review". For all other values the registration 1730 procedure is "Expert Review". T The initial contents of the registry 1731 are: 1733 +-------+-----------------------------------------------------------+ 1734 | Value | X.509 Public Key Algorithms | 1735 +=======+===========================================================+ 1736 | 0 | Name: RSA | 1737 | | Identifiers: rsaEncryption | 1738 | | OID: 1.2.840.113549.1.1.1 | 1739 | | Parameters: NULL | 1740 | | DER: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 01 05 00 | 1741 | | Comments: Compressed subjectPublicKey | 1742 +-------+-----------------------------------------------------------+ 1743 | 1 | Name: EC Public Key (Weierstrass) with secp256r1 | 1744 | | Identifiers: ecPublicKey, id-ecPublicKey | 1745 | | OID: 1.2.840.10045.2.1 | 1746 | | Parameters: namedCurve = secp256r1 (1.2.840.10045.3.1.7) | 1747 | | DER: 30 13 06 07 2A 86 48 CE 3D 02 01 06 08 2A 86 | 1748 | | 48 CE 3D 03 01 07 | 1749 | | Comments: Point compressed subjectPublicKey | 1750 | | Also known as P-256, ansip256r1, prime256v1 | 1751 +-------+-----------------------------------------------------------+ 1752 | 2 | Name: EC Public Key (Weierstrass) with secp384r1 | 1753 | | Identifiers: ecPublicKey, id-ecPublicKey | 1754 | | OID: 1.2.840.10045.2.1 | 1755 | | Parameters: namedCurve = secp384r1 (1.3.132.0.34) | 1756 | | DER: 30 10 06 07 2A 86 48 CE 3D 02 01 06 05 2B 81 | 1757 | | 04 00 22 | 1758 | | Comments: Point compressed subjectPublicKey | 1759 | | Also known as P-384, ansip384r1 | 1760 +-------+-----------------------------------------------------------+ 1761 | 3 | Name: EC Public Key (Weierstrass) with secp521r1 | 1762 | | Identifiers: ecPublicKey, id-ecPublicKey | 1763 | | OID: 1.2.840.10045.2.1 | 1764 | | Parameters: namedCurve = secp521r1 (1.3.132.0.35) | 1765 | | DER: 30 10 06 07 2A 86 48 CE 3D 02 01 06 05 2B 81 | 1766 | | 04 00 23 | 1767 | | Comments: Point compressed subjectPublicKey | 1768 | | Also known as P-521, ansip521r1 | 1769 +-------+-----------------------------------------------------------+ 1770 | 8 | Name: X25519 (Montgomery) | 1771 | | Identifiers: id-X25519 | 1772 | | OID: 1.3.101.110 | 1773 | | Parameters: Absent | 1774 | | DER: 30 05 06 03 2B 65 6E | 1775 | | Comments: | 1776 +-------+-----------------------------------------------------------+ 1777 | 9 | Name: X448 (Montgomery) | 1778 | | Identifiers: id-X448 | 1779 | | OID: 1.3.101.111 | 1780 | | Parameters: Absent | 1781 | | DER: 30 05 06 03 2B 65 6F | 1782 | | Comments: | 1783 +-------+-----------------------------------------------------------+ 1784 | 10 | Name: Ed25519 (Twisted Edwards) | 1785 | | Identifiers: id-Ed25519, id-EdDSA25519 | 1786 | | OID: 1.3.101.112 | 1787 | | Parameters: Absent | 1788 | | DER: 30 05 06 03 2B 65 70 | 1789 | | Comments: | 1790 +-------+-----------------------------------------------------------+ 1791 | 11 | Name: Ed448 (Edwards) | 1792 | | Identifiers: id-Ed448, id-EdDSA448 | 1793 | | OID: 1.3.101.113 | 1794 | | Parameters: Absent | 1795 | | DER: 30 05 06 03 2B 65 71 | 1796 | | Comments: | 1797 +-------+-----------------------------------------------------------+ 1798 | 16 | Name: HSS / LMS | 1799 | | Identifiers: id-alg-hss-lms-hashsig, id-alg-mts-hashsig | 1800 | | OID: 1.2.840.113549.1.9.16.3.17 | 1801 | | Parameters: Absent | 1802 | | DER: 30 0D 06 0B 2A 86 48 86 F7 0D 01 09 10 03 11 | 1803 | | Comments: | 1804 +-------+-----------------------------------------------------------+ 1805 | 17 | Name: XMSS | 1806 | | Identifiers: id_alg_xmss | 1807 | | OID: 0.4.0.127.0.15.1.1.13.0 | 1808 | | Parameters: Absent | 1809 | | DER: 30 0B 06 09 04 00 7F 00 0F 01 01 0D 00 | 1810 | | Comments: | 1811 +-------+-----------------------------------------------------------+ 1812 | 18 | Name: XMSS^MT | 1813 | | Identifiers: id_alg_xmssmt | 1814 | | OID: 0.4.0.127.0.15.1.1.14.0 | 1815 | | Parameters: Absent | 1816 | | DER: 30 0B 06 09 04 00 7F 00 0F 01 01 0E 00 | 1817 | | Comments: | 1818 +-------+-----------------------------------------------------------+ 1819 | 24 | Name: EC Public Key (Weierstrass) with | 1820 | | brainpoolP256r1 | 1821 | | Identifiers: ecPublicKey, id-ecPublicKey | 1822 | | OID: 1.2.840.10045.2.1 | 1823 | | Parameters: namedCurve = brainpoolP256r1 | 1824 | | (1.3.36.3.3.2.8.1.1.7) | 1825 | | DER: 30 13 06 07 2A 86 48 CE 3D 02 01 06 09 2B 24 | 1826 | | 03 03 02 08 01 01 07 | 1827 | | Comments: Point compressed subjectPublicKey | 1828 +-------+-----------------------------------------------------------+ 1829 | 25 | Name: EC Public Key (Weierstrass) with | 1830 | | brainpoolP384r1 | 1831 | | Identifiers: ecPublicKey, id-ecPublicKey | 1832 | | OID: 1.2.840.10045.2.1 | 1833 | | Parameters: namedCurve = brainpoolP384r1 | 1834 | | (1.3.36.3.3.2.8.1.1.11) | 1835 | | DER: 30 13 06 07 2A 86 48 CE 3D 02 01 06 09 2B 24 | 1836 | | 03 03 02 08 01 01 0B | 1837 | | Comments: Point compressed subjectPublicKey | 1838 +-------+-----------------------------------------------------------+ 1839 | 26 | Name: EC Public Key (Weierstrass) with | 1840 | | brainpoolP512r1 | 1841 | | Identifiers: ecPublicKey, id-ecPublicKey | 1842 | | OID: 1.2.840.10045.2.1 | 1843 | | Parameters: namedCurve = brainpoolP512r1 | 1844 | | (1.3.36.3.3.2.8.1.1.13) | 1845 | | DER: 30 13 06 07 2A 86 48 CE 3D 02 01 06 09 2B 24 | 1846 | | 03 03 02 08 01 01 0D | 1847 | | Comments: Point compressed subjectPublicKey | 1848 +-------+-----------------------------------------------------------+ 1849 | 27 | Name: EC Public Key (Weierstrass) with | 1850 | | FRP256v1 | 1851 | | Identifiers: ecPublicKey, id-ecPublicKey | 1852 | | OID: 1.2.840.10045.2.1 | 1853 | | Parameters: namedCurve = FRP256v1 | 1854 | | (1.2.250.1.223.101.256.1) | 1855 | | DER: 30 13 06 07 2A 86 48 CE 3D 02 01 06 0A 2A 81 | 1856 | | 7A 01 81 5F 65 82 00 01 | 1857 | | Comments: Point compressed subjectPublicKey | 1858 +-------+-----------------------------------------------------------+ 1860 Figure 15: C509 Public Key Algorithms 1862 11.11. COSE Header Parameters Registry 1864 EDITORS NOTE: The text should be moved a section and not be in the 1865 IANA Section. 1867 This document registers the following entries in the "COSE Header 1868 Parameters" registry under the "CBOR Object Signing and Encryption 1869 (COSE)" heading. The formatting and processing for c5b, c5c, and 1870 c5t, and c5u are similar to x5bag, x5chain, x5t, x5u defined in 1871 [I-D.ietf-cose-x509] except that the certificates are C509 instead of 1872 DER encoded X.509 and uses a COSE_C509 structure instead of 1873 COSE_X509. c5u provides an alternative way to identify an untrusted 1874 certificate bag/chain by reference with a URI. The content is a 1875 COSE_C509 item served with the application/cbor content format. The 1876 COSE_C509 structure used in c5b, c5c, and c5u is defined as: 1878 COSE_C509 = C509Certificate / [ 2* C509Certificate ] 1880 As the contents of c5bag, c5chain, c5t, and c5u are untrusted input, 1881 the header parameters can be in either the protected or unprotected 1882 header bucket. The trust mechanism MUST process any certificates in 1883 the c5b, c5c, and c5u parameters as untrusted input. The presence of 1884 a self-signed certificate in the parameter MUST NOT cause the update 1885 of the set of trust anchors without some out-of-band confirmation. 1887 Note that certificates can also be identified with a 'kid' header 1888 parameter by storing 'kid' and the associated bag or chain in a 1889 dictionary. 1891 +-----------+-------+----------------+------------------------------+ 1892 | Name | Label | Value Type | Description | 1893 +===========+=======+================+==============================+ 1894 | c5b | TBD1 | COSE_C509 | An unordered bag of C509 | 1895 | | | | certificates | 1896 +-----------+-------+----------------+------------------------------+ 1897 | c5c | TBD2 | COSE_C509 | An ordered chain of C509 | 1898 | | | | certificates | 1899 +-----------+-------+----------------+------------------------------+ 1900 | c5t | TBD3 | COSE_CertHash | Hash of a C509Certificate | 1901 +-----------+-------+----------------+------------------------------+ 1902 | c5u | TBD4 | uri | URI pointing to a COSE_C509 | 1903 | | | | containing a ordered chain | 1904 | | | | of certificates | 1905 +-----------+-------+----------------+------------------------------+ 1907 11.12. TLS Certificate Types Registry 1909 This document registers the following entry in the "TLS Certificate 1910 Types" registry under the "Transport Layer Security (TLS) Extensions" 1911 heading. The new certificate type can be used with additional TLS 1912 certificate compression [RFC8879]. C509 is defined in the same way 1913 as as X509, but uses a different value and instead of DER-encoded 1914 X.509 certificate, opaque cert_data<1..2^24-1> contains a the CBOR 1915 sequence ~C509Certificate (an unwrapped C509Certificate). 1917 EDITOR'S NOTE: The TLS registrations should be discussed and approved 1918 by the TLS WG at a later stage. When COSE WG has adopted work on 1919 C509 certificates, it could perhaps be presented in the TLS WG. The 1920 TLS WG might e.g. want a separate draft in the TLS WG. 1922 +-------+------------------+-------------+--------------------------+ 1923 | Value | Name | Recommended | Comment | 1924 +=======+==================+=============+==========================+ 1925 | TBD5 | C509 Certificate | Y | | 1926 +-------+------------------+-------------+--------------------------+ 1928 11.13. CBOR Tags Registry 1930 This document registers the following entries in the "CBOR Tags" 1931 registry under the "Concise Binary Object Representation (CBOR) Tags" 1932 heading. 1934 +------+------------------------------------------------------------+ 1935 | Tag | X.509 Public Key Algorithms | 1936 +======+============================================================+ 1937 | TDB6 | Data Item: COSE_C509 | 1938 | | Semantics: An ordered chain of C509 certificates | 1939 | | Reference: This document | 1940 +------+------------------------------------------------------------+ 1942 12. References 1944 12.1. Normative References 1946 [I-D.ietf-cbor-tags-oid] 1947 Bormann, C., "Concise Binary Object Representation (CBOR) 1948 Tags for Object Identifiers", draft-ietf-cbor-tags-oid-06 1949 (work in progress), March 2021. 1951 [I-D.ietf-cose-x509] 1952 Schaad, J., "CBOR Object Signing and Encryption (COSE): 1953 Header parameters for carrying and referencing X.509 1954 certificates", draft-ietf-cose-x509-08 (work in progress), 1955 December 2020. 1957 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1958 Requirement Levels", BCP 14, RFC 2119, 1959 DOI 10.17487/RFC2119, March 1997, 1960 . 1962 [RFC2986] Nystrom, M. and B. Kaliski, "PKCS #10: Certification 1963 Request Syntax Specification Version 1.7", RFC 2986, 1964 DOI 10.17487/RFC2986, November 2000, 1965 . 1967 [RFC4108] Housley, R., "Using Cryptographic Message Syntax (CMS) to 1968 Protect Firmware Packages", RFC 4108, 1969 DOI 10.17487/RFC4108, August 2005, 1970 . 1972 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 1973 Housley, R., and W. Polk, "Internet X.509 Public Key 1974 Infrastructure Certificate and Certificate Revocation List 1975 (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, 1976 . 1978 [RFC8152] Schaad, J., "CBOR Object Signing and Encryption (COSE)", 1979 RFC 8152, DOI 10.17487/RFC8152, July 2017, 1980 . 1982 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1983 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1984 May 2017, . 1986 [RFC8610] Birkholz, H., Vigano, C., and C. Bormann, "Concise Data 1987 Definition Language (CDDL): A Notational Convention to 1988 Express Concise Binary Object Representation (CBOR) and 1989 JSON Data Structures", RFC 8610, DOI 10.17487/RFC8610, 1990 June 2019, . 1992 [RFC8742] Bormann, C., "Concise Binary Object Representation (CBOR) 1993 Sequences", RFC 8742, DOI 10.17487/RFC8742, February 2020, 1994 . 1996 [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object 1997 Representation (CBOR)", STD 94, RFC 8949, 1998 DOI 10.17487/RFC8949, December 2020, 1999 . 2001 [SECG] "Elliptic Curve Cryptography, Standards for Efficient 2002 Cryptography Group, ver. 2", 2009, 2003 . 2005 12.2. Informative References 2007 [CAB-Code] 2008 CA/Browser Forum, ., "CA/Browser Forum, "Baseline 2009 Requirements for the Issuance and Management of Publicly- 2010 Trusted Code Signing Certificates Version 2.3"", May 2021, 2011 . 2014 [CAB-TLS] CA/Browser Forum, ., "CA/Browser Forum, "Baseline 2015 Requirements for the Issuance and Management of Publicly- 2016 Trusted Certificates Version 1.7.6"", June 2021, 2017 . 2019 [CborMe] Bormann, C., "CBOR Playground", May 2018, 2020 . 2022 [GSMA-eUICC] 2023 GSMA, ., "GSMA eUICC PKI Certificate Policy Version 2.1", 2024 February 2021, . 2027 [I-D.ietf-emu-eap-tls13] 2028 Mattsson, J. and M. Sethi, "Using EAP-TLS with TLS 1.3 2029 (EAP-TLS 1.3)", draft-ietf-emu-eap-tls13-18 (work in 2030 progress), July 2021. 2032 [I-D.ietf-emu-eaptlscert] 2033 Sethi, M., Mattsson, J., and S. Turner, "Handling Large 2034 Certificates and Long Certificate Chains in TLS-based EAP 2035 Methods", draft-ietf-emu-eaptlscert-08 (work in progress), 2036 November 2020. 2038 [I-D.ietf-lake-edhoc] 2039 Selander, G., Mattsson, J. P., and F. Palombini, 2040 "Ephemeral Diffie-Hellman Over COSE (EDHOC)", draft-ietf- 2041 lake-edhoc-06 (work in progress), April 2021. 2043 [I-D.ietf-tls-ctls] 2044 Rescorla, E., Barnes, R., and H. Tschofenig, "Compact TLS 2045 1.3", draft-ietf-tls-ctls-01 (work in progress), November 2046 2020. 2048 [I-D.ietf-tls-dtls13] 2049 Rescorla, E., Tschofenig, H., and N. Modadugu, "The 2050 Datagram Transport Layer Security (DTLS) Protocol Version 2051 1.3", draft-ietf-tls-dtls13-43 (work in progress), April 2052 2021. 2054 [I-D.ietf-uta-tls13-iot-profile] 2055 Tschofenig, H. and T. Fossati, "TLS/DTLS 1.3 Profiles for 2056 the Internet of Things", draft-ietf-uta-tls13-iot- 2057 profile-01 (work in progress), February 2021. 2059 [IEEE-802.1AR] 2060 Institute of Electrical and Electronics Engineers, ., 2061 "IEEE Standard for Local and metropolitan area networks- 2062 Secure Device Identity", IEEE Standard 802.1AR-2018 , 2063 August 2018, 2064 . 2066 [RFC6487] Huston, G., Michaelson, G., and R. Loomans, "A Profile for 2067 X.509 PKIX Resource Certificates", RFC 6487, 2068 DOI 10.17487/RFC6487, February 2012, 2069 . 2071 [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for 2072 Constrained-Node Networks", RFC 7228, 2073 DOI 10.17487/RFC7228, May 2014, 2074 . 2076 [RFC7925] Tschofenig, H., Ed. and T. Fossati, "Transport Layer 2077 Security (TLS) / Datagram Transport Layer Security (DTLS) 2078 Profiles for the Internet of Things", RFC 7925, 2079 DOI 10.17487/RFC7925, July 2016, 2080 . 2082 [RFC7932] Alakuijala, J. and Z. Szabadka, "Brotli Compressed Data 2083 Format", RFC 7932, DOI 10.17487/RFC7932, July 2016, 2084 . 2086 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 2087 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 2088 . 2090 [RFC8603] Jenkins, M. and L. Zieglar, "Commercial National Security 2091 Algorithm (CNSA) Suite Certificate and Certificate 2092 Revocation List (CRL) Profile", RFC 8603, 2093 DOI 10.17487/RFC8603, May 2019, 2094 . 2096 [RFC8879] Ghedini, A. and V. Vasiliev, "TLS Certificate 2097 Compression", RFC 8879, DOI 10.17487/RFC8879, December 2098 2020, . 2100 [RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based 2101 Multiplexed and Secure Transport", RFC 9000, 2102 DOI 10.17487/RFC9000, May 2021, 2103 . 2105 [X.509-IoT] 2106 Forsby, F., Furuhed, M., Papadimitratos, P., and S. Raza, 2107 "Lightweight X.509 Digital Certificates for the Internet 2108 of Things.", Springer, Cham. Lecture Notes of the 2109 Institute for Computer Sciences, Social Informatics and 2110 Telecommunications Engineering, vol 242., July 2018, 2111 . 2113 Appendix A. Example C509 Certificates 2115 A.1. Example RFC 7925 profiled X.509 Certificate 2117 Example of [RFC7925] profiled X.509 certificate parsed with OpenSSL. 2119 Certificate: 2120 Data: 2121 Version: 3 (0x2) 2122 Serial Number: 128269 (0x1f50d) 2123 Signature Algorithm: ecdsa-with-SHA256 2124 Issuer: CN=RFC test CA 2125 Validity 2126 Not Before: Jan 1 00:00:00 2020 GMT 2127 Not After : Feb 2 00:00:00 2021 GMT 2128 Subject: CN=01-23-45-FF-FE-67-89-AB 2129 Subject Public Key Info: 2130 Public Key Algorithm: id-ecPublicKey 2131 Public-Key: (256 bit) 2132 pub: 2133 04:b1:21:6a:b9:6e:5b:3b:33:40:f5:bd:f0:2e:69: 2134 3f:16:21:3a:04:52:5e:d4:44:50:b1:01:9c:2d:fd: 2135 38:38:ab:ac:4e:14:d8:6c:09:83:ed:5e:9e:ef:24: 2136 48:c6:86:1c:c4:06:54:71:77:e6:02:60:30:d0:51: 2137 f7:79:2a:c2:06 2138 ASN1 OID: prime256v1 2139 NIST CURVE: P-256 2140 X509v3 extensions: 2141 X509v3 Key Usage: 2142 Digital Signature 2143 Signature Algorithm: ecdsa-with-SHA256 2144 30:44:02:20:44:5d:79:8c:90:e7:f5:00:dc:74:7a:65:4c:ec: 2145 6c:fa:6f:03:72:76:e1:4e:52:ed:07:fc:16:29:4c:84:66:0d: 2146 02:20:5a:33:98:5d:fb:d4:bf:dd:6d:4a:cf:38:04:c3:d4:6e: 2147 bf:3b:7f:a6:26:40:67:4f:c0:35:4f:a0:56:db:ae:a6 2149 The DER encoding of the above certificate is 314 bytes. 2151 30 82 01 36 30 81 DE A0 03 02 01 02 02 03 01 F5 0D 30 0A 06 08 2A 86 2152 48 CE 3D 04 03 02 30 16 31 14 30 12 06 03 55 04 03 0C 0B 52 46 43 20 2153 74 65 73 74 20 43 41 30 1E 17 0D 32 30 30 31 30 31 30 30 30 30 30 30 2154 5A 17 0D 32 31 30 32 30 32 30 30 30 30 30 30 5A 30 22 31 20 30 1E 06 2155 03 55 04 03 0C 17 30 31 2D 32 33 2D 34 35 2D 46 46 2D 46 45 2D 36 37 2156 2D 38 39 2D 41 42 30 59 30 13 06 07 2A 86 48 CE 3D 02 01 06 08 2A 86 2157 48 CE 3D 03 01 07 03 42 00 04 B1 21 6A B9 6E 5B 3B 33 40 F5 BD F0 2E 2158 69 3F 16 21 3A 04 52 5E D4 44 50 B1 01 9C 2D FD 38 38 AB AC 4E 14 D8 2159 6C 09 83 ED 5E 9E EF 24 48 C6 86 1C C4 06 54 71 77 E6 02 60 30 D0 51 2160 F7 79 2A C2 06 A3 0F 30 0D 30 0B 06 03 55 1D 0F 04 04 03 02 07 80 30 2161 0A 06 08 2A 86 48 CE 3D 04 03 02 03 47 00 30 44 02 20 44 5D 79 8C 90 2162 E7 F5 00 DC 74 7A 65 4C EC 6C FA 6F 03 72 76 E1 4E 52 ED 07 FC 16 29 2163 4C 84 66 0D 02 20 5A 33 98 5D FB D4 BF DD 6D 4A CF 38 04 C3 D4 6E BF 2164 3B 7F A6 26 40 67 4F C0 35 4F A0 56 DB AE A6 2166 A.1.1. Example C509 Certificate Encoding 2168 The CBOR encoding (~C509Certificate) of the same X.509 certificate is 2169 shown below in CBOR diagnostic format. 2171 /This defines a CBOR Sequence (RFC 8742):/ 2173 1, 2174 h'01f50d', 2175 "RFC test CA", 2176 1577836800, 2177 1612224000, 2178 h'0123456789AB', 2179 1, 2180 h'02B1216AB96E5B3B3340F5BDF02E693F16213A04525ED44450 2181 B1019C2DFD3838AB', 2182 1, 2183 0, 2184 h'445D798C90E7F500DC747A654CEC6CFA6F037276E14E52ED07 2185 FC16294C84660D5A33985DFBD4BFDD6D4ACF3804C3D46EBF3B 2186 7FA62640674FC0354FA056DBAEA6' 2188 The size of the CBOR encoding (CBOR sequence) is 138 bytes. 2190 01 2191 43 01 F5 0D 2192 6B 52 46 43 20 74 65 73 74 20 43 41 2193 1A 5E 0B E1 00 2194 1A 60 18 96 00 2195 46 01 23 45 67 89 AB 2196 01 2197 58 21 02 B1 21 6A B9 6E 5B 3B 33 40 F5 BD F0 2E 69 3F 16 21 3A 04 52 2198 5E D4 44 50 B1 01 9C 2D FD 38 38 AB 2199 01 2200 00 2201 58 40 44 5D 79 8C 90 E7 F5 00 DC 74 7A 65 4C EC 6C FA 6F 03 72 76 E1 2202 4E 52 ED 07 FC 16 29 4C 84 66 0D 5A 33 98 5D FB D4 BF DD 6D 4A CF 38 2203 04 C3 D4 6E BF 3B 7F A6 26 40 67 4F C0 35 4F A0 56 DB AE A6 2205 A.1.2. Example: Natively Signed C509 Certificate 2207 The corresponding natively signed C509 certificate in CBOR diagnostic 2208 format is identical, except for c509CertificateType and 2209 signatureValue. 2211 /This defines a CBOR Sequence (RFC 8742):/ 2213 0, 2214 h'01f50d', 2215 "RFC test CA", 2216 1577836800, 2217 1612224000, 2218 h'0123456789AB', 2219 1, 2220 h'02B1216AB96E5B3B3340F5BDF02E693F16213A04525ED44450 2221 B1019C2DFD3838AB', 2222 1, 2223 0, 2224 h'B27A0B781455F71B68290F6C2EC9A897F18FDE9B6C59575953 2225 BC67268AB0E4DDE99D273E04E4715383AB2257C6AAA35284E5 2226 ED18BDB91247E9F2C433136480B9' 2228 The size of the CBOR encoding (CBOR sequence) is 138 bytes. 2230 00 2231 43 01 F5 0D 2232 6B 52 46 43 20 74 65 73 74 20 43 41 2233 1A 5E 0B E1 00 2234 1A 60 18 96 00 2235 46 01 23 45 67 89 AB 2236 01 2237 58 21 02 B1 21 6A B9 6E 5B 3B 33 40 F5 BD F0 2E 69 3F 16 21 3A 04 52 2238 5E D4 44 50 B1 01 9C 2D FD 38 38 AB 2239 01 2240 00 2241 58 40 B2 7A 0B 78 14 55 F7 1B 68 29 0F 6C 2E C9 A8 97 F1 8F DE 9B 6C 2242 59 57 59 53 BC 67 26 8A B0 E4 DD E9 9D 27 3E 04 E4 71 53 83 AB 22 57 2243 C6 AA A3 52 84 E5 ED 18 BD B9 12 47 E9 F2 C4 33 13 64 80 B9 2245 A.1.3. Example: Additonal Keys for the Example Certificates 2247 Below are the issuer key pair and the subject private key belonging 2248 to the above example certificates. The private keys are encoded as 2249 in COSE [RFC8152]. These issuer key pair can be used to sign or 2250 verify the example certificates and the subject private key allows 2251 the example certificates to be used in test vectors for other 2252 protocols like EDHOC. 2254 issuerPublicKeyAlgorithm : 2255 1 (EC Public Key (Weierstrass) with secp256r1) 2257 issuerPublicKey : 2258 h'02AE4CDB01F614DEFC7121285FDC7F5C6D1D42C95647F061BA0080DF678867845E' 2260 issuerPrivateKey : 2261 h'DC66B3415456D649429B53223DF7532B942D6B0E0842C30BCA4C0ACF91547BB2' 2263 subjectPrivateKey : 2264 h'D718111F3F9BD91B92FF6877F386BDBFCEA7154268FD7F2FB56EE17D99EA16D4' 2266 A.2. Example IEEE 802.1AR profiled X.509 Certificate 2268 EDITOR'S NOTE: To do 2270 A.3. Example CAB Baseline ECDSA HTTPS X.509 Certificate 2272 The www.ietf.org HTTPS server replies with a certificate message with 2273 2 certificates. The DER encoding of the first certificate is 1209 2274 bytes. 2276 30 82 04 b5 30 82 04 5a a0 03 02 01 02 02 10 04 7f a1 e3 19 28 ee 40 2277 3b a0 b8 3a 39 56 73 fc 30 0a 06 08 2a 86 48 ce 3d 04 03 02 30 4a 31 2278 0b 30 09 06 03 55 04 06 13 02 55 53 31 19 30 17 06 03 55 04 0a 13 10 2279 43 6c 6f 75 64 66 6c 61 72 65 2c 20 49 6e 63 2e 31 20 30 1e 06 03 55 2280 04 03 13 17 43 6c 6f 75 64 66 6c 61 72 65 20 49 6e 63 20 45 43 43 20 2281 43 41 2d 33 30 1e 17 0d 32 30 30 37 32 39 30 30 30 30 30 30 5a 17 0d 2282 32 31 30 37 32 39 31 32 30 30 30 30 5a 30 6d 31 0b 30 09 06 03 55 04 2283 06 13 02 55 53 31 0b 30 09 06 03 55 04 08 13 02 43 41 31 16 30 14 06 2284 03 55 04 07 13 0d 53 61 6e 20 46 72 61 6e 63 69 73 63 6f 31 19 30 17 2285 06 03 55 04 0a 13 10 43 6c 6f 75 64 66 6c 61 72 65 2c 20 49 6e 63 2e 2286 31 1e 30 1c 06 03 55 04 03 13 15 73 6e 69 2e 63 6c 6f 75 64 66 6c 61 2287 72 65 73 73 6c 2e 63 6f 6d 30 59 30 13 06 07 2a 86 48 ce 3d 02 01 06 2288 08 2a 86 48 ce 3d 03 01 07 03 42 00 04 96 3e cd d8 4d cd 1b 93 a1 cf 2289 43 2d 1a 72 17 d6 c6 3b de 33 55 a0 2f 8c fb 5a d8 99 4c d4 4e 20 5f 2290 15 f6 e3 d2 3b 38 2b a6 49 9b b1 7f 34 1f a5 92 fa 21 86 1f 16 d3 12 2291 06 63 24 05 fd 70 42 bd a3 82 02 fd 30 82 02 f9 30 1f 06 03 55 1d 23 2292 04 18 30 16 80 14 a5 ce 37 ea eb b0 75 0e 94 67 88 b4 45 fa d9 24 10 2293 87 96 1f 30 1d 06 03 55 1d 0e 04 16 04 14 cc 0b 50 e7 d8 37 db f2 43 2294 f3 85 3d 48 60 f5 3b 39 be 9b 2a 30 2e 06 03 55 1d 11 04 27 30 25 82 2295 15 73 6e 69 2e 63 6c 6f 75 64 66 6c 61 72 65 73 73 6c 2e 63 6f 6d 82 2296 0c 77 77 77 2e 69 65 74 66 2e 6f 72 67 30 0e 06 03 55 1d 0f 01 01 ff 2297 04 04 03 02 07 80 30 1d 06 03 55 1d 25 04 16 30 14 06 08 2b 06 01 05 2298 05 07 03 01 06 08 2b 06 01 05 05 07 03 02 30 7b 06 03 55 1d 1f 04 74 2299 30 72 30 37 a0 35 a0 33 86 31 68 74 74 70 3a 2f 2f 63 72 6c 33 2e 64 2300 69 67 69 63 65 72 74 2e 63 6f 6d 2f 43 6c 6f 75 64 66 6c 61 72 65 49 2301 6e 63 45 43 43 43 41 2d 33 2e 63 72 6c 30 37 a0 35 a0 33 86 31 68 74 2302 74 70 3a 2f 2f 63 72 6c 34 2e 64 69 67 69 63 65 72 74 2e 63 6f 6d 2f 2303 43 6c 6f 75 64 66 6c 61 72 65 49 6e 63 45 43 43 43 41 2d 33 2e 63 72 2304 6c 30 4c 06 03 55 1d 20 04 45 30 43 30 37 06 09 60 86 48 01 86 fd 6c 2305 01 01 30 2a 30 28 06 08 2b 06 01 05 05 07 02 01 16 1c 68 74 74 70 73 2306 3a 2f 2f 77 77 77 2e 64 69 67 69 63 65 72 74 2e 63 6f 6d 2f 43 50 53 2307 30 08 06 06 67 81 0c 01 02 02 30 76 06 08 2b 06 01 05 05 07 01 01 04 2308 6a 30 68 30 24 06 08 2b 06 01 05 05 07 30 01 86 18 68 74 74 70 3a 2f 2309 2f 6f 63 73 70 2e 64 69 67 69 63 65 72 74 2e 63 6f 6d 30 40 06 08 2b 2310 06 01 05 05 07 30 02 86 34 68 74 74 70 3a 2f 2f 63 61 63 65 72 74 73 2311 2e 64 69 67 69 63 65 72 74 2e 63 6f 6d 2f 43 6c 6f 75 64 66 6c 61 72 2312 65 49 6e 63 45 43 43 43 41 2d 33 2e 63 72 74 30 0c 06 03 55 1d 13 01 2313 01 ff 04 02 30 00 30 82 01 05 06 0a 2b 06 01 04 01 d6 79 02 04 02 04 2314 81 f6 04 81 f3 00 f1 00 76 00 f6 5c 94 2f d1 77 30 22 14 54 18 08 30 2315 94 56 8e e3 4d 13 19 33 bf df 0c 2f 20 0b cc 4e f1 64 e3 00 00 01 73 2316 9c 83 5f 8e 00 00 04 03 00 47 30 45 02 21 00 f8 d1 b4 a9 3d 2f 0d 4c 2317 41 76 df b4 88 bc c7 3b 86 44 3d 7d e0 0e 6a c8 17 4d 89 48 a8 84 36 2318 68 02 20 29 ff 5a 34 06 8a 24 0c 69 50 27 88 e8 ee 25 ab 7e d2 cb cf 2319 68 6e ce 7b 5f 96 b4 31 a9 07 02 fa 00 77 00 5c dc 43 92 fe e6 ab 45 2320 44 b1 5e 9a d4 56 e6 10 37 fb d5 fa 47 dc a1 73 94 b2 5e e6 f6 c7 0e 2321 ca 00 00 01 73 9c 83 5f be 00 00 04 03 00 48 30 46 02 21 00 e8 91 c1 2322 97 bf b0 e3 d3 0c b6 ce e6 0d 94 c3 c7 5f d1 17 53 36 93 11 08 d8 98 2323 12 d4 d2 9d 81 d0 02 21 00 a1 59 d1 6c 46 47 d1 48 37 57 fc d6 ce 4e 2324 75 ec 7b 5e f6 57 ef e0 28 f8 e5 cc 47 92 68 2d ac 43 30 0a 06 08 2a 2325 86 48 ce 3d 04 03 02 03 49 00 30 46 02 21 00 bd 63 cf 4f 7e 5c fe 6c 2326 29 38 5e a7 1c fb fc 1e 3f 7b 1c d0 72 51 a2 21 f7 77 69 c0 f4 71 df 2327 ea 02 21 00 b5 c0 6c c4 58 54 fa 30 b2 82 88 b1 d3 bb 9a 66 61 ed 50 2328 31 72 5b 1a 82 02 e0 da 5b 59 f9 54 02 2330 A.3.1. Example C509 Certificate Encoding 2332 The CBOR encoding (~C509Certificate) of the first X.509 certificate 2333 is shown below in CBOR diagnostic format. 2335 /This defines a CBOR Sequence (RFC 8742):/ 2337 1, 2338 h'047FA1E31928EE403BA0B83A395673FC', 2339 [ 2340 -4, "US", 2341 -8, "Cloudflare, Inc.", 2342 -1, "Cloudflare Inc ECC CA-3" 2343 ], 2344 1595980800, 2345 1627560000, 2346 [ 2347 -4, "US", 2348 -6, "CA", 2349 -5, "San Francisco", 2350 -8, "Cloudflare, Inc.", 2351 -1, "sni.cloudflaressl.com" 2352 ], 2353 1, 2354 h'03963ECDD84DCD1B93A1CF432D1A7217D6C63BDE3355A02F8CFB5AD8994CD44E20', 2355 [ 2356 7, h'A5CE37EAEBB0750E946788B445FAD9241087961F', 2357 1, h'CC0B50E7D837DBF243F3853D4860F53B39BE9B2A', 2358 3, [2, "sni.cloudflaressl.com", 2, "www.ietf.org"], 2359 -2, 1, 2360 8, [1, 2], 2361 5, ["http://crl3.digicert.com/CloudflareIncECCCA-3.crl", 2362 "http://crl4.digicert.com/CloudflareIncECCCA-3.crl"], 2363 6, [h'6086480186FD6C0101', [1, "https://www.digicert.com/CPS"], 2], 2364 9, [1, "http://ocsp.digicert.com", 2365 2, "http://cacerts.digicert.com/CloudflareIncECCCA-3.crt"], 2366 -4, -2, 2367 10, [ 2368 h'F65C942FD1773022145418083094568EE34D131933BFDF0C2F200BCC4EF164E3', 2369 77922190, 2370 0, 2371 h'F8D1B4A93D2F0D4C4176DFB488BCC73B86443D7DE00E6AC8174D8948A8843668 2372 29FF5A34068A240C69502788E8EE25AB7ED2CBCF686ECE7B5F96B431A90702FA', 2373 h'5CDC4392FEE6AB4544B15E9AD456E61037FBD5FA47DCA17394B25EE6F6C70ECA', 2374 77922238, 2375 0, 2376 h'E891C197BFB0E3D30CB6CEE60D94C3C75FD1175336931108D89812D4D29D81D0 2377 A159D16C4647D1483757FCD6CE4E75EC7B5EF657EFE028F8E5CC4792682DAC43' 2378 ] 2379 ], 2380 0, 2381 h'BD63CF4F7E5CFE6C29385EA71CFBFC1E3F7B1CD07251A221F77769C0F471DFEA 2382 B5C06CC45854FA30B28288B1D3BB9A6661ED5031725B1A8202E0DA5B59F95402' 2383 The size of the CBOR encoding (CBOR sequence) is 783 bytes. 2385 A.4. Example CAB Baseline RSA HTTPS X.509 Certificate 2387 The tools.ietf.org HTTPS server replies with a certificate message 2388 with 4 certificates. The DER encoding of the first certificate is 2389 1647 bytes. 2391 30 82 06 6b 30 82 05 53 a0 03 02 01 02 02 09 00 a6 a5 5c 87 0e 39 b4 2392 0e 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0b 05 00 30 81 c6 31 0b 30 09 2393 06 03 55 04 06 13 02 55 53 31 10 30 0e 06 03 55 04 08 13 07 41 72 69 2394 7a 6f 6e 61 31 13 30 11 06 03 55 04 07 13 0a 53 63 6f 74 74 73 64 61 2395 6c 65 31 25 30 23 06 03 55 04 0a 13 1c 53 74 61 72 66 69 65 6c 64 20 2396 54 65 63 68 6e 6f 6c 6f 67 69 65 73 2c 20 49 6e 63 2e 31 33 30 31 06 2397 03 55 04 0b 13 2a 68 74 74 70 3a 2f 2f 63 65 72 74 73 2e 73 74 61 72 2398 66 69 65 6c 64 74 65 63 68 2e 63 6f 6d 2f 72 65 70 6f 73 69 74 6f 72 2399 79 2f 31 34 30 32 06 03 55 04 03 13 2b 53 74 61 72 66 69 65 6c 64 20 2400 53 65 63 75 72 65 20 43 65 72 74 69 66 69 63 61 74 65 20 41 75 74 68 2401 6f 72 69 74 79 20 2d 20 47 32 30 1e 17 0d 32 30 31 30 30 31 31 39 33 2402 38 33 36 5a 17 0d 32 31 31 31 30 32 31 39 33 38 33 36 5a 30 3e 31 21 2403 30 1f 06 03 55 04 0b 13 18 44 6f 6d 61 69 6e 20 43 6f 6e 74 72 6f 6c 2404 20 56 61 6c 69 64 61 74 65 64 31 19 30 17 06 03 55 04 03 0c 10 2a 2e 2405 74 6f 6f 6c 73 2e 69 65 74 66 2e 6f 72 67 30 82 01 22 30 0d 06 09 2a 2406 86 48 86 f7 0d 01 01 01 05 00 03 82 01 0f 00 30 82 01 0a 02 82 01 01 2407 00 b1 e1 37 e8 eb 82 d6 89 fa db f5 c2 4b 77 f0 2c 4a de 72 6e 3e 13 2408 60 d1 a8 66 1e c4 ad 3d 32 60 e5 f0 99 b5 f4 7a 7a 48 55 21 ee 0e 39 2409 12 f9 ce 0d ca f5 69 61 c7 04 ed 6e 0f 1d 3b 1e 50 88 79 3a 0e 31 41 2410 16 f1 b1 02 64 68 a5 cd f5 4a 0a ca 99 96 35 08 c3 7e 27 5d d0 a9 cf 2411 f3 e7 28 af 37 d8 b6 7b dd f3 7e ae 6e 97 7f f7 ca 69 4e cc d0 06 df 2412 5d 27 9b 3b 12 e7 e6 fe 08 6b 52 7b 82 11 7c 72 b3 46 eb c1 e8 78 b8 2413 0f cb e1 eb bd 06 44 58 dc 83 50 b2 a0 62 5b dc 81 b8 36 e3 9e 7c 79 2414 b2 a9 53 8a e0 0b c9 4a 2a 13 39 31 13 bd 2c cf a8 70 cf 8c 8d 3d 01 2415 a3 88 ae 12 00 36 1d 1e 24 2b dd 79 d8 53 01 26 ed 28 4f c9 86 94 83 2416 4e c8 e1 14 2e 85 b3 af d4 6e dd 69 46 af 41 25 0e 7a ad 8b f2 92 ca 2417 79 d9 7b 32 4f f7 77 e8 f9 b4 4f 23 5c d4 5c 03 ae d8 ab 3a ca 13 5f 2418 5d 5d 5d a1 02 03 01 00 01 a3 82 02 e1 30 82 02 dd 30 0c 06 03 55 1d 2419 13 01 01 ff 04 02 30 00 30 1d 06 03 55 1d 25 04 16 30 14 06 08 2b 06 2420 01 05 05 07 03 01 06 08 2b 06 01 05 05 07 03 02 30 0e 06 03 55 1d 0f 2421 01 01 ff 04 04 03 02 05 a0 30 3d 06 03 55 1d 1f 04 36 30 34 30 32 a0 2422 30 a0 2e 86 2c 68 74 74 70 3a 2f 2f 63 72 6c 2e 73 74 61 72 66 69 65 2423 6c 64 74 65 63 68 2e 63 6f 6d 2f 73 66 69 67 32 73 31 2d 32 34 32 2e 2424 63 72 6c 30 63 06 03 55 1d 20 04 5c 30 5a 30 4e 06 0b 60 86 48 01 86 2425 fd 6e 01 07 17 01 30 3f 30 3d 06 08 2b 06 01 05 05 07 02 01 16 31 68 2426 74 74 70 3a 2f 2f 63 65 72 74 69 66 69 63 61 74 65 73 2e 73 74 61 72 2427 66 69 65 6c 64 74 65 63 68 2e 63 6f 6d 2f 72 65 70 6f 73 69 74 6f 72 2428 79 2f 30 08 06 06 67 81 0c 01 02 01 30 81 82 06 08 2b 06 01 05 05 07 2429 01 01 04 76 30 74 30 2a 06 08 2b 06 01 05 05 07 30 01 86 1e 68 74 74 2430 70 3a 2f 2f 6f 63 73 70 2e 73 74 61 72 66 69 65 6c 64 74 65 63 68 2e 2431 63 6f 6d 2f 30 46 06 08 2b 06 01 05 05 07 30 02 86 3a 68 74 74 70 3a 2432 2f 2f 63 65 72 74 69 66 69 63 61 74 65 73 2e 73 74 61 72 66 69 65 6c 2433 64 74 65 63 68 2e 63 6f 6d 2f 72 65 70 6f 73 69 74 6f 72 79 2f 73 66 2434 69 67 32 2e 63 72 74 30 1f 06 03 55 1d 23 04 18 30 16 80 14 25 45 81 2435 68 50 26 38 3d 3b 2d 2c be cd 6a d9 b6 3d b3 66 63 30 2b 06 03 55 1d 2436 11 04 24 30 22 82 10 2a 2e 74 6f 6f 6c 73 2e 69 65 74 66 2e 6f 72 67 2437 82 0e 74 6f 6f 6c 73 2e 69 65 74 66 2e 6f 72 67 30 1d 06 03 55 1d 0e 2438 04 16 04 14 ad 8a b4 1c 07 51 d7 92 89 07 b0 b7 84 62 2f 36 55 7a 5f 2439 4d 30 82 01 06 06 0a 2b 06 01 04 01 d6 79 02 04 02 04 81 f7 04 81 f4 2440 00 f2 00 77 00 f6 5c 94 2f d1 77 30 22 14 54 18 08 30 94 56 8e e3 4d 2441 13 19 33 bf df 0c 2f 20 0b cc 4e f1 64 e3 00 00 01 74 e5 ac 71 13 00 2442 00 04 03 00 48 30 46 02 21 00 8c f5 48 52 ce 56 35 43 39 11 cf 10 cd 2443 b9 1f 52 b3 36 39 22 3a d1 38 a4 1d ec a6 fe de 1f e9 0f 02 21 00 bc 2444 a2 25 43 66 c1 9a 26 91 c4 7a 00 b5 b6 53 ab bd 44 c2 f8 ba ae f4 d2 2445 da f2 52 7c e6 45 49 95 00 77 00 5c dc 43 92 fe e6 ab 45 44 b1 5e 9a 2446 d4 56 e6 10 37 fb d5 fa 47 dc a1 73 94 b2 5e e6 f6 c7 0e ca 00 00 01 2447 74 e5 ac 72 3c 00 00 04 03 00 48 30 46 02 21 00 a5 e0 90 6e 63 e9 1d 2448 4f dd ef ff 03 52 b9 1e 50 89 60 07 56 4b 44 8a 38 28 f5 96 dc 6b 28 2449 72 6d 02 21 00 fc 91 ea ed 02 16 88 66 05 4e e1 8a 2e 53 46 c4 cc 51 2450 fe b3 fa 10 a9 1d 2e db f9 91 25 f8 6c e6 30 0d 06 09 2a 86 48 86 f7 2451 0d 01 01 0b 05 00 03 82 01 01 00 14 04 3f a0 be d2 ee 3f a8 6e 3a 1f 2452 78 8e a0 4c 35 53 0f 11 06 1f ff 60 a1 6d 0b 83 e9 d9 2a db b3 3f 9d 2453 b3 d7 e0 59 4c 19 a8 e4 19 a5 0c a7 70 72 77 63 d5 fe 64 51 0a d2 7a 2454 d6 50 a5 8a 92 38 ec cb 2f 0f 5a c0 64 58 4d 5c 06 b9 73 63 68 27 8b 2455 89 34 dc 79 c7 1d 3a fd 34 5f 83 14 41 58 49 80 68 29 80 39 8a 86 72 2456 69 cc 79 37 ce e3 97 f7 dc f3 95 88 ed 81 03 29 00 d2 a2 c7 ba ab d6 2457 3a 8e ca 09 0b d9 fb 39 26 4b ff 03 d8 8e 2d 3f 6b 21 ca 8a 7d d8 5f 2458 fb 94 ba 83 de 9c fc 15 8d 61 fa 67 2d b0 c7 db 3d 25 0a 41 4a 85 d3 2459 7f 49 46 37 3c f4 b1 75 d0 52 f3 dd c7 66 f1 4b fd aa 00 ed bf e4 7e 2460 ed 01 ec 7b e4 f6 46 fc 31 fd 72 fe 03 d2 f2 65 af 4d 7e e2 81 9b 7a 2461 fd 30 3c f5 52 f4 05 34 a0 8a 3e 19 41 58 c8 a8 e0 51 71 84 09 15 ae 2462 ec a5 77 75 fa 18 f7 d5 77 d5 31 cc c7 2d 2464 A.4.1. Example C509 Certificate Encoding 2466 The CBOR encoding (~C509Certificate) of the first X.509 certificate 2467 is shown below in CBOR diagnostic format. 2469 /This defines a CBOR Sequence (RFC 8742):/ 2471 1, 2472 h'A6A55C870E39B40E', 2473 [ 2474 -4, "US", 2475 -6, "Arizona", 2476 -5, "Scottsdale", 2477 -8, "Starfield Technologies, Inc.", 2478 -9, "http://certs.starfieldtech.com/repository/", 2479 -1, "Starfield Secure Certificate Authority - G2" 2480 ], 2481 1601581116, 2482 1635881916, 2483 [ 2484 -9, "Domain Control Validated", 2485 1, "*.tools.ietf.org" 2486 ], 2487 0, 2488 h'B1E137E8EB82D689FADBF5C24B77F02C4ADE726E3E1360D1A8661EC4AD3D3260 2489 E5F099B5F47A7A485521EE0E3912F9CE0DCAF56961C704ED6E0F1D3B1E508879 2490 3A0E314116F1B1026468A5CDF54A0ACA99963508C37E275DD0A9CFF3E728AF37 2491 D8B67BDDF37EAE6E977FF7CA694ECCD006DF5D279B3B12E7E6FE086B527B8211 2492 7C72B346EBC1E878B80FCBE1EBBD064458DC8350B2A0625BDC81B836E39E7C79 2493 B2A9538AE00BC94A2A13393113BD2CCFA870CF8C8D3D01A388AE1200361D1E24 2494 2BDD79D8530126ED284FC98694834EC8E1142E85B3AFD46EDD6946AF41250E7A 2495 AD8BF292CA79D97B324FF777E8F9B44F235CD45C03AED8AB3ACA135F5D5D5DA1', 2496 [ 2497 -4, -2, 2498 8, [ 1, 2 ], 2499 -2, 5, 2500 5, ["http://crl.starfieldtech.com/sfig2s1-242.crl"], 2501 6, [ h'6086480186fd6e01071701', 2502 [1, "http://certificates.starfieldtech.com/repository/"], 1 ], 2503 9, [ 1, "http://ocsp.starfieldtech.com/", 2504 2, "http://certificates.starfieldtech.com/repository/sfig2.crt" ], 2505 7, h'254581685026383D3B2D2CBECD6AD9B63DB36663', 2506 3, [ 2, "*.tools.ietf.org", 2, "tools.ietf.org" ], 2507 1, h'AD8AB41C0751D7928907B0B784622F36557A5F4D', 2508 10, [ 2509 h'F65C942FD1773022145418083094568EE34D131933BFDF0C2F200BCC4EF164E3', 2510 1715, 2511 0, 2512 h'8CF54852CE5635433911CF10CDB91F52B33639223AD138A41DECA6FEDE1FE90F 2513 BCA2254366C19A2691C47A00B5B653ABBD44C2F8BAAEF4D2DAF2527CE6454995', 2514 h'5CDC4392FEE6AB4544B15E9AD456E61037FBD5FA47DCA17394B25EE6F6C70ECA', 2515 2012, 2516 0, 2517 h'A5E0906E63E91D4FDDEFFF0352B91E50896007564B448A3828F596DC6B28726D 2518 FC91EAED02168866054EE18A2E5346C4CC51FEB3FA10A91D2EDBF99125F86CE6' 2519 ] 2520 ], 2521 23, 2522 h'14043FA0BED2EE3FA86E3A1F788EA04C35530F11061FFF60A16D0B83E9D92ADB 2523 B33F9DB3D7E0594C19A8E419A50CA770727763D5FE64510AD27AD650A58A9238 2524 ECCB2F0F5AC064584D5C06B9736368278B8934DC79C71D3AFD345F8314415849 2525 80682980398A867269CC7937CEE397F7DCF39588ED81032900D2A2C7BAABD63A 2526 8ECA090BD9FB39264BFF03D88E2D3F6B21CA8A7DD85FFB94BA83DE9CFC158D61 2527 FA672DB0C7DB3D250A414A85D37F4946373CF4B175D052F3DDC766F14BFDAA00 2528 EDBFE47EED01EC7BE4F646FC31FD72FE03D2F265AF4D7EE2819B7AFD303CF552 2529 F40534A08A3E194158C8A8E05171840915AEECA57775FA18F7D577D531CCC72D' 2531 The size of the CBOR encoding (CBOR sequence) is 1245 bytes. 2533 Acknowledgments 2535 The authors want to thank Henk Birkholz, Carsten Bormann, Russ 2536 Housley, Olle Johansson, Benjamin Kaduk, Ilari Liusvaara, Laurence 2537 Lundblade, Francesca Palombinini, Thomas Peterson, Michael 2538 Richardson, Maik Reichert, Stefan Santesson, Jim Schaad, Fraser 2539 Tweedale, and Rene Struik for reviewing and commenting on 2540 intermediate versions of the draft and helping with GitHub. 2542 Authors' Addresses 2544 John Preuss Mattsson 2545 Ericsson AB 2547 Email: john.mattsson@ericsson.com 2549 Goeran Selander 2550 Ericsson AB 2552 Email: goran.selander@ericsson.com 2554 Shahid Raza 2555 RISE AB 2557 Email: shahid.raza@ri.se 2559 Joel Hoeglund 2560 RISE AB 2562 Email: joel.hoglund@ri.se 2564 Martin Furuhed 2565 Nexus Group 2567 Email: martin.furuhed@nexusgroup.com