| 1 |
<pre>Network Working Group S. Santesson |
| 2 |
Request for Comments: 3739 Microsoft |
| 3 |
Obsoletes: <a href="./rfc3039">3039</a> M. Nystrom |
| 4 |
Category: Standards Track RSA Security |
| 5 |
T. Polk |
| 6 |
NIST |
| 7 |
March 2004 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Internet X.509 Public Key Infrastructure:</span> |
| 11 |
<span class="h1">Qualified Certificates Profile</span> |
| 12 |
|
| 13 |
Status of this Memo |
| 14 |
|
| 15 |
This document specifies an Internet standards track protocol for the |
| 16 |
Internet community, and requests discussion and suggestions for |
| 17 |
improvements. Please refer to the current edition of the "Internet |
| 18 |
Official Protocol Standards" (STD 1) for the standardization state |
| 19 |
and status of this protocol. Distribution of this memo is unlimited. |
| 20 |
|
| 21 |
Copyright Notice |
| 22 |
|
| 23 |
Copyright (C) The Internet Society (2004). All Rights Reserved. |
| 24 |
|
| 25 |
Abstract |
| 26 |
|
| 27 |
This document forms a certificate profile, based on <a href="./rfc3280">RFC 3280</a>, for |
| 28 |
identity certificates issued to natural persons. |
| 29 |
|
| 30 |
The profile defines specific conventions for certificates that are |
| 31 |
qualified within a defined legal framework, named Qualified |
| 32 |
Certificates. However, the profile does not define any legal |
| 33 |
requirements for such Qualified Certificates. |
| 34 |
|
| 35 |
The goal of this document is to define a certificate profile that |
| 36 |
supports the issuance of Qualified Certificates independent of local |
| 37 |
legal requirements. The profile is however not limited to Qualified |
| 38 |
Certificates and further profiling may facilitate specific local |
| 39 |
needs. |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Santesson, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 60 |
<a href="#section-1.1">1.1</a>. Changes since <a href="./rfc3039">RFC 3039</a> . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 61 |
<a href="#section-1.2">1.2</a>. Definitions. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 62 |
<a href="#section-2">2</a>. Requirements and Assumptions . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 63 |
<a href="#section-2.1">2.1</a>. Properties . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 64 |
<a href="#section-2.2">2.2</a>. Statement of Purpose . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 65 |
<a href="#section-2.3">2.3</a>. Policy Issues. . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 66 |
<a href="#section-2.4">2.4</a>. Uniqueness of Names. . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 67 |
<a href="#section-3">3</a>. Certificate and Certificate Extensions Profile . . . . . . . . <a href="#page-6">6</a> |
| 68 |
<a href="#section-3.1">3.1</a>. Basic Certificate Fields . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 69 |
<a href="#section-3.1.1">3.1.1</a>. Issuer . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 70 |
<a href="#section-3.1.2">3.1.2</a>. Subject. . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 71 |
<a href="#section-3.2">3.2</a>. Certificate Extensions . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 72 |
<a href="#section-3.2.1">3.2.1</a>. Subject Alternative Name . . . . . . . . . . . . <a href="#page-9">9</a> |
| 73 |
<a href="#section-3.2.2">3.2.2</a>. Subject Directory Attributes . . . . . . . . . . <a href="#page-9">9</a> |
| 74 |
<a href="#section-3.2.3">3.2.3</a>. Certificate Policies . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 75 |
<a href="#section-3.2.4">3.2.4</a>. Key Usage. . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 76 |
<a href="#section-3.2.5">3.2.5</a>. Biometric Information. . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 77 |
<a href="#section-3.2.6">3.2.6</a>. Qualified Certificate Statements . . . . . . . . <a href="#page-13">13</a> |
| 78 |
<a href="#section-4">4</a>. Security Considerations. . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 79 |
<a href="#appendix-A">A</a>. ASN.1 Definitions. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 80 |
<a href="#appendix-A.1">A.1</a>. 1988 ASN.1 Module (Normative). . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 81 |
<a href="#appendix-A.2">A.2</a>. 1997 ASN.1 Module (Informative). . . . . . . . . . . . . <a href="#page-19">19</a> |
| 82 |
<a href="#appendix-B">B</a>. A Note on Attributes . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 83 |
<a href="#appendix-C">C</a>. Example Certificate. . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 84 |
<a href="#appendix-C.1">C.1</a>. ASN.1 Structure. . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 85 |
<a href="#appendix-C.1.1">C.1.1</a>. Extensions . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 86 |
<a href="#appendix-C.1.2">C.1.2</a>. The Certificate. . . . . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 87 |
<a href="#appendix-C.2">C.2</a>. ASN.1 Dump . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a> |
| 88 |
<a href="#appendix-C.3">C.3</a>. DER-encoding . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a> |
| 89 |
<a href="#appendix-C.4">C.4</a>. CA's Public Key. . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 90 |
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 91 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a> |
| 92 |
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 93 |
|
| 94 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 95 |
|
| 96 |
This specification is one part of a family of standards for the X.509 |
| 97 |
Public Key Infrastructure (PKI) for the Internet. It is based on |
| 98 |
[<a href="#ref-X.509">X.509</a>] and [<a href="./rfc3280">RFC 3280</a>], which defines underlying certificate formats |
| 99 |
and semantics needed for a full implementation of this standard. |
| 100 |
|
| 101 |
This profile includes specific mechanisms intended for use with |
| 102 |
Qualified Certificates. The term Qualified Certificates and the |
| 103 |
assumptions that affect the scope of this document are discussed in |
| 104 |
<a href="#section-2">Section 2</a>. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Santesson, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 111 |
|
| 112 |
|
| 113 |
<a href="#section-3">Section 3</a> defines requirements on certificate information content. |
| 114 |
This specification provides profiles for two certificate fields: |
| 115 |
issuer and subject. It also provides profiles for four certificate |
| 116 |
extensions defined in <a href="./rfc3280">RFC 3280</a>: subject alternate name, subject |
| 117 |
directory attributes, certificate policies, and key usage, and it |
| 118 |
defines two additional extensions: biometric information and |
| 119 |
qualified certificate statements. The certificate extensions are |
| 120 |
presented in the 1997 Abstract Syntax Notation One (ASN.1) [<a href="#ref-X.680" title=" Information Technology - Abstract Syntax Notation One">X.680</a>], |
| 121 |
but in conformance with <a href="./rfc3280">RFC 3280</a> the 1988 ASN.1 module in <a href="#appendix-A">Appendix A</a> |
| 122 |
contains all normative definitions (the 1997 module in <a href="#appendix-A">Appendix A</a> is |
| 123 |
informative). |
| 124 |
|
| 125 |
In <a href="#section-4">Section 4</a>, some security considerations are discussed in order to |
| 126 |
clarify the security context in which the standard may be utilized. |
| 127 |
|
| 128 |
<a href="#appendix-A">Appendix A</a> contains all relevant ASN.1 structures that are not |
| 129 |
already defined in <a href="./rfc3280">RFC 3280</a>. <a href="#appendix-B">Appendix B</a> contains a note on |
| 130 |
attributes. <a href="#appendix-C">Appendix C</a> contains an example certificate. |
| 131 |
|
| 132 |
The appendices sections are followed by the References, Authors |
| 133 |
Addresses, and the Full Copyright Statement. |
| 134 |
|
| 135 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Changes since <a href="./rfc3039">RFC 3039</a></span> |
| 136 |
|
| 137 |
This specification obsoletes <a href="./rfc3039">RFC 3039</a>. This specification differs |
| 138 |
from <a href="./rfc3039">RFC 3039</a> in the following basic areas: |
| 139 |
|
| 140 |
* Some editorial clarifications have been made to introductory |
| 141 |
sections to clarify that this profile is generally applicable |
| 142 |
to a broad type of certificates, even if its prime purpose is |
| 143 |
to facilitate issuance of Qualified Certificates. |
| 144 |
|
| 145 |
* To align with <a href="./rfc3280">RFC 3280</a>, support for domainComponent and title |
| 146 |
attributes in subject names are included, and postalAddress is |
| 147 |
no longer supported. |
| 148 |
|
| 149 |
* To align with actual usage, support for the title attribute in |
| 150 |
the subject directory attributes extension is no longer |
| 151 |
supported. |
| 152 |
|
| 153 |
* To better facilitate broad applicability of this profile, some |
| 154 |
constraints on key usage settings in the key usage extension |
| 155 |
have been removed. |
| 156 |
|
| 157 |
* A new qc-Statement reflecting this second version of the |
| 158 |
profile has been defined in <a href="#section-3.2.6.1">Section 3.2.6.1</a>. This profile |
| 159 |
obsoletes <a href="./rfc3039">RFC 3039</a>, but the qc-statement reflecting compliance |
| 160 |
with <a href="./rfc3039">RFC 3039</a> is also defined for backwards compatibility. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Santesson, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Definitions</span> |
| 170 |
|
| 171 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 172 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 173 |
document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, [<a href="./rfc2119">RFC 2119</a>]. |
| 174 |
|
| 175 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements and Assumptions</span> |
| 176 |
|
| 177 |
The term "Qualified Certificate" is used by the European Directive on |
| 178 |
Electronic Signature [<a href="#ref-EU-ESDIR">EU-ESDIR</a>] to refer to a specific type of |
| 179 |
certificates, with appliance in European electronic signature |
| 180 |
legislation. This specification is intended to support this class of |
| 181 |
certificates, but its scope is not limited to this application. |
| 182 |
|
| 183 |
Within this standard, the term "Qualified Certificate" is used |
| 184 |
generally, describing a certificate whose primary purpose is to |
| 185 |
identify a person with a high level of assurance, where the |
| 186 |
certificate meets some qualification requirements defined by an |
| 187 |
applicable legal framework, such as the European Directive on |
| 188 |
Electronic Signature [<a href="#ref-EU-ESDIR">EU-ESDIR</a>]. The actual mechanisms that decide |
| 189 |
whether a certificate should or should not be considered a "Qualified |
| 190 |
Certificate" in regard to any legislation are outside the scope of |
| 191 |
this standard. |
| 192 |
|
| 193 |
Harmonization in the field of identity certificates issued to natural |
| 194 |
persons, in particular Qualified Certificates, is essential within |
| 195 |
several aspects that fall outside the scope of <a href="./rfc3280">RFC 3280</a>. The most |
| 196 |
important aspects that affect the scope of this specification are: |
| 197 |
|
| 198 |
- Definition of names and identity information in order to identify |
| 199 |
the associated subject in a uniform way. |
| 200 |
|
| 201 |
- Definition of information which identifies the CA and the |
| 202 |
jurisdiction under which the CA operates when issuing a particular |
| 203 |
certificate. |
| 204 |
|
| 205 |
- Definition of key usage extension usage for Qualified |
| 206 |
Certificates. |
| 207 |
|
| 208 |
- Definition of information structure for storage of biometric |
| 209 |
information. |
| 210 |
|
| 211 |
- Definition of a standardized way to store predefined statements |
| 212 |
with relevance for Qualified Certificates. |
| 213 |
|
| 214 |
- Requirements for critical extensions. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Santesson, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Properties</span> |
| 226 |
|
| 227 |
This profile accommodates profiling needs for Qualified Certificates |
| 228 |
based on the assumptions that: |
| 229 |
|
| 230 |
- Qualified Certificates are issued by a CA that makes a statement |
| 231 |
that the certificate serves the purpose of a Qualified |
| 232 |
Certificate, as discussed in <a href="#section-2.2">Section 2.2</a>. |
| 233 |
|
| 234 |
- The Qualified Certificate indicates a certificate policy |
| 235 |
consistent with liabilities, practices, and procedures undertaken |
| 236 |
by the CA, as discussed in <a href="#section-2.3">Section 2.3</a>. |
| 237 |
|
| 238 |
- The Qualified Certificate is issued to a natural person (living |
| 239 |
human being). |
| 240 |
|
| 241 |
- The Qualified Certificate contains a name which may be either |
| 242 |
based on the real name of the subject or a pseudonym. |
| 243 |
|
| 244 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Statement of Purpose</span> |
| 245 |
|
| 246 |
This profile defines conventions to declare within a certificate that |
| 247 |
it serves the purpose of being a Qualified Certificate. This enables |
| 248 |
the CA to explicitly define this intent. |
| 249 |
|
| 250 |
The function of this declaration is thus to assist any concerned |
| 251 |
entity in evaluating the risk associated with creating or accepting |
| 252 |
signatures that are based on a Qualified Certificate. |
| 253 |
|
| 254 |
This profile defines two ways to include this information: |
| 255 |
|
| 256 |
- As information defined by a certificate policy included in the |
| 257 |
certificate policies extension, and |
| 258 |
|
| 259 |
- As a statement included in the Qualified Certificates Statements |
| 260 |
extension. |
| 261 |
|
| 262 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Policy Issues</span> |
| 263 |
|
| 264 |
Certain policy aspects define the context in which this profile is to |
| 265 |
be understood and used. It is however outside the scope of this |
| 266 |
profile to specify any policies or legal aspects that will govern |
| 267 |
services that issue or utilize certificates according to this |
| 268 |
profile. |
| 269 |
|
| 270 |
It is however an underlying assumption in this profile that a |
| 271 |
responsible issuing CA will undertake to follow a certificate policy |
| 272 |
that is consistent with its liabilities, practices, and procedures. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Santesson, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Uniqueness of names</span> |
| 282 |
|
| 283 |
Distinguished name is originally defined in X.501 [<a href="#ref-X.501" title=" Information Technology - Open Systems Interconnection - The Directory: Models">X.501</a>] as a |
| 284 |
representation of a directory name, defined as a construct that |
| 285 |
identifies a particular object from among a set of all objects. The |
| 286 |
distinguished name MUST be unique for each subject entity certified |
| 287 |
by the one CA as defined by the issuer name field, for the whole life |
| 288 |
time of the CA. |
| 289 |
|
| 290 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Certificate and Certificate Extensions Profile</span> |
| 291 |
|
| 292 |
This section defines certificate profiling conventions. The profile |
| 293 |
is based on the Internet certificate profile <a href="./rfc3280">RFC 3280</a>, which in turn |
| 294 |
is based on the X.509 version 3 format. For full implementation of |
| 295 |
this section, implementers are REQUIRED to consult the underlying |
| 296 |
formats and semantics defined in <a href="./rfc3280">RFC 3280</a>. |
| 297 |
|
| 298 |
ASN.1 definitions, relevant for this section that are not supplied by |
| 299 |
<a href="./rfc3280">RFC 3280</a>, are supplied in <a href="#appendix-A">Appendix A</a>. |
| 300 |
|
| 301 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Basic Certificate Fields</span> |
| 302 |
|
| 303 |
This section provides additional details regarding the contents of |
| 304 |
two fields in the basic certificate. These fields are the issuer and |
| 305 |
subject fields. |
| 306 |
|
| 307 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Issuer</span> |
| 308 |
|
| 309 |
The issuer field SHALL identify the organization responsible for |
| 310 |
issuing the certificate. The name SHOULD be an officially registered |
| 311 |
name of the organization. |
| 312 |
|
| 313 |
The distinguished name of the issuer SHALL be specified using an |
| 314 |
appropriate subset of the following attributes: |
| 315 |
|
| 316 |
domainComponent; |
| 317 |
countryName; |
| 318 |
stateOrProvinceName; |
| 319 |
organizationName; |
| 320 |
localityName; and |
| 321 |
serialNumber. |
| 322 |
|
| 323 |
The domainComponent attribute is defined in [<a href="./rfc2247">RFC 2247</a>], all other |
| 324 |
attributes are defined in [<a href="./rfc3280">RFC 3280</a>] and [<a href="#ref-X.520" title=" Information Technology - Open Systems Interconnection - The Directory: Selected Attribute Types">X.520</a>]. |
| 325 |
|
| 326 |
Additional attributes MAY be present, but they SHOULD NOT be |
| 327 |
necessary to identify the issuing organization. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Santesson, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 335 |
|
| 336 |
|
| 337 |
A relying party MAY have to consult associated certificate policies |
| 338 |
and/or the issuer's CPS, in order to determine the semantics of name |
| 339 |
fields. |
| 340 |
|
| 341 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Subject</span> |
| 342 |
|
| 343 |
The subject field of a certificate compliant with this profile SHALL |
| 344 |
contain a distinguished name of the subject (see 2.4 for definition |
| 345 |
of distinguished name). |
| 346 |
|
| 347 |
The subject field SHALL contain an appropriate subset of the |
| 348 |
following attributes: |
| 349 |
|
| 350 |
domainComponent; |
| 351 |
countryName; |
| 352 |
commonName; |
| 353 |
surname; |
| 354 |
givenName; |
| 355 |
pseudonym; |
| 356 |
serialNumber; |
| 357 |
title; |
| 358 |
organizationName; |
| 359 |
organizationalUnitName; |
| 360 |
stateOrProvinceName; and |
| 361 |
localityName. |
| 362 |
|
| 363 |
The domainComponent attribute is defined in [<a href="./rfc2247">RFC 2247</a>], all other |
| 364 |
attributes are defined in [<a href="./rfc3280">RFC 3280</a>] and [<a href="#ref-X.520" title=" Information Technology - Open Systems Interconnection - The Directory: Selected Attribute Types">X.520</a>]. |
| 365 |
|
| 366 |
Other attributes MAY also be present; however, the use of other |
| 367 |
attributes MUST NOT be necessary to distinguish one subject name from |
| 368 |
another subject name. That is, the attributes listed above are |
| 369 |
sufficient to ensure unique subject names. |
| 370 |
|
| 371 |
Of these attributes, the subject field SHALL include at least one of |
| 372 |
the following: |
| 373 |
|
| 374 |
Choice I: commonName |
| 375 |
Choice II: givenName |
| 376 |
Choice III: pseudonym |
| 377 |
|
| 378 |
The countryName attribute value specifies a general context in |
| 379 |
which other attributes are to be understood. The country |
| 380 |
attribute does not necessarily indicate the subject's country of |
| 381 |
citizenship or country of residence, nor does it have to indicate |
| 382 |
the country of issuance. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Santesson, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 391 |
|
| 392 |
|
| 393 |
Note: Many X.500 implementations require the presence of countryName |
| 394 |
in the DIT. In cases where the subject name, as specified in the |
| 395 |
subject field, specifies a public X.500 directory entry, the |
| 396 |
countryName attribute SHOULD always be present. |
| 397 |
|
| 398 |
The commonName attribute value SHALL, when present, contain a name |
| 399 |
of the subject. This MAY be in the subject's preferred |
| 400 |
presentation format, or a format preferred by the CA, or some |
| 401 |
other format. Pseudonyms, nicknames, and names with spelling |
| 402 |
other than defined by the registered name MAY be used. To |
| 403 |
understand the nature of the name presented in commonName, |
| 404 |
complying applications MAY have to examine present values of the |
| 405 |
givenName and surname attributes, or the pseudonym attribute. |
| 406 |
|
| 407 |
Note: Many client implementations presuppose the presence of the |
| 408 |
commonName attribute value in the subject field and use this value to |
| 409 |
display the subject's name regardless of present givenName, surname, |
| 410 |
or pseudonym attribute values. |
| 411 |
|
| 412 |
The surname and givenName attribute types SHALL be used in the |
| 413 |
subject field if neither the commonName attribute nor the |
| 414 |
pseudonym attribute is present. In cases where the subject only |
| 415 |
has a givenName, the surname attribute SHALL be omitted. |
| 416 |
|
| 417 |
The pseudonym attribute type SHALL, if present, contain a |
| 418 |
pseudonym of the subject. Use of the pseudonym attribute MUST NOT |
| 419 |
be combined with use of any of the attributes surname and/or |
| 420 |
givenName. |
| 421 |
|
| 422 |
The serialNumber attribute type SHALL, when present, be used to |
| 423 |
differentiate between names where the subject field would |
| 424 |
otherwise be identical. This attribute has no defined semantics |
| 425 |
beyond ensuring uniqueness of subject names. It MAY contain a |
| 426 |
number or code assigned by the CA or an identifier assigned by a |
| 427 |
government or civil authority. It is the CA's responsibility to |
| 428 |
ensure that the serialNumber is sufficient to resolve any subject |
| 429 |
name collisions. |
| 430 |
|
| 431 |
The title attribute type SHALL, when present, be used to store a |
| 432 |
designated position or function of the subject within the |
| 433 |
organization specified by present organizational attributes in the |
| 434 |
subject field. The association between the title, the subject, |
| 435 |
and the organization is beyond the scope of this document. |
| 436 |
|
| 437 |
The organizationName and the organizationalUnitName attribute |
| 438 |
types SHALL, when present, be used to store the name and relevant |
| 439 |
information of an organization with which the subject is |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Santesson, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 447 |
|
| 448 |
|
| 449 |
associated. The type of association between the organization and |
| 450 |
the subject is beyond the scope of this document. |
| 451 |
|
| 452 |
The stateOrProvinceName and the localityName attribute types |
| 453 |
SHALL, when present, be used to store geographical information |
| 454 |
with which the subject is associated. If an organizationName |
| 455 |
value is also present, then the stateOrProvinceName and |
| 456 |
localityName attribute values SHALL be associated with the |
| 457 |
specified organization. The type of association between the |
| 458 |
stateOrProvinceName and the localityName and either the subject or |
| 459 |
the organizationName is beyond the scope of this document. |
| 460 |
|
| 461 |
Compliant implementations SHALL be able to interpret the attributes |
| 462 |
named in this section. |
| 463 |
|
| 464 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Certificate Extensions</span> |
| 465 |
|
| 466 |
This section provides additional details regarding the contents of |
| 467 |
four certificate extensions defined in <a href="./rfc3280">RFC 3280</a>: Subject Alternative |
| 468 |
Name, Subject directory attributes, Certificate policies, and Key |
| 469 |
usage. This section also defines two additional extensions: |
| 470 |
biometric information and qualified certificate statements. |
| 471 |
|
| 472 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Subject Alternative Name</span> |
| 473 |
|
| 474 |
If the subjectAltName extension is present, and it contains a |
| 475 |
directoryName name, then the directoryName MUST follow the |
| 476 |
conventions specified in <a href="#section-3.1.2">section 3.1.2</a> of this profile. |
| 477 |
|
| 478 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Subject Directory Attributes</span> |
| 479 |
|
| 480 |
The subjectDirectoryAttributes extension MAY be present and MAY |
| 481 |
contain additional attributes associated with the subject, as a |
| 482 |
complement to present information in the subject field and the |
| 483 |
subject alternative name extension. |
| 484 |
|
| 485 |
Attributes suitable for storage in this extension are attributes |
| 486 |
which are not part of the subject's distinguished name, but which MAY |
| 487 |
still be useful for other purposes (e.g., authorization). |
| 488 |
|
| 489 |
This extension MUST NOT be marked critical. |
| 490 |
|
| 491 |
Compliant implementations SHALL be able to interpret the following |
| 492 |
attributes: |
| 493 |
|
| 494 |
dateOfBirth; |
| 495 |
placeOfBirth; |
| 496 |
gender; |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Santesson, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 503 |
|
| 504 |
|
| 505 |
countryOfCitizenship; and |
| 506 |
countryOfResidence. |
| 507 |
|
| 508 |
Other attributes MAY be included according to local definitions. |
| 509 |
|
| 510 |
The dateOfBirth attribute SHALL, when present, contain the value |
| 511 |
of the date of birth of the subject. The manner in which the date |
| 512 |
of birth is associated with the subject is outside the scope of |
| 513 |
this document. The date of birth is defined in the |
| 514 |
GeneralizedTime format and SHOULD specify GMT 12.00.00 (noon) down |
| 515 |
to the granularity of seconds, in order to prevent accidental |
| 516 |
change of date due to time zone adjustments. For example, a birth |
| 517 |
date of September 27, 1959 is encoded as "19590927120000Z". |
| 518 |
Compliant certificate parsing applications SHOULD ignore any time |
| 519 |
data and just present the contained date without any time zone |
| 520 |
adjustments. |
| 521 |
|
| 522 |
The placeOfBirth attribute SHALL, when present, contain the value |
| 523 |
of the place of birth of the subject. The manner in which the |
| 524 |
place of birth is associated with the subject is outside the scope |
| 525 |
of this document. |
| 526 |
|
| 527 |
The gender attribute SHALL, when present, contain the value of the |
| 528 |
gender of the subject. For females the value "F" (or "f"), and |
| 529 |
for males the value "M" (or "m"), have to be used. The manner in |
| 530 |
which the gender is associated with the subject is outside the |
| 531 |
scope of this document. |
| 532 |
|
| 533 |
The countryOfCitizenship attribute SHALL, when present, contain |
| 534 |
the identifier of at least one of the subject's claimed countries |
| 535 |
of citizenship at the time the certificate was issued. If more |
| 536 |
than one country of citizenship is specified, each country of |
| 537 |
citizenship SHOULD be specified through a separate, single-valued |
| 538 |
countryOfCitizenship attribute. Determination of citizenship is a |
| 539 |
matter of law and is outside the scope of this document. |
| 540 |
|
| 541 |
The countryOfResidence attribute SHALL, when present, contain the |
| 542 |
value of at least one country in which the subject is resident. |
| 543 |
If more than one country of residence is specified, each country |
| 544 |
of residence SHOULD be specified through a separate, single-valued |
| 545 |
countryOfResidence attribute. Determination of residence is a |
| 546 |
matter of law and is outside the scope of this document. |
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Santesson, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Certificate Policies</span> |
| 562 |
|
| 563 |
The certificate policies extension SHALL be present and SHALL contain |
| 564 |
the identifier of at least one certificate policy which reflects the |
| 565 |
practices and procedures undertaken by the CA. The certificate |
| 566 |
policy extension MAY be marked critical. |
| 567 |
|
| 568 |
Information provided by the issuer stating the purpose of the |
| 569 |
certificate, as discussed in <a href="#section-2.2">Section 2.2</a>, SHOULD be evident through |
| 570 |
indicated policies. |
| 571 |
|
| 572 |
The certificate policies extension MUST include all policy |
| 573 |
information needed for certification path validation. If policy |
| 574 |
related statements are included in the QCStatements extension (see |
| 575 |
3.2.6), then these statements SHOULD also be contained in the |
| 576 |
identified policies. |
| 577 |
|
| 578 |
Certificate policies MAY be combined with any qualifier defined in |
| 579 |
<a href="./rfc3280">RFC 3280</a>. |
| 580 |
|
| 581 |
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Key Usage</span> |
| 582 |
|
| 583 |
The key usage extension SHALL be present. Key usage settings SHALL |
| 584 |
be set in accordance with <a href="./rfc3280">RFC 3280</a> definitions. Further requirements |
| 585 |
on key usage settings MAY be defined by local policy and/or local |
| 586 |
legal requirements. |
| 587 |
|
| 588 |
The key usage extension SHOULD be marked critical. |
| 589 |
|
| 590 |
<span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Biometric Information</span> |
| 591 |
|
| 592 |
This section defines an OPTIONAL extension for storage of biometric |
| 593 |
information. Biometric information is stored in the form of a hash |
| 594 |
of a biometric template. |
| 595 |
|
| 596 |
The purpose of this extension is to provide a means for the |
| 597 |
authentication of biometric information. The biometric information |
| 598 |
that corresponds to the stored hash is not stored in this extension, |
| 599 |
but the extension MAY include a URI (sourceDataUri) that references a |
| 600 |
file containing this information. |
| 601 |
|
| 602 |
If included, the URI MUST use the HTTP scheme (http://) [HTTP/1.1] or |
| 603 |
the HTTPS scheme (https://) [<a href="./rfc2818">RFC 2818</a>]. Since the fact that |
| 604 |
identifying data is being checked may itself be sensitive |
| 605 |
information, those deploying this mechanism may also wish to consider |
| 606 |
using URIs which cannot be easily tied by outsiders to the identities |
| 607 |
of those whose information is being retrieved. |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Santesson, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 615 |
|
| 616 |
|
| 617 |
Use of the URI option presumes that the data encoding format of the |
| 618 |
file content is determined through means outside the scope of this |
| 619 |
specification, such as file naming conventions and metadata inside |
| 620 |
the file. Use of this URI option does not imply that it is the only |
| 621 |
way to access this information. |
| 622 |
|
| 623 |
It is RECOMMENDED that biometric information in this extension be |
| 624 |
limited to information types suitable for human verification, i.e., |
| 625 |
where the decision of whether the information is an accurate |
| 626 |
representation of the subject is naturally performed by a person. |
| 627 |
This implies a usage where the biometric information is represented |
| 628 |
by, for example, a graphical image displayed to the relying party, |
| 629 |
which MAY be used by the relying party to enhance identification of |
| 630 |
the subject. |
| 631 |
|
| 632 |
This extension MUST NOT be marked critical. |
| 633 |
|
| 634 |
biometricInfo EXTENSION ::= { |
| 635 |
SYNTAX BiometricSyntax |
| 636 |
IDENTIFIED BY id-pe-biometricInfo } |
| 637 |
|
| 638 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= {id-pe 2} |
| 639 |
|
| 640 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 641 |
|
| 642 |
BiometricData ::= SEQUENCE { |
| 643 |
typeOfBiometricData TypeOfBiometricData, |
| 644 |
hashAlgorithm AlgorithmIdentifier, |
| 645 |
biometricDataHash OCTET STRING, |
| 646 |
sourceDataUri IA5String OPTIONAL } |
| 647 |
|
| 648 |
TypeOfBiometricData ::= CHOICE { |
| 649 |
predefinedBiometricType PredefinedBiometricType, |
| 650 |
biometricDataID OBJECT IDENTIFIER } |
| 651 |
|
| 652 |
PredefinedBiometricType ::= INTEGER { picture(0), |
| 653 |
handwritten-signature(1)} (picture|handwritten-signature,...) |
| 654 |
|
| 655 |
The predefined biometric type picture, when present, SHALL identify |
| 656 |
that the source picture is in the form of a displayable graphical |
| 657 |
image of the subject. The hash of the graphical image SHALL be |
| 658 |
calculated over the whole referenced image file. |
| 659 |
|
| 660 |
The predefined biometric type handwritten-signature, when present, |
| 661 |
SHALL identify that the source data is in the form of a displayable |
| 662 |
graphical image of the subject's handwritten signature. The hash of |
| 663 |
the graphical image SHALL be calculated over the whole referenced |
| 664 |
image file. |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Santesson, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h4"><a class="selflink" id="section-3.2.6" href="#section-3.2.6">3.2.6</a>. Qualified Certificate Statements</span> |
| 674 |
|
| 675 |
This section defines an OPTIONAL extension for the inclusion of |
| 676 |
statements defining explicit properties of the certificate. |
| 677 |
|
| 678 |
Each statement SHALL include an object identifier for the statement |
| 679 |
and MAY also include optional qualifying data contained in the |
| 680 |
statementInfo parameter. |
| 681 |
|
| 682 |
If the statementInfo parameter is included, then the object |
| 683 |
identifier of the statement SHALL define the syntax and SHOULD define |
| 684 |
the semantics of this parameter. If the object identifier does not |
| 685 |
define the semantics, a relying party may have to consult a relevant |
| 686 |
certificate policy or CPS to determine the exact semantics. |
| 687 |
|
| 688 |
This extension may be critical or non-critical. If the extension is |
| 689 |
critical, this means that all statements included in the extension |
| 690 |
are regarded as critical. |
| 691 |
|
| 692 |
qcStatements EXTENSION ::= { |
| 693 |
SYNTAX QCStatements |
| 694 |
IDENTIFIED BY id-pe-qcStatements } |
| 695 |
|
| 696 |
-- NOTE: This extension does not allow to mix critical and |
| 697 |
-- non-critical Qualified Certificate Statements. Either all |
| 698 |
-- statements must be critical or all statements must be |
| 699 |
-- non-critical. |
| 700 |
|
| 701 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3 } |
| 702 |
|
| 703 |
QCStatements ::= SEQUENCE OF QCStatement |
| 704 |
QCStatement ::= SEQUENCE { |
| 705 |
statementId QC-STATEMENT.&Id({SupportedStatements}), |
| 706 |
statementInfo QC-STATEMENT.&Type |
| 707 |
({SupportedStatements}{@statementId}) OPTIONAL } |
| 708 |
|
| 709 |
SupportedStatements QC-STATEMENT ::= { qcStatement-1,...} |
| 710 |
|
| 711 |
A statement suitable for inclusion in this extension MAY be a |
| 712 |
statement by the issuer that the certificate is issued as a Qualified |
| 713 |
Certificate in accordance with a particular legal system (as |
| 714 |
discussed in <a href="#section-2.2">Section 2.2</a>). |
| 715 |
|
| 716 |
Other statements suitable for inclusion in this extension MAY be |
| 717 |
statements related to the applicable legal jurisdiction within which |
| 718 |
the certificate is issued. As an example, this MAY include a maximum |
| 719 |
reliance limit for the certificate indicating restrictions on CA's |
| 720 |
liability. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Santesson, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h5"><a class="selflink" id="section-3.2.6.1" href="#section-3.2.6.1">3.2.6.1</a>. Predefined Statements</span> |
| 730 |
|
| 731 |
The certificate statement (id-qcs-pkixQCSyntax-v1), identifies |
| 732 |
conformance with requirements defined in the obsoleted <a href="./rfc3039">RFC 3039</a> |
| 733 |
(Version 1). This statement is thus provided for identification of |
| 734 |
old certificates issued in conformance with <a href="./rfc3039">RFC 3039</a>. This statement |
| 735 |
MUST NOT be included in certificates issued in accordance with this |
| 736 |
profile. |
| 737 |
|
| 738 |
This profile includes a new qualified certificate statement |
| 739 |
(identified by the OID id-qcs-pkixQCSyntax-v2), identifying |
| 740 |
conformance with requirements defined in this profile. This |
| 741 |
Qualified Certificate profile is referred to as version 2, while <a href="./rfc3039">RFC</a> |
| 742 |
<a href="./rfc3039">3039</a> is referred to as version 1. |
| 743 |
|
| 744 |
qcStatement-1 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 745 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v1 } |
| 746 |
-- This statement identifies conformance with requirements |
| 747 |
-- defined in <a href="./rfc3039">RFC 3039</a> (Version 1). This statement may |
| 748 |
-- optionally contain additional semantics information as |
| 749 |
-- specified below. |
| 750 |
|
| 751 |
qcStatement-2 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 752 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v2 } |
| 753 |
-- This statement identifies conformance with requirements |
| 754 |
-- defined in this Qualified Certificate profile |
| 755 |
-- (Version 2). This statement may optionally contain |
| 756 |
-- additional semantics information as specified below. |
| 757 |
|
| 758 |
SemanticsInformation ::= SEQUENCE { |
| 759 |
semanticsIdentifier OBJECT IDENTIFIER OPTIONAL, |
| 760 |
nameRegistrationAuthorities NameRegistrationAuthorities |
| 761 |
OPTIONAL } |
| 762 |
(WITH COMPONENTS {..., semanticsIdentifier PRESENT}| |
| 763 |
WITH COMPONENTS {..., nameRegistrationAuthorities PRESENT}) |
| 764 |
|
| 765 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF |
| 766 |
GeneralName |
| 767 |
|
| 768 |
The SementicsInformation component identified by id-qcs- |
| 769 |
pkixQCSyntax-v1 MAY contain a semantics identifier and MAY identify |
| 770 |
one or more name registration authorities. |
| 771 |
|
| 772 |
The semanticsIdentifier component, if present, SHALL contain an OID, |
| 773 |
defining semantics for attributes and names in basic certificate |
| 774 |
fields and certificate extensions. The OID may define semantics for |
| 775 |
all, or for a subgroup of all present attributes and/or names. |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Santesson, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 783 |
|
| 784 |
|
| 785 |
The NameRegistrationAuthorities component, if present, SHALL contain |
| 786 |
a name of one or more name registration authorities, responsible for |
| 787 |
registration of attributes or names associated with the subject. The |
| 788 |
association between an identified name registration authority and |
| 789 |
present attributes MAY be defined by a semantics identifier OID, by a |
| 790 |
certificate policy (or CPS), or some other implicit factors. |
| 791 |
|
| 792 |
If a value of type SemanticsInformation is present in a QCStatement |
| 793 |
where the statementID component is set to id-qcs-pkix-QCSyntax-v1 or |
| 794 |
id-qcs-pkix-QCSyntax-v2, then at least one of the semanticsIdentifier |
| 795 |
or nameRegistrationAuthorities fields must be present, as indicated. |
| 796 |
Note that the statementInfo component need not be present in a |
| 797 |
QCStatement value even if the statementID component is set to id- |
| 798 |
qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2. |
| 799 |
|
| 800 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 801 |
|
| 802 |
The legal value of a digital signature that is validated with a |
| 803 |
Qualified Certificate will be highly dependent upon the policy |
| 804 |
governing the use of the associated private key. Both the private |
| 805 |
key holder, as well as the relying party, should make sure that the |
| 806 |
private key is used only with the consent of the legitimate key |
| 807 |
holder. |
| 808 |
|
| 809 |
Since the public keys are for public use with legal implications for |
| 810 |
involved parties, certain conditions should exist before CAs issue |
| 811 |
certificates as Qualified Certificates. The associated private keys |
| 812 |
must be unique for the subject, and must be maintained under the |
| 813 |
subject's sole control. That is, a CA should not issue a qualified |
| 814 |
certificate if the means to use the private key is not protected |
| 815 |
against unintended usage. This implies that the CA has some |
| 816 |
knowledge about the subject's cryptographic module. |
| 817 |
|
| 818 |
The CA must further verify that the public key contained in the |
| 819 |
certificate is legitimately representing the subject. |
| 820 |
|
| 821 |
CAs should not issue CA certificates with policy mapping extensions |
| 822 |
indicating acceptance of another CA's policy unless these conditions |
| 823 |
are met. |
| 824 |
|
| 825 |
Combining the nonRepudiation bit in the keyUsage certificate |
| 826 |
extension with other keyUsage bits may have security implications |
| 827 |
depending on the context in which the certificate is to be used. |
| 828 |
Applications validating electronic signatures based on such |
| 829 |
certificates should determine whether the present key usage |
| 830 |
combination is appropriate for their use. |
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Santesson, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 839 |
|
| 840 |
|
| 841 |
The ability to compare two qualified certificates to determine if |
| 842 |
they represent the same physical entity is dependent on the semantics |
| 843 |
of the subjects' names. The semantics of a particular attribute may |
| 844 |
be different for different issuers. Comparing names without |
| 845 |
knowledge of the semantics of names in these particular certificates |
| 846 |
may provide misleading results. |
| 847 |
|
| 848 |
This specification is a profile of <a href="./rfc3280">RFC 3280</a>. The security |
| 849 |
considerations section of that document applies to this specification |
| 850 |
as well. |
| 851 |
|
| 852 |
|
| 853 |
|
| 854 |
|
| 855 |
|
| 856 |
|
| 857 |
|
| 858 |
|
| 859 |
|
| 860 |
|
| 861 |
|
| 862 |
|
| 863 |
|
| 864 |
|
| 865 |
|
| 866 |
|
| 867 |
|
| 868 |
|
| 869 |
|
| 870 |
|
| 871 |
|
| 872 |
|
| 873 |
|
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Santesson, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">A</a>. ASN.1 Definitions</span> |
| 898 |
|
| 899 |
As in <a href="./rfc3280">RFC 3280</a>, ASN.1 modules are supplied in two different variants |
| 900 |
of the ASN.1 syntax. |
| 901 |
|
| 902 |
<a href="#appendix-A.1">Appendix A.1</a> is in the 1988 syntax, and does not use macros. |
| 903 |
However, since the module imports type definitions from modules in |
| 904 |
<a href="./rfc3280">RFC 3280</a> which are not completely in the 1988 syntax, the same |
| 905 |
comments as in <a href="./rfc3280">RFC 3280</a> regarding its use applies here as well; i.e., |
| 906 |
<a href="#appendix-A.1">Appendix A.1</a> may be parsed by an 1988 ASN.1-parser by removing the |
| 907 |
definitions for the UNIVERSAL types and all references to them in <a href="./rfc3280">RFC</a> |
| 908 |
<a href="./rfc3280">3280</a>'s 1988 modules. |
| 909 |
|
| 910 |
<a href="#appendix-A.2">Appendix A.2</a> is in the 1997 syntax. |
| 911 |
|
| 912 |
In case of discrepancies between these modules, the 1988 module is |
| 913 |
the normative one. |
| 914 |
|
| 915 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. 1988 ASN.1 Module (Normative)</span> |
| 916 |
|
| 917 |
PKIXqualified88 {iso(1) identified-organization(3) dod(6) |
| 918 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 919 |
id-mod-qualified-cert(31) } |
| 920 |
|
| 921 |
DEFINITIONS EXPLICIT TAGS ::= |
| 922 |
|
| 923 |
BEGIN |
| 924 |
|
| 925 |
-- EXPORTS ALL -- |
| 926 |
|
| 927 |
IMPORTS |
| 928 |
|
| 929 |
GeneralName |
| 930 |
FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6) |
| 931 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 932 |
id-pkix1-implicit(19)} |
| 933 |
|
| 934 |
AlgorithmIdentifier, DirectoryString, AttributeType, id-pkix, id-pe |
| 935 |
FROM PKIX1Explicit88 {iso(1) identified-organization(3) dod(6) |
| 936 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 937 |
id-pkix1-explicit(18)}; |
| 938 |
|
| 939 |
-- Locally defined OIDs |
| 940 |
|
| 941 |
-- Arc for QC personal data attributes |
| 942 |
id-pda OBJECT IDENTIFIER ::= { id-pkix 9 } |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Santesson, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 951 |
|
| 952 |
|
| 953 |
-- Arc for QC statements |
| 954 |
id-qcs OBJECT IDENTIFIER ::= { id-pkix 11 } |
| 955 |
|
| 956 |
-- Personal data attributes |
| 957 |
|
| 958 |
id-pda-dateOfBirth AttributeType ::= { id-pda 1 } |
| 959 |
DateOfBirth ::= GeneralizedTime |
| 960 |
|
| 961 |
id-pda-placeOfBirth AttributeType ::= { id-pda 2 } |
| 962 |
PlaceOfBirth ::= DirectoryString |
| 963 |
|
| 964 |
id-pda-gender AttributeType ::= { id-pda 3 } |
| 965 |
Gender ::= PrintableString (SIZE(1)) |
| 966 |
-- "M", "F", "m" or "f" |
| 967 |
|
| 968 |
id-pda-countryOfCitizenship AttributeType ::= { id-pda 4 } |
| 969 |
CountryOfCitizenship ::= PrintableString (SIZE (2)) |
| 970 |
-- ISO 3166 Country Code |
| 971 |
|
| 972 |
id-pda-countryOfResidence AttributeType ::= { id-pda 5 } |
| 973 |
CountryOfResidence ::= PrintableString (SIZE (2)) |
| 974 |
-- ISO 3166 Country Code |
| 975 |
|
| 976 |
-- Certificate extensions |
| 977 |
|
| 978 |
-- Biometric info extension |
| 979 |
|
| 980 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= {id-pe 2} |
| 981 |
|
| 982 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 983 |
|
| 984 |
BiometricData ::= SEQUENCE { |
| 985 |
typeOfBiometricData TypeOfBiometricData, |
| 986 |
hashAlgorithm AlgorithmIdentifier, |
| 987 |
biometricDataHash OCTET STRING, |
| 988 |
sourceDataUri IA5String OPTIONAL } |
| 989 |
|
| 990 |
TypeOfBiometricData ::= CHOICE { |
| 991 |
predefinedBiometricType PredefinedBiometricType, |
| 992 |
biometricDataOid OBJECT IDENTIFIER } |
| 993 |
|
| 994 |
PredefinedBiometricType ::= INTEGER { |
| 995 |
picture(0), handwritten-signature(1)} |
| 996 |
(picture|handwritten-signature) |
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Santesson, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
-- QC Statements Extension |
| 1010 |
-- NOTE: This extension does not allow to mix critical and |
| 1011 |
-- non-critical Qualified Certificate Statements. Either all |
| 1012 |
-- statements must be critical or all statements must be |
| 1013 |
-- non-critical. |
| 1014 |
|
| 1015 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3} |
| 1016 |
|
| 1017 |
QCStatements ::= SEQUENCE OF QCStatement |
| 1018 |
|
| 1019 |
QCStatement ::= SEQUENCE { |
| 1020 |
statementId OBJECT IDENTIFIER, |
| 1021 |
statementInfo ANY DEFINED BY statementId OPTIONAL} |
| 1022 |
|
| 1023 |
-- QC statements |
| 1024 |
id-qcs-pkixQCSyntax-v1 OBJECT IDENTIFIER ::= { id-qcs 1 } |
| 1025 |
-- This statement identifies conformance with requirements |
| 1026 |
-- defined in <a href="./rfc3039">RFC 3039</a> (Version 1). This statement may |
| 1027 |
-- optionally contain additional semantics information as specified |
| 1028 |
-- below. |
| 1029 |
|
| 1030 |
id-qcs-pkixQCSyntax-v2 OBJECT IDENTIFIER ::= { id-qcs 2 } |
| 1031 |
-- This statement identifies conformance with requirements |
| 1032 |
-- defined in this Qualified Certificate profile |
| 1033 |
-- (Version 2). This statement may optionally contain |
| 1034 |
-- additional semantics information as specified below. |
| 1035 |
|
| 1036 |
SemanticsInformation ::= SEQUENCE { |
| 1037 |
semanticsIndentifier OBJECT IDENTIFIER OPTIONAL, |
| 1038 |
nameRegistrationAuthorities NameRegistrationAuthorities OPTIONAL |
| 1039 |
} -- At least one field shall be present |
| 1040 |
|
| 1041 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF GeneralName |
| 1042 |
|
| 1043 |
END |
| 1044 |
|
| 1045 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. 1997 ASN.1 Module (Informative)</span> |
| 1046 |
|
| 1047 |
PKIXqualified97 {iso(1) identified-organization(3) dod(6) |
| 1048 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 1049 |
id-mod-qualified-cert-97(35) } |
| 1050 |
|
| 1051 |
DEFINITIONS EXPLICIT TAGS ::= |
| 1052 |
|
| 1053 |
BEGIN |
| 1054 |
|
| 1055 |
-- EXPORTS ALL -- |
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Santesson, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
IMPORTS |
| 1066 |
|
| 1067 |
informationFramework, certificateExtensions, selectedAttributeTypes, |
| 1068 |
authenticationFramework, upperBounds, id-at |
| 1069 |
FROM UsefulDefinitions {joint-iso-itu-t(2) ds(5) module(1) |
| 1070 |
usefulDefinitions(0) 3 } |
| 1071 |
|
| 1072 |
ub-name |
| 1073 |
FROM UpperBounds upperBounds |
| 1074 |
|
| 1075 |
GeneralName |
| 1076 |
FROM CertificateExtensions certificateExtensions |
| 1077 |
|
| 1078 |
ATTRIBUTE, AttributeType |
| 1079 |
FROM InformationFramework informationFramework |
| 1080 |
|
| 1081 |
DirectoryString |
| 1082 |
FROM SelectedAttributeTypes selectedAttributeTypes |
| 1083 |
|
| 1084 |
AlgorithmIdentifier, Extension, EXTENSION |
| 1085 |
FROM AuthenticationFramework authenticationFramework |
| 1086 |
|
| 1087 |
id-pkix, id-pe |
| 1088 |
FROM PKIX1Explicit88 { iso(1) identified-organization(3) dod(6) |
| 1089 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 1090 |
id-pkix1-explicit(18) }; |
| 1091 |
|
| 1092 |
-- Locally defined OIDs |
| 1093 |
|
| 1094 |
-- Arc for QC personal data attributes |
| 1095 |
id-pda OBJECT IDENTIFIER ::= { id-pkix 9 } |
| 1096 |
|
| 1097 |
-- Arc for QC statements |
| 1098 |
id-qcs OBJECT IDENTIFIER ::= { id-pkix 11 } |
| 1099 |
|
| 1100 |
-- Personal data attributes |
| 1101 |
|
| 1102 |
id-pda-dateOfBirth AttributeType ::= { id-pda 1 } |
| 1103 |
id-pda-placeOfBirth AttributeType ::= { id-pda 2 } |
| 1104 |
id-pda-gender AttributeType ::= { id-pda 3 } |
| 1105 |
id-pda-countryOfCitizenship AttributeType ::= { id-pda 4 } |
| 1106 |
id-pda-countryOfResidence AttributeType ::= { id-pda 5 } |
| 1107 |
|
| 1108 |
-- Certificate extensions |
| 1109 |
|
| 1110 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= { id-pe 2 } |
| 1111 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3 } |
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Santesson, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
-- QC statements |
| 1122 |
|
| 1123 |
id-qcs-pkixQCSyntax-v1 OBJECT IDENTIFIER ::= { id-qcs 1 } |
| 1124 |
id-qcs-pkixQCSyntax-v2 OBJECT IDENTIFIER ::= { id-qcs 2 } |
| 1125 |
|
| 1126 |
-- Personal data attributes |
| 1127 |
|
| 1128 |
dateOfBirth ATTRIBUTE ::= { |
| 1129 |
WITH SYNTAX GeneralizedTime |
| 1130 |
ID id-pda-dateOfBirth } |
| 1131 |
|
| 1132 |
placeOfBirth ATTRIBUTE ::= { |
| 1133 |
WITH SYNTAX DirectoryString {ub-name} |
| 1134 |
ID id-pda-placeOfBirth } |
| 1135 |
|
| 1136 |
gender ATTRIBUTE ::= { |
| 1137 |
WITH SYNTAX PrintableString (SIZE(1) ^ FROM("M"|"F"|"m"|"f")) |
| 1138 |
ID id-pda-gender } |
| 1139 |
|
| 1140 |
countryOfCitizenship ATTRIBUTE ::= { |
| 1141 |
WITH SYNTAX PrintableString (SIZE (2)) |
| 1142 |
(CONSTRAINED BY { -- ISO 3166 codes only -- }) |
| 1143 |
ID id-pda-countryOfCitizenship } |
| 1144 |
|
| 1145 |
countryOfResidence ATTRIBUTE ::= { |
| 1146 |
WITH SYNTAX PrintableString (SIZE (2)) |
| 1147 |
(CONSTRAINED BY { -- ISO 3166 codes only -- }) |
| 1148 |
ID id-pda-countryOfResidence } |
| 1149 |
|
| 1150 |
-- Certificate extensions |
| 1151 |
|
| 1152 |
-- Biometric info extension |
| 1153 |
|
| 1154 |
biometricInfo EXTENSION ::= { |
| 1155 |
SYNTAX BiometricSyntax |
| 1156 |
IDENTIFIED BY id-pe-biometricInfo } |
| 1157 |
|
| 1158 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 1159 |
|
| 1160 |
BiometricData ::= SEQUENCE { |
| 1161 |
typeOfBiometricData TypeOfBiometricData, |
| 1162 |
hashAlgorithm AlgorithmIdentifier, |
| 1163 |
biometricDataHash OCTET STRING, |
| 1164 |
sourceDataUri IA5String OPTIONAL, |
| 1165 |
... -- For future extensions -- } |
| 1166 |
|
| 1167 |
TypeOfBiometricData ::= CHOICE { |
| 1168 |
predefinedBiometricType PredefinedBiometricType, |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Santesson, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
biometricDataOid OBJECT IDENTIFIER } |
| 1178 |
|
| 1179 |
PredefinedBiometricType ::= INTEGER { |
| 1180 |
picture(0), handwritten-signature(1)} |
| 1181 |
(picture|handwritten-signature,...) |
| 1182 |
|
| 1183 |
-- QC Statements Extension |
| 1184 |
-- NOTE: This extension does not allow to mix critical and |
| 1185 |
-- non-critical Qualified Certificate Statements. Either all |
| 1186 |
-- statements must be critical or all statements must be |
| 1187 |
-- non-critical. |
| 1188 |
|
| 1189 |
qcStatements EXTENSION ::= { |
| 1190 |
SYNTAX QCStatements |
| 1191 |
IDENTIFIED BY id-pe-qcStatements } |
| 1192 |
|
| 1193 |
QCStatements ::= SEQUENCE OF QCStatement |
| 1194 |
|
| 1195 |
QCStatement ::= SEQUENCE { |
| 1196 |
statementId QC-STATEMENT.&id({SupportedStatements}), |
| 1197 |
statementInfo QC-STATEMENT.&Type |
| 1198 |
({SupportedStatements}{@statementId}) OPTIONAL } |
| 1199 |
|
| 1200 |
QC-STATEMENT ::= CLASS { |
| 1201 |
&id OBJECT IDENTIFIER UNIQUE, |
| 1202 |
&Type OPTIONAL } |
| 1203 |
WITH SYNTAX { |
| 1204 |
[SYNTAX &Type] IDENTIFIED BY &id } |
| 1205 |
|
| 1206 |
qcStatement-1 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 1207 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v1} |
| 1208 |
-- This statement identifies conformance with requirements |
| 1209 |
-- defined in <a href="./rfc3039">RFC 3039</a> (Version 1). This statement |
| 1210 |
-- may optionally contain additional semantics information |
| 1211 |
-- as specified below. |
| 1212 |
|
| 1213 |
qcStatement-2 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 1214 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v2} |
| 1215 |
-- This statement identifies conformance with requirements |
| 1216 |
-- defined in this Qualified Certificate profile |
| 1217 |
-- (Version 2). This statement may optionally contain |
| 1218 |
-- additional semantics information as specified below. |
| 1219 |
|
| 1220 |
SemanticsInformation ::= SEQUENCE { |
| 1221 |
semanticsIdentifier OBJECT IDENTIFIER OPTIONAL, |
| 1222 |
nameRegistrationAuthorities NameRegistrationAuthorities OPTIONAL |
| 1223 |
}(WITH COMPONENTS {..., semanticsIdentifier PRESENT}| |
| 1224 |
WITH COMPONENTS {..., nameRegistrationAuthorities PRESENT}) |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Santesson, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF GeneralName |
| 1234 |
|
| 1235 |
-- The following information object set is defined to constrain the |
| 1236 |
-- set of attributes applications are required to recognize as QCSs. |
| 1237 |
SupportedStatements QC-STATEMENT ::= { |
| 1238 |
qcStatement-1 | |
| 1239 |
qcStatement-2 , ... -- For future extensions -- } |
| 1240 |
|
| 1241 |
END |
| 1242 |
|
| 1243 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">B</a>. A Note on Attributes</span> |
| 1244 |
|
| 1245 |
This document defines several new attributes, both for use in the |
| 1246 |
subject field of issued certificates and in the |
| 1247 |
subjectDirectoryAttributes extension. A complete definition of these |
| 1248 |
new attributes (including matching rules), along with object classes |
| 1249 |
to support them in LDAP-accessible directories, can be found in |
| 1250 |
PKCS 9 [<a href="./rfc2985">RFC 2985</a>]. |
| 1251 |
|
| 1252 |
<span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">C</a>. Example Certificate</span> |
| 1253 |
|
| 1254 |
This section contains the ASN.1 structure, an ASN.1 dump, and the |
| 1255 |
DER-encoding of a certificate issued in conformance with this |
| 1256 |
profile. The example has been developed with the help of the OSS |
| 1257 |
ASN.1 compiler. The certificate has the following characteristics: |
| 1258 |
|
| 1259 |
1. The certificate is signed with RSA and the SHA-1 hash |
| 1260 |
algorithm |
| 1261 |
|
| 1262 |
2. The issuer's distinguished name is (using the syntax specified |
| 1263 |
in [<a href="./rfc2253">RFC 2253</a>]): O=GMD - Forschungszentrum Informationstechnik |
| 1264 |
GmbH, C=DE |
| 1265 |
|
| 1266 |
3. The subject's distinguished name is (using the syntax |
| 1267 |
specified in [<a href="./rfc2253">RFC 2253</a>]): GN=Petra+SN=Barzin, O=GMD |
| 1268 |
- Forschungszentrum Informationstechnik GmbH, C=DE |
| 1269 |
|
| 1270 |
4. The certificate was issued on 1 February, 2004 and will expire |
| 1271 |
on 1 February, 2008 |
| 1272 |
|
| 1273 |
5. The certificate contains a 1024 bit RSA key |
| 1274 |
|
| 1275 |
6. The certificate includes a critical key usage extension |
| 1276 |
exclusively indicating non-repudiation |
| 1277 |
|
| 1278 |
7. The certificate includes a certificate policy identifier |
| 1279 |
extension indicating the practices and procedures undertaken |
| 1280 |
by the issuing CA (object identifier 1.3.36.8.1.1). The |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Santesson, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
certificate policy object identifier is defined by TeleTrust, |
| 1290 |
Germany. |
| 1291 |
|
| 1292 |
8. The certificate includes a subject directory attributes |
| 1293 |
extension containing the following attributes: |
| 1294 |
|
| 1295 |
date of birth: October, 14th 1971 |
| 1296 |
place of birth: Darmstadt |
| 1297 |
country of citizenship:Germany |
| 1298 |
gender: Female |
| 1299 |
|
| 1300 |
9. The certificate includes a qualified statement certificate |
| 1301 |
extension indicating that the naming registration authority's |
| 1302 |
name is "[email protected]". |
| 1303 |
|
| 1304 |
10. The certificate includes, in conformance with <a href="./rfc3280">RFC 3280</a>, an |
| 1305 |
authority key identifier extension. |
| 1306 |
|
| 1307 |
<span class="h3"><a class="selflink" id="appendix-C.1" href="#appendix-C.1">C.1</a>. ASN.1 Structure</span> |
| 1308 |
|
| 1309 |
<span class="h4"><a class="selflink" id="appendix-C.1.1" href="#appendix-C.1.1">C.1.1</a>. Extensions</span> |
| 1310 |
|
| 1311 |
Since extensions are DER-encoded already when placed in the structure |
| 1312 |
to be signed, they are, for clarity, shown here in the value notation |
| 1313 |
defined in [<a href="#ref-X.680" title=" Information Technology - Abstract Syntax Notation One">X.680</a>]. |
| 1314 |
|
| 1315 |
<span class="h5"><a class="selflink" id="appendix-C.1.1.1" href="#appendix-C.1.1.1">C.1.1.1</a>. The subjectDirectoryAttributes Extension</span> |
| 1316 |
|
| 1317 |
certSubjDirAttrs AttributesSyntax ::= { |
| 1318 |
{ |
| 1319 |
type id-pda-countryOfCitizenship, |
| 1320 |
values { |
| 1321 |
PrintableString : "DE" |
| 1322 |
} |
| 1323 |
}, |
| 1324 |
{ |
| 1325 |
type id-pda-gender, |
| 1326 |
values { |
| 1327 |
PrintableString : "F" |
| 1328 |
} |
| 1329 |
}, |
| 1330 |
{ |
| 1331 |
type id-pda-dateOfBirth, |
| 1332 |
values { |
| 1333 |
GeneralizedTime : "197110141200Z" |
| 1334 |
} |
| 1335 |
}, |
| 1336 |
{ |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Santesson, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
type id-pda-placeOfBirth, |
| 1346 |
values { |
| 1347 |
DirectoryString : utf8String : "Darmstadt" |
| 1348 |
} |
| 1349 |
} |
| 1350 |
} |
| 1351 |
|
| 1352 |
<span class="h5"><a class="selflink" id="appendix-C.1.1.2" href="#appendix-C.1.1.2">C.1.1.2</a>. The keyUsage Extension</span> |
| 1353 |
|
| 1354 |
certKeyUsage KeyUsage ::= {nonRepudiation} |
| 1355 |
|
| 1356 |
<span class="h5"><a class="selflink" id="appendix-C.1.1.3" href="#appendix-C.1.1.3">C.1.1.3</a>. The certificatePolicies Extension</span> |
| 1357 |
|
| 1358 |
certCertificatePolicies CertificatePoliciesSyntax ::= { |
| 1359 |
{ |
| 1360 |
policyIdentifier {1 3 36 8 1 1} |
| 1361 |
} |
| 1362 |
} |
| 1363 |
|
| 1364 |
<span class="h5"><a class="selflink" id="appendix-C.1.1.4" href="#appendix-C.1.1.4">C.1.1.4</a>. The qcStatements Extension</span> |
| 1365 |
|
| 1366 |
certQCStatement QCStatements ::= { |
| 1367 |
{ |
| 1368 |
statementId id-qcs-pkixQCSyntax-v2, |
| 1369 |
statementInfo SemanticsInformation : { |
| 1370 |
nameRegistrationAuthorities { |
| 1371 |
rfc822Name : "[email protected]" |
| 1372 |
} |
| 1373 |
} |
| 1374 |
} |
| 1375 |
} |
| 1376 |
|
| 1377 |
<span class="h5"><a class="selflink" id="appendix-C.1.1.5" href="#appendix-C.1.1.5">C.1.1.5</a>. The authorityKeyIdentifier Extension</span> |
| 1378 |
|
| 1379 |
certAKI AuthorityKeyIdentifier ::= { |
| 1380 |
keyIdentifier '000102030405060708090A0B0C0D0E0FFEDCBA98'H |
| 1381 |
} |
| 1382 |
|
| 1383 |
<span class="h4"><a class="selflink" id="appendix-C.1.2" href="#appendix-C.1.2">C.1.2</a>. The Certificate</span> |
| 1384 |
|
| 1385 |
The signed portion of the certificate is shown here in the value |
| 1386 |
notation defined in [<a href="#ref-X.680" title=" Information Technology - Abstract Syntax Notation One">X.680</a>]. Note that extension values are already |
| 1387 |
DER encoded in this structure. Some values have been truncated for |
| 1388 |
readability purposes. |
| 1389 |
|
| 1390 |
certCertInfo CertificateInfo ::= { |
| 1391 |
version v3, |
| 1392 |
serialNumber 1234567890, |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Santesson, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
signature |
| 1402 |
{ |
| 1403 |
algorithm { 1 2 840 113549 1 1 5 }, |
| 1404 |
parameters RSAParams : NULL |
| 1405 |
}, |
| 1406 |
issuer rdnSequence : |
| 1407 |
{ |
| 1408 |
{ |
| 1409 |
{ |
| 1410 |
type { 2 5 4 6 }, |
| 1411 |
value PrintableString : "DE" |
| 1412 |
} |
| 1413 |
}, |
| 1414 |
{ |
| 1415 |
{ |
| 1416 |
type { 2 5 4 10 }, |
| 1417 |
value UTF8String : |
| 1418 |
} |
| 1419 |
} |
| 1420 |
}, |
| 1421 |
validity |
| 1422 |
{ |
| 1423 |
notBefore utcTime : "040201100000Z", |
| 1424 |
notAfter utcTime : "080201100000Z" |
| 1425 |
}, |
| 1426 |
subject rdnSequence : |
| 1427 |
{ |
| 1428 |
{ |
| 1429 |
{ |
| 1430 |
type { 2 5 4 6 }, |
| 1431 |
value PrintableString : "DE" |
| 1432 |
} |
| 1433 |
}, |
| 1434 |
{ |
| 1435 |
{ |
| 1436 |
type { 2 5 4 10 }, |
| 1437 |
value UTF8String : |
| 1438 |
"GMD Forschungszentrum Informationstechnik GmbH" |
| 1439 |
} |
| 1440 |
}, |
| 1441 |
{ |
| 1442 |
{ |
| 1443 |
type { 2 5 4 4 }, |
| 1444 |
value UTF8String : "Barzin" |
| 1445 |
}, |
| 1446 |
{ |
| 1447 |
type { 2 5 4 42 }, |
| 1448 |
value UTF8String : "Petra" |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Santesson, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
} |
| 1458 |
} |
| 1459 |
}, |
| 1460 |
subjectPublicKeyInfo |
| 1461 |
{ |
| 1462 |
algorithm |
| 1463 |
{ |
| 1464 |
algorithm { 1 2 840 113549 1 1 1 }, |
| 1465 |
parameters RSAParams : NULL |
| 1466 |
}, |
| 1467 |
subjectPublicKey '30818902818100DCE74CD5...0203010001'H |
| 1468 |
}, |
| 1469 |
extensions |
| 1470 |
{ |
| 1471 |
{ |
| 1472 |
extnId { 2 5 29 9 }, -- subjectDirectoryAttributes |
| 1473 |
extnValue '305B301006082B0601050507090...7374616474'H |
| 1474 |
}, |
| 1475 |
{ |
| 1476 |
extnId { 2 5 29 15 }, -- keyUsage |
| 1477 |
critical TRUE, |
| 1478 |
extnValue '03020640'H |
| 1479 |
}, |
| 1480 |
{ |
| 1481 |
extnId { 2 5 29 32 }, -- certificatePolicies |
| 1482 |
extnValue '3009300706052B24080101'H |
| 1483 |
}, |
| 1484 |
{ |
| 1485 |
extnId { 2 5 29 35 }, -- authorityKeyIdentifier |
| 1486 |
extnValue '30168014000102030405060708090A0B0C0D0E0FFEDCBA98'H |
| 1487 |
}, |
| 1488 |
{ |
| 1489 |
extnId { 1 3 6 1 5 5 7 1 3 }, -- qcStatements |
| 1490 |
extnValue '302B302906082B06010505070B0...4742E6465 'H |
| 1491 |
} |
| 1492 |
} |
| 1493 |
} |
| 1494 |
|
| 1495 |
<span class="h3"><a class="selflink" id="appendix-C.2" href="#appendix-C.2">C.2</a>. ASN.1 Dump</span> |
| 1496 |
|
| 1497 |
This section contains an ASN.1 dump of the signed portion of the |
| 1498 |
certificate. Some values have been truncated for readability |
| 1499 |
purposes. |
| 1500 |
|
| 1501 |
CertificateInfo SEQUENCE: tag = [UNIVERSAL 16] constructed; length = 633 |
| 1502 |
version : tag = [0] constructed; length = 3 |
| 1503 |
Version INTEGER: tag = [UNIVERSAL 2] primitive; length = 1 |
| 1504 |
2 |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Santesson, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
serialNumber CertificateSerialNumber INTEGER: tag = [UNIVERSAL 2] |
| 1514 |
primitive; length = 4 |
| 1515 |
1234567890 |
| 1516 |
signature AlgorithmIdentifier SEQUENCE: tag = [UNIVERSAL 16] |
| 1517 |
constructed; length = 13 |
| 1518 |
algorithm OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1519 |
primitive; length = 9 |
| 1520 |
{ 1 2 840 113549 1 1 5 } |
| 1521 |
parameters OpenType |
| 1522 |
NULL |
| 1523 |
issuer Name CHOICE |
| 1524 |
rdnSequence RDNSequence SEQUENCE OF: tag = [UNIVERSAL 16] |
| 1525 |
constructed; length = 72 |
| 1526 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1527 |
constructed; length = 11 |
| 1528 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1529 |
constructed; length = 9 |
| 1530 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1531 |
primitive; length = 3 |
| 1532 |
{ 2 5 4 6 } -- id-at-countryName |
| 1533 |
value PrintableString |
| 1534 |
"DE" |
| 1535 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1536 |
constructed; length = 57 |
| 1537 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1538 |
constructed; length = 55 |
| 1539 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1540 |
primitive; length = 3 |
| 1541 |
{ 2 5 4 10 } -- id-at-organizationName |
| 1542 |
value UTF8String |
| 1543 |
"GMD Forschungszentrum Informationstechnik GmbH" |
| 1544 |
validity Validity SEQUENCE: tag = [UNIVERSAL 16] |
| 1545 |
constructed; length = 30 |
| 1546 |
notBefore Time CHOICE |
| 1547 |
utcTime UTCTime: tag = [UNIVERSAL 23] primitive; length = 13 |
| 1548 |
040201100000Z |
| 1549 |
notAfter Time CHOICE |
| 1550 |
utcTime UTCTime: tag = [UNIVERSAL 23] primitive; length = 13 |
| 1551 |
080201100000Z |
| 1552 |
subject Name CHOICE |
| 1553 |
rdnSequence RDNSequence SEQUENCE OF: tag = [UNIVERSAL 16] |
| 1554 |
constructed; length = 101 |
| 1555 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1556 |
constructed; length = 11 |
| 1557 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1558 |
constructed; length = 9 |
| 1559 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1560 |
primitive; length = 3 |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Santesson, et al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
{ 2 5 4 6 } -- id-at-countryName |
| 1570 |
value PrintableString |
| 1571 |
"DE" |
| 1572 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1573 |
constructed; length = 55 |
| 1574 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1575 |
constructed; length = 53 |
| 1576 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1577 |
primitive; length = 3 |
| 1578 |
{ 2 5 4 10 } -- id-at-organizationName |
| 1579 |
value UTF8String |
| 1580 |
"GMD Forschungszentrum Informationstechnik GmbH" |
| 1581 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1582 |
constructed; length = 29 |
| 1583 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1584 |
constructed; length = 13 |
| 1585 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1586 |
primitive; length = 3 |
| 1587 |
{ 2 5 4 4 } -- id-at-surname |
| 1588 |
value UTF8String |
| 1589 |
"Barzin" |
| 1590 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1591 |
constructed; length = 12 |
| 1592 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1593 |
primitive; length = 3 |
| 1594 |
{ 2 5 4 42 } -- id-at-givenName |
| 1595 |
value UTF8String |
| 1596 |
"Petra" |
| 1597 |
subjectPublicKeyInfo SubjectPublicKeyInfo SEQUENCE: |
| 1598 |
tag = [UNIVERSAL 16] constructed; length = 159 |
| 1599 |
algorithm AlgorithmIdentifier SEQUENCE: tag = [UNIVERSAL 16] |
| 1600 |
constructed; length = 13 |
| 1601 |
algorithm OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1602 |
primitive; length = 9 |
| 1603 |
{ 1 2 840 113549 1 1 1 } -- rsaEncryption |
| 1604 |
parameters OpenType |
| 1605 |
NULL |
| 1606 |
subjectPublicKey BIT STRING: tag = [UNIVERSAL 3] |
| 1607 |
primitive; length = 141 |
| 1608 |
0x0030818902818100dce74cd5a1d55aeb01cf5ecc20f3c3fca787... |
| 1609 |
extensions : tag = [3] constructed; length = 233 |
| 1610 |
Extensions SEQUENCE OF: tag = [UNIVERSAL 16] |
| 1611 |
constructed; length = 230 |
| 1612 |
Extension SEQUENCE: tag = [UNIVERSAL 16] |
| 1613 |
constructed; length = 100 |
| 1614 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1615 |
primitive; length = 3 |
| 1616 |
{ 2 5 29 9 } -- id-ce-subjectDirectoryAttributes |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Santesson, et al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] |
| 1626 |
primitive; length = 93 |
| 1627 |
0x305b301006082b06010505070904310413024445300f06082... |
| 1628 |
Extension SEQUENCE: tag = [UNIVERSAL 16] |
| 1629 |
constructed; length = 14 |
| 1630 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1631 |
primitive; length = 3 |
| 1632 |
{ 2 5 29 15 } -- id-ce-keyUsage |
| 1633 |
critical BOOLEAN: tag = [UNIVERSAL 1] primitive; length = 1 |
| 1634 |
TRUE |
| 1635 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] |
| 1636 |
primitive; length = 4 |
| 1637 |
0x03020640 |
| 1638 |
Extension SEQUENCE: tag = [UNIVERSAL 16] |
| 1639 |
constructed; length = 18 |
| 1640 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1641 |
primitive; length = 3 |
| 1642 |
{ 2 5 29 32 } -- id-ce-certificatePolicies |
| 1643 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] |
| 1644 |
primitive; length = 11 |
| 1645 |
0x3009300706052b24080101 |
| 1646 |
Extension SEQUENCE: tag = [UNIVERSAL 16] |
| 1647 |
constructed; length = 31 |
| 1648 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1649 |
primitive; length = 3 |
| 1650 |
{ 2 5 29 35 } -- id-ce-authorityKeyIdentifier |
| 1651 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] |
| 1652 |
primitive; length = 24 |
| 1653 |
0x30168014000102030405060708090a0b0c0d0e0ffedcba98 |
| 1654 |
Extension SEQUENCE: tag = [UNIVERSAL 16] |
| 1655 |
constructed; length = 57 |
| 1656 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] |
| 1657 |
primitive; length = 8 |
| 1658 |
{ 1 3 6 1 5 5 7 1 3 } -- id-pe-qcStatements |
| 1659 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] |
| 1660 |
primitive; length = 45 |
| 1661 |
0x302b302906082b06010505070b02301d301b81196d756e696... |
| 1662 |
|
| 1663 |
<span class="h3"><a class="selflink" id="appendix-C.3" href="#appendix-C.3">C.3</a> DER-encoding</span> |
| 1664 |
|
| 1665 |
This section contains the full, DER-encoded certificate, in hex. |
| 1666 |
|
| 1667 |
<span class="h2"><a class="selflink" id="section-30820310" href="#section-30820310">30820310</a> 30820279 A0030201 02020449 9602D230 0D06092A 864886F7 0D010105</span> |
| 1668 |
<span class="h2"><a class="selflink" id="section-05003048" href="#section-05003048">05003048</a> 310B3009 06035504 06130244 45313930 37060355 040A0C30 474D4420</span> |
| 1669 |
2D20466F 72736368 756E6773 7A656E74 72756D20 496E666F 726D6174 696F6E73 |
| 1670 |
<span class="h2"><a class="selflink" id="section-74656368" href="#section-74656368">74656368</a> 6E696B20 476D6248 301E170D 30343032 30313130 30303030 5A170D30</span> |
| 1671 |
<span class="h2"><a class="selflink" id="section-38303230" href="#section-38303230">38303230</a> 31313030 3030305A 3065310B 30090603 55040613 02444531 37303506</span> |
| 1672 |
0355040A 0C2E474D 4420466F 72736368 756E6773 7A656E74 72756D20 496E666F |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Santesson, et al. Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
726D6174 696F6E73 74656368 6E696B20 476D6248 311D300C 06035504 2A0C0550 |
| 1682 |
<span class="h2"><a class="selflink" id="section-65747261" href="#section-65747261">65747261</a> 300D0603 5504040C 06426172 7A696E30 819F300D 06092A86 4886F70D</span> |
| 1683 |
<span class="h2"><a class="selflink" id="section-01010105" href="#section-01010105">01010105</a> 0003818D 00308189 02818100 DCE74CD5 A1D55AEB 01CF5ECC 20F3C3FC</span> |
| 1684 |
A787CFCB 571A21AA 8A20AD5D FF015130 DE724E5E D3F95392 E7BB16C4 A71D0F31 |
| 1685 |
B3A9926A 8F08EA00 FDC3A8F2 BB016DEC A3B9411B A2599A2A 8CB655C6 DFEA25BF |
| 1686 |
EDDC73B5 94FAA0EF E595C612 A6AE5B8C 7F0CA19C EC4FE7AB 60546768 4BB2387D |
| 1687 |
5F2F7EBD BC3EF0A6 04F6B404 01176925 02030100 01A381E9 3081E630 64060355 |
| 1688 |
1D09045D 305B3010 06082B06 01050507 09043104 13024445 300F0608 2B060105 |
| 1689 |
<span class="h2"><a class="selflink" id="section-05070903" href="#section-05070903">05070903</a> 31031301 46301D06 082B0601 05050709 01311118 0F313937 31313031</span> |
| 1690 |
<span class="h2"><a class="selflink" id="section-34313230" href="#section-34313230">34313230</a> 3030305A 30170608 2B060105 05070902 310B0C09 4461726D 73746164</span> |
| 1691 |
74300E06 03551D0F 0101FF04 04030206 40301206 03551D20 040B3009 30070605 |
| 1692 |
2B240801 01301F06 03551D23 04183016 80140001 02030405 06070809 0A0B0C0D |
| 1693 |
0E0FFEDC BA983039 06082B06 01050507 0103042D 302B3029 06082B06 01050507 |
| 1694 |
0B02301D 301B8119 6D756E69 63697061 6C697479 40646172 6D737461 64742E64 |
| 1695 |
65300D06 092A8648 86F70D01 01050500 03818100 8F8C80BB B2D86B75 F4E21F82 |
| 1696 |
EFE0F20F 6C558890 A6E73118 8359B9C7 8CE71C92 0C66C600 53FBC924 825090F2 |
| 1697 |
95B08826 EAF3FF1F 5917C80B B4836129 CFE5563E 78592B5B B0F9ACB5 2915F0F2 |
| 1698 |
BC36991F 21436520 E9064761 D932D871 F71FFEBD AD648FA7 CF3C1BC0 96F112D4 |
| 1699 |
B882B39F E1A16A90 AE1A80B8 A9676518 B5AA7E97 |
| 1700 |
|
| 1701 |
<span class="h3"><a class="selflink" id="appendix-C.4" href="#appendix-C.4">C.4</a>. CA's Public RSA Key</span> |
| 1702 |
|
| 1703 |
This section contains the DER-encoded public RSA key of the CA who |
| 1704 |
signed the example certificate. It is included with the purpose of |
| 1705 |
simplifying verifications of the example certificate. |
| 1706 |
|
| 1707 |
30818902818100c88f4bdb66f713ba3dd7a9069880e888d4321acb53cda7fcdf |
| 1708 |
da89b834e25430b956d46a438baa6798035af30db378424e00a8296b012b1b24 |
| 1709 |
f9cf0b3f83be116cd8a36957dc3f54cbd7c58a10c380b3dfa15bd2922ea8660f |
| 1710 |
96e1603d81357c0442ad607c5161d083d919fd5307c1c3fa6dfead0e6410999e |
| 1711 |
8b8a8411d525dd0203010001 |
| 1712 |
|
| 1713 |
References |
| 1714 |
|
| 1715 |
Normative References |
| 1716 |
|
| 1717 |
[<a id="ref-RFC 2119">RFC 2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1718 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1719 |
|
| 1720 |
[<a id="ref-RFC 2247">RFC 2247</a>] Kille, S., Wahl, M., Grimstad, A., Huber R. and S. |
| 1721 |
Sataluri, "Using Domains in LDAP/X.500 Distinguished |
| 1722 |
Names", <a href="./rfc2247">RFC 2247</a>, January 1998. |
| 1723 |
|
| 1724 |
[<a id="ref-RFC 2818">RFC 2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000. |
| 1725 |
|
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Santesson, et al. Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
[<a id="ref-RFC 2985">RFC 2985</a>] Nystrom, M. and B. Kaliski, "PKCS #9: Selected Object |
| 1738 |
Classes and Attribute Types Version 2.0", <a href="./rfc2985">RFC 2985</a>, |
| 1739 |
November 2000. |
| 1740 |
|
| 1741 |
[<a id="ref-RFC 3280">RFC 3280</a>] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet |
| 1742 |
X.509 Public Key Infrastructure: Certificate and |
| 1743 |
Certificate Revocation List (CRL) Profile", <a href="./rfc3280">RFC 3280</a>, |
| 1744 |
April 2002. |
| 1745 |
|
| 1746 |
[<a id="ref-X.509">X.509</a>] ITU-T Recommendation X.509 (2000) | ISO/IEC 9594-8:2001, |
| 1747 |
Information technology - Open Systems Interconnection - |
| 1748 |
The Directory: Public-key and attribute certificate |
| 1749 |
frameworks |
| 1750 |
|
| 1751 |
[<a id="ref-X.520">X.520</a>] ITU-T Recommendation X.520 (2001) | ISO/IEC 9594-6:2001, |
| 1752 |
Information Technology - Open Systems Interconnection - |
| 1753 |
The Directory: Selected Attribute Types, 2001. |
| 1754 |
|
| 1755 |
[<a id="ref-X.680">X.680</a>] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002), |
| 1756 |
Information Technology - Abstract Syntax Notation One, |
| 1757 |
2002. |
| 1758 |
|
| 1759 |
[ISO 3166] ISO 3166-1:1997, Codes for the representation of names of |
| 1760 |
countries, 1997. |
| 1761 |
|
| 1762 |
[HTTP/1.1] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., |
| 1763 |
Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext |
| 1764 |
Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999. |
| 1765 |
|
| 1766 |
Informative References |
| 1767 |
|
| 1768 |
[<a id="ref-X.501">X.501</a>] ITU-T recommendation X.501 (2001) | ISO/IEC 9594-2:2001, |
| 1769 |
Information Technology - Open Systems Interconnection - |
| 1770 |
The Directory: Models, 2001. |
| 1771 |
|
| 1772 |
[<a id="ref-EU-ESDIR">EU-ESDIR</a>] Directive 1999/93/EC of the European Parliament and of the |
| 1773 |
Council of 13 December 1999 on a Community framework for |
| 1774 |
electronic signatures, 1999. |
| 1775 |
|
| 1776 |
[<a id="ref-RFC 2253">RFC 2253</a>] Wahl, M., Kille, S. and T. Howes, "Lightweight Directory |
| 1777 |
Access Protocol (v3): UTF-8 String Representation of |
| 1778 |
Distinguished Names", <a href="./rfc2253">RFC 2253</a>, December 1997. |
| 1779 |
|
| 1780 |
|
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Santesson, et al. Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
Authors' Addresses |
| 1794 |
|
| 1795 |
Stefan Santesson |
| 1796 |
Microsoft Denmark |
| 1797 |
Tuborg Boulevard 12 |
| 1798 |
DK-2900 Hellerup |
| 1799 |
Denmark |
| 1800 |
|
| 1801 |
EMail: [email protected] |
| 1802 |
|
| 1803 |
|
| 1804 |
Tim Polk |
| 1805 |
NIST |
| 1806 |
Building 820, Room 426 |
| 1807 |
Gaithersburg, MD 20899, USA |
| 1808 |
|
| 1809 |
EMail: [email protected] |
| 1810 |
|
| 1811 |
|
| 1812 |
Magnus Nystrom |
| 1813 |
RSA Security |
| 1814 |
Box 10704 |
| 1815 |
S-121 29 Stockholm |
| 1816 |
Sweden |
| 1817 |
|
| 1818 |
EMail: [email protected] |
| 1819 |
|
| 1820 |
|
| 1821 |
|
| 1822 |
|
| 1823 |
|
| 1824 |
|
| 1825 |
|
| 1826 |
|
| 1827 |
|
| 1828 |
|
| 1829 |
|
| 1830 |
|
| 1831 |
|
| 1832 |
|
| 1833 |
|
| 1834 |
|
| 1835 |
|
| 1836 |
|
| 1837 |
|
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Santesson, et al. Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc3739">RFC 3739</a> Qualified Certificates Profile March 2004</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
Full Copyright Statement |
| 1850 |
|
| 1851 |
Copyright (C) The Internet Society (2004). This document is subject |
| 1852 |
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and |
| 1853 |
except as set forth therein, the authors retain all their rights. |
| 1854 |
|
| 1855 |
This document and the information contained herein are provided on an |
| 1856 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE |
| 1857 |
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE |
| 1858 |
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR |
| 1859 |
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 1860 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1861 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1862 |
|
| 1863 |
Intellectual Property |
| 1864 |
|
| 1865 |
The IETF takes no position regarding the validity or scope of any |
| 1866 |
Intellectual Property Rights or other rights that might be claimed |
| 1867 |
to pertain to the implementation or use of the technology |
| 1868 |
described in this document or the extent to which any license |
| 1869 |
under such rights might or might not be available; nor does it |
| 1870 |
represent that it has made any independent effort to identify any |
| 1871 |
such rights. Information on the procedures with respect to |
| 1872 |
rights in RFC documents can be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 1873 |
|
| 1874 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1875 |
assurances of licenses to be made available, or the result of an |
| 1876 |
attempt made to obtain a general license or permission for the use |
| 1877 |
of such proprietary rights by implementers or users of this |
| 1878 |
specification can be obtained from the IETF on-line IPR repository |
| 1879 |
at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1880 |
|
| 1881 |
The IETF invites any interested party to bring to its attention |
| 1882 |
any copyrights, patents or patent applications, or other |
| 1883 |
proprietary rights that may cover technology that may be required |
| 1884 |
to implement this standard. Please address the information to the |
| 1885 |
IETF at [email protected]. |
| 1886 |
|
| 1887 |
Acknowledgement |
| 1888 |
|
| 1889 |
Funding for the RFC Editor function is currently provided by the |
| 1890 |
Internet Society. |
| 1891 |
|
| 1892 |
|
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
Santesson, et al. Standards Track [Page 34] |
| 1901 |
</pre> |