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