| 1 |
<pre>Network Working Group S. Santesson |
| 2 |
Request for Comments: 3039 AddTrust |
| 3 |
Category: Standards Track W. Polk |
| 4 |
NIST |
| 5 |
P. Barzin |
| 6 |
SECUDE |
| 7 |
M. Nystrom |
| 8 |
RSA Security |
| 9 |
January 2001 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">Internet X.509 Public Key Infrastructure</span> |
| 13 |
<span class="h1">Qualified Certificates Profile</span> |
| 14 |
|
| 15 |
Status of this Memo |
| 16 |
|
| 17 |
This document specifies an Internet standards track protocol for the |
| 18 |
Internet community, and requests discussion and suggestions for |
| 19 |
improvements. Please refer to the current edition of the "Internet |
| 20 |
Official Protocol Standards" (STD 1) for the standardization state |
| 21 |
and status of this protocol. Distribution of this memo is unlimited. |
| 22 |
|
| 23 |
Copyright Notice |
| 24 |
|
| 25 |
Copyright (C) The Internet Society (2001). All Rights Reserved. |
| 26 |
|
| 27 |
Abstract |
| 28 |
|
| 29 |
This document forms a certificate profile for Qualified Certificates, |
| 30 |
based on <a href="./rfc2459">RFC 2459</a>, for use in the Internet. The term Qualified |
| 31 |
Certificate is used to describe a certificate with a certain |
| 32 |
qualified status within applicable governing law. Further, Qualified |
| 33 |
Certificates are issued exclusively to physical persons. |
| 34 |
|
| 35 |
The goal of this document is to define a general syntax independent |
| 36 |
of local legal requirements. The profile is however designed to |
| 37 |
allow further profiling in order to meet specific local needs. |
| 38 |
|
| 39 |
It is important to note that the profile does not define any legal |
| 40 |
requirements for Qualified Certificates. |
| 41 |
|
| 42 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 43 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 44 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a>. |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</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-2">2</a> Requirements and Assumptions ................................ <a href="#page-3">3</a> |
| 61 |
<a href="#section-2.1">2.1</a> Properties ................................................ <a href="#page-4">4</a> |
| 62 |
<a href="#section-2.2">2.2</a> Statement of Purpose ...................................... <a href="#page-5">5</a> |
| 63 |
<a href="#section-2.3">2.3</a> Policy Issues ............................................. <a href="#page-5">5</a> |
| 64 |
<a href="#section-2.4">2.4</a> Uniqueness of names ....................................... <a href="#page-5">5</a> |
| 65 |
<a href="#section-3">3</a> Certificate and Certificate Extensions Profile .............. <a href="#page-6">6</a> |
| 66 |
<a href="#section-3.1">3.1</a> Basic Certificate Fields .................................. <a href="#page-6">6</a> |
| 67 |
<a href="#section-3.1.1">3.1.1</a> Issuer .................................................. <a href="#page-6">6</a> |
| 68 |
<a href="#section-3.1.2">3.1.2</a> Subject ................................................. <a href="#page-6">6</a> |
| 69 |
<a href="#section-3.2">3.2</a> Certificate Extensions .................................... <a href="#page-9">9</a> |
| 70 |
<a href="#section-3.2.1">3.2.1</a> Subject Directory Attributes ............................ <a href="#page-9">9</a> |
| 71 |
<a href="#section-3.2.2">3.2.2</a> Certificate Policies .................................... <a href="#page-10">10</a> |
| 72 |
<a href="#section-3.2.3">3.2.3</a> Key Usage ............................................... <a href="#page-10">10</a> |
| 73 |
<a href="#section-3.2.4">3.2.4</a> Biometric Information ................................... <a href="#page-11">11</a> |
| 74 |
<a href="#section-3.2.5">3.2.5</a> Qualified Certificate Statements ........................ <a href="#page-12">12</a> |
| 75 |
<a href="#section-4">4</a> Security Considerations ..................................... <a href="#page-14">14</a> |
| 76 |
<a href="#section-5">5</a> References .................................................. <a href="#page-15">15</a> |
| 77 |
<a href="#section-6">6</a> Intellectual Property Rights ................................ <a href="#page-16">16</a> |
| 78 |
<a href="#appendix-A">A</a> ASN.1 definitions ........................................... <a href="#page-17">17</a> |
| 79 |
<a href="#appendix-A.1">A.1</a> 1988 ASN.1 Module ......................................... <a href="#page-17">17</a> |
| 80 |
<a href="#appendix-A.2">A.2</a> 1993 ASN.1 Module ......................................... <a href="#page-19">19</a> |
| 81 |
<a href="#appendix-B">B</a> A Note on Attributes ........................................ <a href="#page-24">24</a> |
| 82 |
<a href="#appendix-C">C</a>. Example Certificate ........................................ <a href="#page-24">24</a> |
| 83 |
<a href="#appendix-C.1">C.1</a> ASN.1 Structure ........................................... <a href="#page-25">25</a> |
| 84 |
<a href="#appendix-C.1.1">C.1.1</a> Extensions ............................................... <a href="#page-25">25</a> |
| 85 |
<a href="#appendix-C.1.2">C.1.2</a> The certificate .......................................... <a href="#page-27">27</a> |
| 86 |
<a href="#appendix-C.2">C.2</a> ASN.1 Dump ................................................ <a href="#page-29">29</a> |
| 87 |
<a href="#appendix-C.3">C.3</a> DER-encoding .............................................. <a href="#page-32">32</a> |
| 88 |
<a href="#appendix-C.4">C.4</a> CA's public key ........................................... <a href="#page-33">33</a> |
| 89 |
Authors' Addresses ............................................. <a href="#page-34">34</a> |
| 90 |
Full Copyright Statement ....................................... <a href="#page-35">35</a> |
| 91 |
|
| 92 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Introduction</span> |
| 93 |
|
| 94 |
This specification is one part of a family of standards for the X.509 |
| 95 |
Public Key Infrastructure (PKI) for the Internet. It is based on <a href="./rfc2459">RFC</a> |
| 96 |
<a href="./rfc2459">2459</a>, which defines underlying certificate formats and semantics |
| 97 |
needed for a full implementation of this standard. |
| 98 |
|
| 99 |
The standard profiles the format for a specific type of certificates |
| 100 |
named Qualified Certificates. The term Qualified Certificates and |
| 101 |
the assumptions that affects the scope of this document are discussed |
| 102 |
in <a href="#section-2">Section 2</a>. |
| 103 |
|
| 104 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 111 |
|
| 112 |
|
| 113 |
<a href="#section-3">Section 3</a> defines requirements on information content in Qualified |
| 114 |
Certificates. This profile addresses two fields in the basic |
| 115 |
certificate as well as five certificate extensions. The certificate |
| 116 |
fields are the subject and issuer fields. The certificate extensions |
| 117 |
are subject directory attributes, certificate policies, key usage, a |
| 118 |
private extension for storage of biometric data and a private |
| 119 |
extension for storage of statements related to Qualified |
| 120 |
Certificates. The private extensions are presented in the 1993 |
| 121 |
Abstract Syntax Notation One (ASN.1), but in conformance with <a href="./rfc2459">RFC</a> |
| 122 |
<a href="./rfc2459">2459</a> the 1988 ASN.1 module in <a href="#appendix-A">Appendix A</a> contains all normative |
| 123 |
definitions (the 1993 module in <a href="#appendix-A">Appendix A</a> is 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 Qualified Certificates are |
| 127 |
assumed to be utilized. <a href="#section-5">Section 5</a> contains the references. |
| 128 |
|
| 129 |
<a href="#appendix-A">Appendix A</a> contains all relevant ASN.1 [<a href="#ref-X.680">X.680</a>] structures that are |
| 130 |
not already defined in <a href="./rfc2459">RFC 2459</a>. <a href="#appendix-B">Appendix B</a> contains a note on |
| 131 |
attributes. <a href="#appendix-C">Appendix C</a> contains an example certificate. <a href="#appendix-D">Appendix D</a> |
| 132 |
contains authors' addresses and <a href="#appendix-E">Appendix E</a> contains the IETF |
| 133 |
Copyright Statement. |
| 134 |
|
| 135 |
It should be noted that this specification does not define the |
| 136 |
specific semantics of Qualified Certificates, and does not define the |
| 137 |
policies that should be used with them. That is, this document |
| 138 |
defines what information should go into Qualified Certificates, but |
| 139 |
not what that information means. A system that uses Qualified |
| 140 |
Certificates must define its own semantics for the information in |
| 141 |
Qualified Certificates. It is expected that laws and corporate |
| 142 |
policies will make these definitions. |
| 143 |
|
| 144 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Requirements and Assumptions</span> |
| 145 |
|
| 146 |
The term "Qualified Certificate" has been used by the European |
| 147 |
Commission to describe a certain type of certificates with specific |
| 148 |
relevance for European legislation. This specification is intended |
| 149 |
to support this class of certificates, but its scope is not limited |
| 150 |
to this application. |
| 151 |
|
| 152 |
Within this standard the term "Qualified Certificate" is used more |
| 153 |
generally, describing the format for a certificate whose primary |
| 154 |
purpose is identifying a person with high level of assurance in |
| 155 |
public non-repudiation services. The actual mechanisms that will |
| 156 |
decide whether a certificate should or should not be considered to be |
| 157 |
a "Qualified Certificate" in regard to any legislation are outside |
| 158 |
the scope of this standard. |
| 159 |
|
| 160 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 167 |
|
| 168 |
|
| 169 |
Harmonization in the field of Qualified Certificates is essential |
| 170 |
within several aspects that fall outside the scope of <a href="./rfc2459">RFC 2459</a>. The |
| 171 |
most important aspects that affect the scope of this specification |
| 172 |
are: |
| 173 |
|
| 174 |
- Definition of names and identity information in order to identify |
| 175 |
the associated subject in a uniform way. |
| 176 |
|
| 177 |
- Definition of information which identifies the CA and the |
| 178 |
jurisdiction under which the CA operates when issuing a particular |
| 179 |
certificate. |
| 180 |
|
| 181 |
- Definition of key usage extension usage for Qualified |
| 182 |
Certificates. |
| 183 |
|
| 184 |
- Definition of information structure for storage of biometric |
| 185 |
information. |
| 186 |
|
| 187 |
- Definition of a standardized way to store predefined statements |
| 188 |
with relevance for Qualified Certificates. |
| 189 |
|
| 190 |
- Requirements for critical extensions. |
| 191 |
|
| 192 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Properties</span> |
| 193 |
|
| 194 |
A Qualified Certificate as defined in this standard is assumed to |
| 195 |
have the following properties: |
| 196 |
|
| 197 |
- The certificate is issued by a CA that makes a public statement |
| 198 |
that the certificate serves the purpose of a Qualified |
| 199 |
Certificate, as discussed in <a href="#section-2.2">Section 2.2</a> |
| 200 |
|
| 201 |
- The certificate indicates a certificate policy consistent with |
| 202 |
liabilities, practices and procedures undertaken by the CA, as |
| 203 |
discussed in 2.3 |
| 204 |
|
| 205 |
- The certificate is issued to a natural person (living human |
| 206 |
being). |
| 207 |
|
| 208 |
- The certificate contains an identity based on a pseudonym or a |
| 209 |
real name of the subject. |
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Statement of Purpose</span> |
| 226 |
|
| 227 |
For a certificate to serve the purpose of being a Qualified |
| 228 |
Certificate, this profile assumes that the CA will have to include in |
| 229 |
the certificate information that explicitly defines this intent. |
| 230 |
|
| 231 |
The function of this information is thus to assist any concerned |
| 232 |
entity in evaluating the risk associated with creating or accepting |
| 233 |
signatures that are based on a Qualified Certificate. |
| 234 |
|
| 235 |
This profile defines two complementary ways to include this |
| 236 |
information: |
| 237 |
|
| 238 |
- As information defined by a certificate policy included in the |
| 239 |
certificate policies extension, and |
| 240 |
|
| 241 |
- As a statement included in the Qualified Certificates Statements |
| 242 |
extension. |
| 243 |
|
| 244 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Policy Issues</span> |
| 245 |
|
| 246 |
Certain policy aspects define the context in which this profile is to |
| 247 |
be understood and used. It is however outside the scope of this |
| 248 |
profile to specify any policies or legal aspects that will govern |
| 249 |
services that issue or utilize certificates according to this |
| 250 |
profile. |
| 251 |
|
| 252 |
It is however assumed that the issuing CA will undertake to follow a |
| 253 |
publicly available certificate policy that is consistent with its |
| 254 |
liabilities, practices and procedures. |
| 255 |
|
| 256 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Uniqueness of names</span> |
| 257 |
|
| 258 |
Distinguished name is originally defined in X.501 [<a href="#ref-X.501">X.501</a>] as a |
| 259 |
representation of a directory name, defined as a construct that |
| 260 |
identifies a particular object from among the set of all objects. An |
| 261 |
object can be assigned a distinguished name without being represented |
| 262 |
by an entry in the Directory, but this name is then the name its |
| 263 |
object entry could have had if it were represented in the Directory. |
| 264 |
In the context of qualified certificates, a distinguished name |
| 265 |
denotes a set of attribute values [<a href="#ref-X.501">X.501</a>] which forms a name that is |
| 266 |
unambiguous within a certain domain that forms either a real or a |
| 267 |
virtual DIT (Directory Information Tree)[<a href="#ref-X.501">X.501</a>]. In the case of |
| 268 |
subject names the domain is assumed to be at least the issuing domain |
| 269 |
of the CA. The distinguished name MUST be unique for each subject |
| 270 |
entity certified by the one CA as defined by the issuer name field, |
| 271 |
during the whole life time of the CA. |
| 272 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Certificate and Certificate Extensions Profile</span> |
| 282 |
|
| 283 |
This section defines a profile for Qualified Certificates. The |
| 284 |
profile is based on the Internet certificate profile <a href="./rfc2459">RFC 2459</a> which |
| 285 |
in turn is based on the X.509 version 3 format. For full |
| 286 |
implementation of this section implementers are REQUIRED to consult |
| 287 |
the underlying formats and semantics defined in <a href="./rfc2459">RFC 2459</a>. |
| 288 |
|
| 289 |
ASN.1 definitions relevant for this section that are not supplied by |
| 290 |
<a href="./rfc2459">RFC 2459</a> are supplied in <a href="#appendix-A">Appendix A</a>. |
| 291 |
|
| 292 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Basic Certificate Fields</span> |
| 293 |
|
| 294 |
This specification provides additional details regarding the contents |
| 295 |
of two fields in the basic certificate. These fields are the issuer |
| 296 |
and subject fields. |
| 297 |
|
| 298 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a> Issuer</span> |
| 299 |
|
| 300 |
The issuer field SHALL identify the organization responsible for |
| 301 |
issuing the certificate. The name SHOULD be an officially registered |
| 302 |
name of the organization. |
| 303 |
|
| 304 |
The identity of the issuer SHALL be specified using an appropriate |
| 305 |
subset of the following attributes: |
| 306 |
|
| 307 |
domainComponent; |
| 308 |
countryName; |
| 309 |
stateOrProvinceName; |
| 310 |
organizationName; |
| 311 |
localityName; and |
| 312 |
serialNumber. |
| 313 |
|
| 314 |
Additional attributes MAY be present but they SHOULD NOT be necessary |
| 315 |
to identify the issuing organization. |
| 316 |
|
| 317 |
Attributes present in the issuer field SHOULD be consistent with the |
| 318 |
laws under which the issuer operates. |
| 319 |
|
| 320 |
A relying party MAY have to consult associated certificate policies |
| 321 |
and/or the issuer's CPS, in order to determine the semantics of name |
| 322 |
fields and the laws under which the issuer operates. |
| 323 |
|
| 324 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a> Subject</span> |
| 325 |
|
| 326 |
The subject field of a certificate compliant with this profile SHALL |
| 327 |
contain a distinguished name of the subject (see 2.4 for definition |
| 328 |
of distinguished name). |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 335 |
|
| 336 |
|
| 337 |
The subject field SHALL contain an appropriate subset of the |
| 338 |
following attributes: |
| 339 |
|
| 340 |
countryName; |
| 341 |
commonName; |
| 342 |
surname; |
| 343 |
givenName; |
| 344 |
pseudonym; |
| 345 |
serialNumber; |
| 346 |
organizationName; |
| 347 |
organizationalUnitName; |
| 348 |
stateOrProvinceName |
| 349 |
localityName and |
| 350 |
postalAddress. |
| 351 |
|
| 352 |
Other attributes may be present but MUST NOT be necessary to |
| 353 |
distinguish the subject name from other subject names within the |
| 354 |
issuer domain. |
| 355 |
|
| 356 |
Of these attributes, the subject field SHALL include at least one of |
| 357 |
the following: |
| 358 |
|
| 359 |
Choice I: commonName |
| 360 |
Choice II: givenName |
| 361 |
Choice III: pseudonym |
| 362 |
|
| 363 |
The countryName attribute value specifies a general context in which |
| 364 |
other attributes are to be understood. The country attribute does |
| 365 |
not necessarily indicate the subject's country of citizenship or |
| 366 |
country of residence, nor does it have to indicate the country of |
| 367 |
issuance. |
| 368 |
|
| 369 |
Note: Many X.500 implementations require the presence of countryName |
| 370 |
in the DIT. In cases where the subject name, as specified in the |
| 371 |
subject field, specifies a public X.500 directory entry, the |
| 372 |
countryName attribute SHOULD always be present. |
| 373 |
|
| 374 |
The commonName attribute value SHALL, when present, contain a name of |
| 375 |
the subject. This MAY be in the subject's preferred presentation |
| 376 |
format, or a format preferred by the CA, or some other format. |
| 377 |
Pseudonyms, nicknames and names with spelling other than defined by |
| 378 |
the registered name MAY be used. To understand the nature of the |
| 379 |
name presented in commonName, complying applications MAY have to |
| 380 |
examine present values of the givenName and surname attributes, or |
| 381 |
the pseudonym attribute. |
| 382 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 391 |
|
| 392 |
|
| 393 |
Note: Many client implementations presuppose the presence of the |
| 394 |
commonName attribute value in the subject field and use this value to |
| 395 |
display the subject's name regardless of present givenName, surname |
| 396 |
or pseudonym attribute values. |
| 397 |
|
| 398 |
The surname and givenName attribute types SHALL, if present, contain |
| 399 |
the registered name of the subject, in accordance with the laws under |
| 400 |
which the CA prepares the certificate. These attributes SHALL be |
| 401 |
used in the subject field if the commonName attribute is not present. |
| 402 |
In cases where the subject only has a single name registered, the |
| 403 |
givenName attribute SHALL be used and the surname attribute SHALL be |
| 404 |
omitted. |
| 405 |
|
| 406 |
The pseudonym attribute type SHALL, if present, contain a pseudonym |
| 407 |
of the subject. Use of the pseudonym attribute MUST NOT be combined |
| 408 |
with use of any of the attributes surname and/or givenName. |
| 409 |
|
| 410 |
The serialNumber attribute type SHALL, when present, be used to |
| 411 |
differentiate between names where the subject field would otherwise |
| 412 |
be identical. This attribute has no defined semantics beyond |
| 413 |
ensuring uniqueness of subject names. It MAY contain a number or |
| 414 |
code assigned by the CA or an identifier assigned by a government or |
| 415 |
civil authority. It is the CA's responsibility to ensure that the |
| 416 |
serialNumber is sufficient to resolve any subject name collisions. |
| 417 |
|
| 418 |
The organizationName and the organizationalUnitName attribute types |
| 419 |
SHALL, when present, be used to store the name and relevant |
| 420 |
information of an organization with which the subject is associated. |
| 421 |
The type of association between the organization and the subject is |
| 422 |
beyond the scope of this document. |
| 423 |
|
| 424 |
The postalAddress, the stateOrProvinceName and the localityName |
| 425 |
attribute types SHALL, when present, be used to store address and |
| 426 |
geographical information with which the subject is associated. If an |
| 427 |
organizationName value also is present then the postalAddress, |
| 428 |
stateOrProvinceName and localityName attribute values SHALL be |
| 429 |
associated with the specified organization. The type of association |
| 430 |
between the postalAddress, stateOrProvinceName and the localityName |
| 431 |
and either the subject or the organizationName is beyond the scope of |
| 432 |
this document. |
| 433 |
|
| 434 |
Compliant implementations SHALL be able to interpret the attributes |
| 435 |
named in this section. |
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Certificate Extensions</span> |
| 450 |
|
| 451 |
This specification provides additional details regarding the contents |
| 452 |
of five certificate extensions. These extensions are the subject |
| 453 |
directory attributes, certificate policies, key usage, private |
| 454 |
extension for biometric information and private extension for |
| 455 |
Qualified Certificate statements. |
| 456 |
|
| 457 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a> Subject Directory Attributes</span> |
| 458 |
|
| 459 |
The subjectDirectoryAttributes extension MAY contain additional |
| 460 |
attributes, associated with the subject, as complement to present |
| 461 |
information in the subject field and the subject alternative name |
| 462 |
extension. |
| 463 |
|
| 464 |
Attributes suitable for storage in this extension are attributes, |
| 465 |
which are not part of the subject's distinguished name, but which MAY |
| 466 |
still be useful for other purposes (e.g., authorization). |
| 467 |
|
| 468 |
This extension MUST NOT be marked critical. |
| 469 |
|
| 470 |
Compliant implementations SHALL be able to interpret the following |
| 471 |
attributes: |
| 472 |
|
| 473 |
title; |
| 474 |
dateOfBirth; |
| 475 |
placeOfBirth; |
| 476 |
gender; |
| 477 |
countryOfCitizenship; and |
| 478 |
countryOfResidence. |
| 479 |
|
| 480 |
Other attributes MAY be included according to local definitions. |
| 481 |
|
| 482 |
The title attribute type SHALL, when present, be used to store a |
| 483 |
designated position or function of the subject within the |
| 484 |
organization specified by present organizational attributes in the |
| 485 |
subject field. The association between the title, the subject and |
| 486 |
the organization is beyond the scope of this document. |
| 487 |
|
| 488 |
The dateOfBirth attribute SHALL, when present, contain the value of |
| 489 |
the date of birth of the subject. The manner in which the date of |
| 490 |
birth is associated with the subject is outside the scope of this |
| 491 |
document. |
| 492 |
|
| 493 |
The placeOfBirth attribute SHALL, when present, contain the value of |
| 494 |
the place of birth of the subject. The manner in which the place of |
| 495 |
birth is associated with the subject is outside the scope of this |
| 496 |
document. |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 503 |
|
| 504 |
|
| 505 |
The gender attribute SHALL, when present, contain the value of the |
| 506 |
gender of the subject. For females the value "F" (or "f") and for |
| 507 |
males the value "M" (or "m") have to be used. The manner in which |
| 508 |
the gender is associated with the subject is outside the scope of |
| 509 |
this document. |
| 510 |
|
| 511 |
The countryOfCitizenship attribute SHALL, when present, contain the |
| 512 |
identifier of at least one of the subject's claimed countries of |
| 513 |
citizenship at the time that the certificate was issued. If the |
| 514 |
subject is a citizen of more than one country, more than one country |
| 515 |
MAY be present. Determination of citizenship is a matter of law and |
| 516 |
is outside the scope of this document. |
| 517 |
|
| 518 |
The countryOfResidence attribute SHALL, when present, contain the |
| 519 |
value of at least one country in which the subject is resident. If |
| 520 |
the subject is a resident of more than one country, more than one |
| 521 |
country MAY be present. Determination of residence is a matter of |
| 522 |
law and is outside the scope of this document. |
| 523 |
|
| 524 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a> Certificate Policies</span> |
| 525 |
|
| 526 |
The certificate policies extension SHALL contain the identifier of at |
| 527 |
least one certificate policy which reflects the practices and |
| 528 |
procedures undertaken by the CA. The certificate policy extension |
| 529 |
MAY be marked critical. |
| 530 |
|
| 531 |
Information provided by the issuer stating the purpose of the |
| 532 |
certificate as discussed in <a href="#section-2.2">Section 2.2</a> SHOULD be evident through |
| 533 |
indicated policies. |
| 534 |
|
| 535 |
The certificate policies extension SHOULD include all policy |
| 536 |
information needed for validation of the certificate. If policy |
| 537 |
information is included in the QCStatements extension (see 3.2.5), |
| 538 |
then this information SHOULD also be defined by indicated policies. |
| 539 |
|
| 540 |
Certificate policies MAY be combined with any qualifier defined in |
| 541 |
<a href="./rfc2459">RFC 2459</a>. |
| 542 |
|
| 543 |
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a> Key Usage</span> |
| 544 |
|
| 545 |
The key usage extension SHALL be present. If the key usage |
| 546 |
nonRepudiation bit is asserted then it SHOULD NOT be combined with |
| 547 |
any other key usage , i.e., if set, the key usage non-repudiation |
| 548 |
SHOULD be set exclusively. |
| 549 |
|
| 550 |
The key usage extension MAY be marked critical. |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a> Biometric Information</span> |
| 562 |
|
| 563 |
This section defines an extension for storage of biometric |
| 564 |
information. Biometric information is stored in the form of a hash |
| 565 |
of a biometric template. |
| 566 |
|
| 567 |
The purpose of this extension is to provide means for authentication |
| 568 |
of biometric information. The biometric information that corresponds |
| 569 |
to the stored hash is not stored in this extension, but the extension |
| 570 |
MAY include an URI pointing to a location where this information can |
| 571 |
be obtained. If included, this URI does not imply that this is the |
| 572 |
only way to access this information. |
| 573 |
|
| 574 |
It is RECOMMENDED that biometric information in this extension is |
| 575 |
limited to information types suitable for human verification, i.e., |
| 576 |
where the decision of whether the information is an accurate |
| 577 |
representation of the subject is naturally performed by a person. |
| 578 |
This implies a usage where the biometric information is represented |
| 579 |
by, for example, a graphical image displayed to the relying party, |
| 580 |
which MAY be used by the relying party to enhance identification of |
| 581 |
the subject. |
| 582 |
|
| 583 |
This extension MUST NOT be marked critical. |
| 584 |
|
| 585 |
biometricInfo EXTENSION ::= { |
| 586 |
SYNTAX BiometricSyntax |
| 587 |
IDENTIFIED BY id-pe-biometricInfo } |
| 588 |
|
| 589 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= {id-pe 2} |
| 590 |
|
| 591 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 592 |
|
| 593 |
BiometricData ::= SEQUENCE { |
| 594 |
typeOfBiometricData TypeOfBiometricData, |
| 595 |
hashAlgorithm AlgorithmIdentifier, |
| 596 |
biometricDataHash OCTET STRING, |
| 597 |
sourceDataUri IA5String OPTIONAL } |
| 598 |
|
| 599 |
TypeOfBiometricData ::= CHOICE { |
| 600 |
predefinedBiometricType PredefinedBiometricType, |
| 601 |
biometricDataID OBJECT IDENTIFIER } |
| 602 |
|
| 603 |
PredefinedBiometricType ::= INTEGER { picture(0), |
| 604 |
handwritten-signature(1)} (picture|handwritten-signature,...) |
| 605 |
|
| 606 |
|
| 607 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 615 |
|
| 616 |
|
| 617 |
The predefined biometric type picture, when present, SHALL identify |
| 618 |
that the source picture is in the form of a displayable graphical |
| 619 |
image of the subject. The hash of the graphical image SHALL only be |
| 620 |
calculated over the image data excluding any labels defining the |
| 621 |
image type. |
| 622 |
|
| 623 |
The predefined biometric type handwritten-signature, when present, |
| 624 |
SHALL identify that the source data is in the form of a displayable |
| 625 |
graphical image of the subject's handwritten signature. The hash of |
| 626 |
the graphical image SHALL only be calculated over the image data |
| 627 |
excluding any labels defining the image type. |
| 628 |
|
| 629 |
<span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a> Qualified Certificate Statements</span> |
| 630 |
|
| 631 |
This section defines an extension for inclusion of defined statements |
| 632 |
related to Qualified Certificates. |
| 633 |
|
| 634 |
A typical statement suitable for inclusion in this extension MAY be a |
| 635 |
statement by the issuer that the certificate is issued as a Qualified |
| 636 |
Certificate in accordance with a particular legal system (as |
| 637 |
discussed in <a href="#section-2.2">Section 2.2</a>). |
| 638 |
|
| 639 |
Other statements suitable for inclusion in this extension MAY be |
| 640 |
statements related to the applicable legal jurisdiction within which |
| 641 |
the certificate is issued. As an example this MAY include a maximum |
| 642 |
reliance limit for the certificate indicating restrictions on CA's |
| 643 |
liability. |
| 644 |
|
| 645 |
Each statement SHALL include an object identifier for the statement |
| 646 |
and MAY also include optional qualifying data contained in the |
| 647 |
statementInfo parameter. |
| 648 |
|
| 649 |
If the statementInfo parameter is included then the object identifier |
| 650 |
of the statement SHALL define the syntax and SHOULD define the |
| 651 |
semantics of this parameter. If the object identifier does not |
| 652 |
define the semantics, a relying party may have to consult a relevant |
| 653 |
certificate policy or CPS to determine the exact semantics. |
| 654 |
|
| 655 |
This extension may be critical or non-critical. If the extension is |
| 656 |
critical, this means that all statements included in the extension |
| 657 |
are regarded as critical. |
| 658 |
|
| 659 |
qcStatements EXTENSION ::= { |
| 660 |
SYNTAX QCStatements |
| 661 |
IDENTIFIED BY id-pe-qcStatements } |
| 662 |
|
| 663 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3 } |
| 664 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 671 |
|
| 672 |
|
| 673 |
QCStatements ::= SEQUENCE OF QCStatement |
| 674 |
|
| 675 |
QCStatement ::= SEQUENCE { |
| 676 |
statementId QC-STATEMENT.&Id({SupportedStatements}), |
| 677 |
statementInfo QC-STATEMENT.&Type |
| 678 |
({SupportedStatements}{@statementId}) OPTIONAL } |
| 679 |
|
| 680 |
SupportedStatements QC-STATEMENT ::= { qcStatement-1,...} |
| 681 |
|
| 682 |
<span class="h5"><a class="selflink" id="section-3.2.5.1" href="#section-3.2.5.1">3.2.5.1</a> Predefined Statements</span> |
| 683 |
|
| 684 |
This profile includes one predefined object identifier (id-qcs- |
| 685 |
pkixQCSyntax-v1), identifying conformance with syntax and semantics |
| 686 |
defined in this profile. This Qualified Certificate profile is |
| 687 |
referred to as version 1. |
| 688 |
|
| 689 |
qcStatement-1 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 690 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v1 } |
| 691 |
-- This statement identifies conformance with syntax and |
| 692 |
-- semantics defined in this Qualified Certificate profile |
| 693 |
-- (Version 1). The SemanticsInformation may optionally contain |
| 694 |
-- additional semantics information as specified. |
| 695 |
|
| 696 |
SemanticsInformation ::= SEQUENCE { |
| 697 |
semanticsIdentifier OBJECT IDENTIFIER OPTIONAL, |
| 698 |
nameRegistrationAuthorities NameRegistrationAuthorities |
| 699 |
OPTIONAL } |
| 700 |
(WITH COMPONENTS {..., semanticsIdentifier PRESENT}| |
| 701 |
WITH COMPONENTS {..., nameRegistrationAuthorities PRESENT}) |
| 702 |
|
| 703 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF |
| 704 |
GeneralName |
| 705 |
|
| 706 |
The SementicsInformation component identified by id-qcs- |
| 707 |
pkixQCSyntax-v1 MAY contain a semantics identifier and MAY identify |
| 708 |
one or more name registration authorities. |
| 709 |
|
| 710 |
The semanticsIdentifier component, if present, SHALL contain an OID, |
| 711 |
defining semantics for attributes and names in basic certificate |
| 712 |
fields and certificate extensions. The OID may define semantics for |
| 713 |
all, or for a subgroup of all present attributes and/or names. |
| 714 |
|
| 715 |
The NameRegistrationAuthorities component, if present, SHALL contain |
| 716 |
a name of one or more name registration authorities, responsible for |
| 717 |
registration of attributes or names associated with the subject. The |
| 718 |
association between an identified name registration authority and |
| 719 |
present attributes MAY be defined by a semantics identifier OID, by a |
| 720 |
certificate policy (or CPS) or some other implicit factors. |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 727 |
|
| 728 |
|
| 729 |
If a value of type SemanticsInformation is present in a QCStatement |
| 730 |
then at least one of the fields semanticsIdentifier and |
| 731 |
nameRegistrationAuthorities must be present, as indicated. |
| 732 |
|
| 733 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Security Considerations</span> |
| 734 |
|
| 735 |
The legal value of a digital signature that is validated with a |
| 736 |
Qualified Certificate will be highly dependent upon the policy |
| 737 |
governing the use of the associated private key. Both the private |
| 738 |
key holder as well as the relying party should make sure that the |
| 739 |
private key is used only with the consent of the legitimate key |
| 740 |
holder. |
| 741 |
|
| 742 |
Since the public keys are for public use with legal implications for |
| 743 |
involved parties, certain conditions should exist before CAs issue |
| 744 |
certificates as Qualified Certificates. The associated private keys |
| 745 |
must be unique for the subject, and must be maintained under the |
| 746 |
subject's sole control. That is, a CA should not issue a qualified |
| 747 |
certificate if the means to use the private key is not protected |
| 748 |
against unintended usage. This implies that the CA have some |
| 749 |
knowledge about the subject's cryptographic module. |
| 750 |
|
| 751 |
The CA must further verify that the public key contained in the |
| 752 |
certificate is legitimately representing the subject. |
| 753 |
|
| 754 |
CAs should not issue CA certificates with policy mapping extensions |
| 755 |
indicating acceptance of another CA's policy unless these conditions |
| 756 |
are met. |
| 757 |
|
| 758 |
Combining the nonRepudiation bit in the keyUsage certificate |
| 759 |
extension with other keyUsage bits may have security implications and |
| 760 |
this specification therefore recommends against such practices. |
| 761 |
|
| 762 |
The ability to compare two qualified certificates to determine if |
| 763 |
they represent the same physical entity is dependent on the semantics |
| 764 |
of the subjects' names. The semantics of a particular attribute may |
| 765 |
be different for different issuers. Comparing names without |
| 766 |
knowledge of the semantics of names in these particular certificates |
| 767 |
may provide misleading results. |
| 768 |
|
| 769 |
This specification is a profile of <a href="./rfc2459">RFC 2459</a>. The security |
| 770 |
considerations section of that document applies to this specification |
| 771 |
as well. |
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> References</span> |
| 786 |
|
| 787 |
[<a id="ref-RFC 2119">RFC 2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 788 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 789 |
|
| 790 |
[<a id="ref-RFC 2247">RFC 2247</a>] Kille, S., Wahl, M., Grimstad, A., Huber, R. and S. |
| 791 |
Sataluri, "Using Domains in LDAP/X.500 Distinguished |
| 792 |
Names", <a href="./rfc2247">RFC 2247</a>, January 1998. |
| 793 |
|
| 794 |
[<a id="ref-RFC 2459">RFC 2459</a>] Housley, R., Ford, W., Polk, W. and D. Solo, "Internet |
| 795 |
X.509 Public Key Infrastructure: Certificate and CRL |
| 796 |
Profile", <a href="./rfc2459">RFC 2459</a>, January 1999. |
| 797 |
|
| 798 |
[<a id="ref-RFC 2985">RFC 2985</a>] Nystrom, M. and B. Kaliski, "PKCS #9: Selected Object |
| 799 |
Classes and Attribute Types Version 2.0", <a href="./rfc2985">RFC 2985</a>, |
| 800 |
November 2000. |
| 801 |
|
| 802 |
[<a id="ref-X.501">X.501</a>] ITU-T Recommendation X.501: Information Technology - Open |
| 803 |
Systems Interconnection - The Directory: Models, June |
| 804 |
1993. |
| 805 |
|
| 806 |
[<a id="ref-X.509">X.509</a>] ITU-T Recommendation X.509: Information Technology - Open |
| 807 |
Systems Interconnection - The Directory: Authentication |
| 808 |
Framework, June 1997. |
| 809 |
|
| 810 |
[<a id="ref-X.520">X.520</a>] ITU-T Recommendation X.520: Information Technology - Open |
| 811 |
Systems Interconnection - The Directory: Selected |
| 812 |
Attribute Types, June 1993. |
| 813 |
|
| 814 |
[<a id="ref-X.680">X.680</a>] ITU-T Recommendation X.680: Information Technology - |
| 815 |
Abstract Syntax Notation One, 1997. |
| 816 |
|
| 817 |
[ISO 3166] ISO Standard 3166: Codes for the representation of names |
| 818 |
of countries, 1993. |
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Intellectual Property Rights</span> |
| 842 |
|
| 843 |
The IETF takes no position regarding the validity or scope of any |
| 844 |
intellectual property or other rights that might be claimed to |
| 845 |
pertain to the implementation or use of the technology described in |
| 846 |
this document or the extent to which any license under such rights |
| 847 |
might or might not be available; neither does it represent that it |
| 848 |
has made any effort to identify any such rights. Information on the |
| 849 |
IETF's procedures with respect to rights in standards-track and |
| 850 |
standards related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of |
| 851 |
claims of rights made available for publication and any assurances of |
| 852 |
licenses to be made available, or the result of an attempt made to |
| 853 |
obtain a general license or permission for the use of such |
| 854 |
proprietary rights by implementors or users of this specification can |
| 855 |
be obtained from the IETF Secretariat. |
| 856 |
|
| 857 |
The IETF invites any interested party to bring to its attention any |
| 858 |
copyrights, patents or patent applications, or other proprietary |
| 859 |
rights which may cover technology that may be required to practice |
| 860 |
this standard. Please address the information to the IETF Executive |
| 861 |
Director. |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</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="./rfc2459">RFC 2459</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="./rfc2459">RFC 2459</a> which are not completely in the 1988 syntax, the same |
| 905 |
comments as in <a href="./rfc2459">RFC 2459</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="./rfc2459">RFC</a> |
| 908 |
<a href="./rfc2459">2459</a>'s 1988 modules. |
| 909 |
|
| 910 |
<a href="#appendix-A.2">Appendix A.2</a> is in the 1993 syntax. However, since the module |
| 911 |
imports type definitions from modules in <a href="./rfc2459">RFC 2459</a> which are not |
| 912 |
completely in the 1993 syntax, the same comments as in <a href="./rfc2459">RFC 2459</a> |
| 913 |
regarding its use applies here as well; i.e., <a href="#appendix-A.2">Appendix A.2</a> may be |
| 914 |
parsed by an 1993 ASN.1-parser by removing the UTF8String choice from |
| 915 |
the definition of DirectoryString in the module PKIX1Explicit93 in |
| 916 |
<a href="./rfc2459">RFC 2459</a>. <a href="#appendix-A.2">Appendix A.2</a> may be parsed "as is" by an 1997 ASN.1 |
| 917 |
parser, however. |
| 918 |
|
| 919 |
In case of discrepancies between these modules, the 1988 module is |
| 920 |
the normative one. |
| 921 |
|
| 922 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a> 1988 ASN.1 Module</span> |
| 923 |
|
| 924 |
PKIXqualified88 {iso(1) identified-organization(3) dod(6) |
| 925 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 926 |
id-mod-qualified-cert-88(10) } |
| 927 |
|
| 928 |
DEFINITIONS EXPLICIT TAGS ::= |
| 929 |
|
| 930 |
BEGIN |
| 931 |
|
| 932 |
-- EXPORTS ALL -- |
| 933 |
|
| 934 |
IMPORTS |
| 935 |
|
| 936 |
GeneralName |
| 937 |
FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6) |
| 938 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 939 |
id-pkix1-implicit-88(2)} |
| 940 |
|
| 941 |
AlgorithmIdentifier, DirectoryString, Attribute, AttributeType, |
| 942 |
id-pkix, id-pe, id-at |
| 943 |
FROM PKIX1Explicit88 {iso(1) identified-organization(3) dod(6) |
| 944 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 951 |
|
| 952 |
|
| 953 |
id-pkix1-explicit-88(1)}; |
| 954 |
|
| 955 |
-- Locally defined OIDs |
| 956 |
|
| 957 |
-- Arc for QC personal data attributes |
| 958 |
id-pda OBJECT IDENTIFIER ::= { id-pkix 9 } |
| 959 |
-- Arc for QC statements |
| 960 |
id-qcs OBJECT IDENTIFIER ::= { id-pkix 11 } |
| 961 |
|
| 962 |
-- Attributes |
| 963 |
|
| 964 |
id-at-serialNumber AttributeType ::= { id-at 5 } |
| 965 |
SerialNumber ::= PrintableString (SIZE(1..64)) |
| 966 |
|
| 967 |
id-at-postalAddress AttributeType ::= { id-at 16 } |
| 968 |
PostalAddress ::= SEQUENCE SIZE (1..6) OF DirectoryString |
| 969 |
|
| 970 |
id-at-pseudonym AttributeType ::= { id-at 65 } |
| 971 |
Pseudonym ::= DirectoryString |
| 972 |
|
| 973 |
domainComponent AttributeType ::= |
| 974 |
{ 0 9 2342 19200300 100 1 25 } |
| 975 |
DomainComponent ::= IA5String |
| 976 |
|
| 977 |
id-pda-dateOfBirth AttributeType ::= { id-pda 1 } |
| 978 |
DateOfBirth ::= GeneralizedTime |
| 979 |
|
| 980 |
id-pda-placeOfBirth AttributeType ::= { id-pda 2 } |
| 981 |
PlaceOfBirth ::= DirectoryString |
| 982 |
|
| 983 |
id-pda-gender AttributeType ::= { id-pda 3 } |
| 984 |
Gender ::= PrintableString (SIZE(1)) |
| 985 |
-- "M", "F", "m" or "f" |
| 986 |
|
| 987 |
id-pda-countryOfCitizenship AttributeType ::= { id-pda 4 } |
| 988 |
CountryOfCitizenship ::= PrintableString (SIZE (2)) |
| 989 |
-- ISO 3166 Country Code |
| 990 |
|
| 991 |
id-pda-countryOfResidence AttributeType ::= { id-pda 5 } |
| 992 |
CountryOfResidence ::= PrintableString (SIZE (2)) |
| 993 |
-- ISO 3166 Country Code |
| 994 |
|
| 995 |
-- Private extensions |
| 996 |
|
| 997 |
-- Biometric info extension |
| 998 |
|
| 999 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= {id-pe 2} |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 1010 |
|
| 1011 |
BiometricData ::= SEQUENCE { |
| 1012 |
typeOfBiometricData TypeOfBiometricData, |
| 1013 |
hashAlgorithm AlgorithmIdentifier, |
| 1014 |
biometricDataHash OCTET STRING, |
| 1015 |
sourceDataUri IA5String OPTIONAL } |
| 1016 |
|
| 1017 |
TypeOfBiometricData ::= CHOICE { |
| 1018 |
predefinedBiometricType PredefinedBiometricType, |
| 1019 |
biometricDataOid OBJECT IDENTIFIER } |
| 1020 |
|
| 1021 |
PredefinedBiometricType ::= INTEGER { |
| 1022 |
picture(0),handwritten-signature(1)} |
| 1023 |
(picture|handwritten-signature) |
| 1024 |
|
| 1025 |
-- QC Statements Extension |
| 1026 |
|
| 1027 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3} |
| 1028 |
|
| 1029 |
QCStatements ::= SEQUENCE OF QCStatement |
| 1030 |
|
| 1031 |
QCStatement ::= SEQUENCE { |
| 1032 |
statementId OBJECT IDENTIFIER, |
| 1033 |
statementInfo ANY DEFINED BY statementId OPTIONAL} |
| 1034 |
|
| 1035 |
-- QC statements |
| 1036 |
id-qcs-pkixQCSyntax-v1 OBJECT IDENTIFIER ::= { id-qcs 1 } |
| 1037 |
|
| 1038 |
-- This statement identifies conformance with syntax and |
| 1039 |
-- semantics defined in this Qualified Certificate profile |
| 1040 |
-- (Version 1). This statement may optionally contain |
| 1041 |
-- additional semantics information as specified below. |
| 1042 |
|
| 1043 |
SemanticsInformation ::= SEQUENCE { |
| 1044 |
semanticsIndentifier OBJECT IDENTIFIER OPTIONAL, |
| 1045 |
nameRegistrationAuthorities NameRegistrationAuthorities OPTIONAL |
| 1046 |
} -- At least one field shall be present |
| 1047 |
|
| 1048 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF GeneralName |
| 1049 |
|
| 1050 |
END |
| 1051 |
|
| 1052 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a> 1993 ASN.1 Module</span> |
| 1053 |
|
| 1054 |
PKIXqualified93 {iso(1) identified-organization(3) dod(6) |
| 1055 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 1056 |
id-mod-qualified-cert-93(11) } |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
DEFINITIONS EXPLICIT TAGS ::= |
| 1066 |
|
| 1067 |
BEGIN |
| 1068 |
|
| 1069 |
-- EXPORTS ALL -- |
| 1070 |
|
| 1071 |
IMPORTS |
| 1072 |
|
| 1073 |
authorityKeyIdentifier, subjectKeyIdentifier, keyUsage, |
| 1074 |
extendedKeyUsage, privateKeyUsagePeriod, certificatePolicies, |
| 1075 |
policyMappings, subjectAltName, issuerAltName, basicConstraints, |
| 1076 |
nameConstraints, policyConstraints, cRLDistributionPoints, |
| 1077 |
subjectDirectoryAttributes, authorityInfoAccess, GeneralName, |
| 1078 |
OTHER-NAME |
| 1079 |
FROM PKIX1Implicit93 {iso(1) identified-organization(3) dod(6) |
| 1080 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 1081 |
id-pkix1-implicit-93(4)} |
| 1082 |
|
| 1083 |
id-pkix, AlgorithmIdentifier, ATTRIBUTE, Extension, EXTENSION, |
| 1084 |
DirectoryString{}, ub-name, id-pe, id-at, id-at-commonName, |
| 1085 |
id-at-surname, id-at-countryName, id-at-localityName, |
| 1086 |
id-at-stateOrProvinceName, id-at-organizationName, |
| 1087 |
id-at-organizationalUnitName, id-at-givenName, id-at-dnQualifier, |
| 1088 |
pkcs9email, title, organizationName, organizationalUnitName, |
| 1089 |
stateOrProvinceName, localityName, countryName, |
| 1090 |
generationQualifier, dnQualifier, initials, givenName, surname, |
| 1091 |
commonName, name |
| 1092 |
FROM PKIX1Explicit93 {iso(1) identified-organization(3) dod(6) |
| 1093 |
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) |
| 1094 |
id-pkix1-explicit-93(3)}; |
| 1095 |
|
| 1096 |
-- Object Identifiers |
| 1097 |
|
| 1098 |
-- Externally defined OIDs |
| 1099 |
id-at-serialNumber OBJECT IDENTIFIER ::= { id-at 5} |
| 1100 |
id-at-postalAddress OBJECT IDENTIFIER ::= { id-at 16 } |
| 1101 |
id-at-pseudonym OBJECT IDENTIFIER ::= { id-at 65 } |
| 1102 |
id-domainComponent OBJECT IDENTIFIER ::= { 0 9 2342 19200300 100 1 25 } |
| 1103 |
|
| 1104 |
-- Locally defined OIDs |
| 1105 |
|
| 1106 |
-- Arc for QC personal data attributes |
| 1107 |
|
| 1108 |
id-pda OBJECT IDENTIFIER ::= { id-pkix 9 } |
| 1109 |
-- Arc for QC statements |
| 1110 |
id-qcs OBJECT IDENTIFIER ::= { id-pkix 11 } |
| 1111 |
|
| 1112 |
-- Private extensions |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
id-pe-biometricInfo OBJECT IDENTIFIER ::= { id-pe 2 } |
| 1122 |
id-pe-qcStatements OBJECT IDENTIFIER ::= { id-pe 3 } |
| 1123 |
|
| 1124 |
-- Personal data attributes |
| 1125 |
id-pda-dateOfBirth OBJECT IDENTIFIER ::= { id-pda 1 } |
| 1126 |
id-pda-placeOfBirth OBJECT IDENTIFIER ::= { id-pda 2 } |
| 1127 |
id-pda-gender OBJECT IDENTIFIER ::= { id-pda 3 } |
| 1128 |
id-pda-countryOfCitizenship OBJECT IDENTIFIER ::= { id-pda 4 } |
| 1129 |
id-pda-countryOfResidence OBJECT IDENTIFIER ::= { id-pda 5 } |
| 1130 |
|
| 1131 |
-- QC statements |
| 1132 |
id-qcs-pkixQCSyntax-v1 OBJECT IDENTIFIER ::= { id-qcs 1 } |
| 1133 |
|
| 1134 |
-- Object Sets |
| 1135 |
|
| 1136 |
-- The following information object set is defined to constrain the |
| 1137 |
-- set of legal certificate extensions. Note that this set is an |
| 1138 |
-- extension of the ExtensionSet defined in <a href="./rfc2459">RFC 2459</a>. |
| 1139 |
ExtensionSet EXTENSION ::= { |
| 1140 |
authorityKeyIdentifier | |
| 1141 |
subjectKeyIdentifier | |
| 1142 |
keyUsage | |
| 1143 |
extendedKeyUsage | |
| 1144 |
privateKeyUsagePeriod | |
| 1145 |
certificatePolicies | |
| 1146 |
policyMappings | |
| 1147 |
subjectAltName | |
| 1148 |
issuerAltName | |
| 1149 |
basicConstraints | |
| 1150 |
nameConstraints | |
| 1151 |
policyConstraints | |
| 1152 |
cRLDistributionPoints | |
| 1153 |
subjectDirectoryAttributes | |
| 1154 |
authorityInfoAccess | |
| 1155 |
biometricInfo | |
| 1156 |
qcStatements, ... } |
| 1157 |
|
| 1158 |
-- The following information object set is defined to constrain the |
| 1159 |
-- set of attributes applications are required to recognize in |
| 1160 |
-- distinguished names. The set may of course be augmented to meet |
| 1161 |
-- local requirements. Note that deleting members of the set may |
| 1162 |
-- prevent interoperability with conforming implementations, and that |
| 1163 |
-- this set is an extension of the SupportedAttributes set in <a href="./rfc2459">RFC 2459</a>. |
| 1164 |
|
| 1165 |
SupportedAttributes ATTRIBUTE ::= { |
| 1166 |
countryName | commonName | surname | givenName | pseudonym | |
| 1167 |
serialNumber | organizationName | organizationalUnitName | |
| 1168 |
stateOrProvinceName | localityName | postalAddress | |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
pkcs9email | domainComponent | dnQualifier, |
| 1178 |
... -- For future extensions -- } |
| 1179 |
|
| 1180 |
-- The following information object set is defined to constrain the |
| 1181 |
-- set of attributes applications are required to recognize in |
| 1182 |
-- subjectDirectoryAttribute extensions. The set may be augmented to |
| 1183 |
-- meet local requirements. Note that deleting members of the set |
| 1184 |
-- may prevent interoperability with conforming implementations. |
| 1185 |
PersonalDataAttributeSet ATTRIBUTE ::= { |
| 1186 |
title | dateOfBirth | placeOfBirth | gender | countryOfCitizenship | |
| 1187 |
countryOfResidence, ... } |
| 1188 |
|
| 1189 |
-- Attributes |
| 1190 |
|
| 1191 |
-- serialNumber from X.520 |
| 1192 |
serialNumber ATTRIBUTE ::= { |
| 1193 |
WITH SYNTAX PrintableString (SIZE(1..64)) |
| 1194 |
ID id-at-serialNumber } |
| 1195 |
|
| 1196 |
-- postalAddress from X.520 |
| 1197 |
postalAddress ATTRIBUTE ::= { |
| 1198 |
WITH SYNTAX SEQUENCE SIZE (1..6) OF DirectoryString { 30 } |
| 1199 |
ID id-at-postalAddress } |
| 1200 |
|
| 1201 |
-- pseudonym from (forthcoming) X.520) |
| 1202 |
pseudonym ATTRIBUTE ::= { |
| 1203 |
WITH SYNTAX DirectoryString { ub-name } |
| 1204 |
ID id-at-pseudonym } |
| 1205 |
|
| 1206 |
-- domainComponent from <a href="./rfc2247">RFC 2247</a> |
| 1207 |
domainComponent ATTRIBUTE ::= { |
| 1208 |
WITH SYNTAX IA5String |
| 1209 |
ID id-domainComponent } |
| 1210 |
|
| 1211 |
dateOfBirth ATTRIBUTE ::= { |
| 1212 |
WITH SYNTAX GeneralizedTime |
| 1213 |
ID id-pda-dateOfBirth } |
| 1214 |
|
| 1215 |
placeOfBirth ATTRIBUTE ::= { |
| 1216 |
WITH SYNTAX DirectoryString { ub-name } |
| 1217 |
ID id-pda-placeOfBirth } |
| 1218 |
|
| 1219 |
gender ATTRIBUTE ::= { |
| 1220 |
WITH SYNTAX PrintableString (SIZE(1) ^ FROM("M"|"F"|"m"|"f")) |
| 1221 |
ID id-pda-gender } |
| 1222 |
|
| 1223 |
countryOfCitizenship ATTRIBUTE ::= { |
| 1224 |
WITH SYNTAX PrintableString (SIZE (2)) |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
(CONSTRAINED BY { -- ISO 3166 codes only -- }) |
| 1234 |
ID id-pda-countryOfCitizenship } |
| 1235 |
|
| 1236 |
countryOfResidence ATTRIBUTE ::= { |
| 1237 |
WITH SYNTAX PrintableString (SIZE (2)) |
| 1238 |
(CONSTRAINED BY { -- ISO 3166 codes only -- }) |
| 1239 |
ID id-pda-countryOfResidence } |
| 1240 |
|
| 1241 |
-- Private extensions |
| 1242 |
|
| 1243 |
-- Biometric info extension |
| 1244 |
|
| 1245 |
biometricInfo EXTENSION ::= { |
| 1246 |
SYNTAX BiometricSyntax |
| 1247 |
IDENTIFIED BY id-pe-biometricInfo } |
| 1248 |
|
| 1249 |
BiometricSyntax ::= SEQUENCE OF BiometricData |
| 1250 |
|
| 1251 |
BiometricData ::= SEQUENCE { |
| 1252 |
typeOfBiometricData TypeOfBiometricData, |
| 1253 |
hashAlgorithm AlgorithmIdentifier, |
| 1254 |
biometricDataHash OCTET STRING, |
| 1255 |
sourceDataUri IA5String OPTIONAL, |
| 1256 |
... -- For future extensions -- } |
| 1257 |
|
| 1258 |
TypeOfBiometricData ::= CHOICE { |
| 1259 |
predefinedBiometricType PredefinedBiometricType, |
| 1260 |
biometricDataOid OBJECT IDENTIFIER } |
| 1261 |
|
| 1262 |
PredefinedBiometricType ::= INTEGER { picture(0), |
| 1263 |
handwritten-signature(1)} (picture|handwritten-signature,...) |
| 1264 |
|
| 1265 |
-- QC Statements Extension |
| 1266 |
|
| 1267 |
qcStatements EXTENSION ::= { |
| 1268 |
SYNTAX QCStatements |
| 1269 |
IDENTIFIED BY id-pe-qcStatements } |
| 1270 |
|
| 1271 |
QCStatements ::= SEQUENCE OF QCStatement |
| 1272 |
|
| 1273 |
QCStatement ::= SEQUENCE { |
| 1274 |
statementId QC-STATEMENT.&id({SupportedStatements}), |
| 1275 |
statementInfo QC-STATEMENT.&Type |
| 1276 |
({SupportedStatements}{@statementId}) OPTIONAL } |
| 1277 |
|
| 1278 |
QC-STATEMENT ::= CLASS { |
| 1279 |
&id OBJECT IDENTIFIER UNIQUE, |
| 1280 |
&Type OPTIONAL } |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
WITH SYNTAX { |
| 1290 |
[SYNTAX &Type] IDENTIFIED BY &id } |
| 1291 |
|
| 1292 |
qcStatement-1 QC-STATEMENT ::= { SYNTAX SemanticsInformation |
| 1293 |
IDENTIFIED BY id-qcs-pkixQCSyntax-v1} |
| 1294 |
-- This statement identifies conformance with syntax and |
| 1295 |
-- semantics defined in this Qualified Certificate profile |
| 1296 |
-- (Version 1). The SemanticsInformation may optionally contain |
| 1297 |
-- additional semantics information as specified. |
| 1298 |
|
| 1299 |
SemanticsInformation ::= SEQUENCE { |
| 1300 |
semanticsIdentifier OBJECT IDENTIFIER OPTIONAL, |
| 1301 |
nameRegistrationAuthorities NameRegistrationAuthorities OPTIONAL |
| 1302 |
}(WITH COMPONENTS {..., semanticsIdentifier PRESENT}| |
| 1303 |
WITH COMPONENTS {..., nameRegistrationAuthorities PRESENT}) |
| 1304 |
|
| 1305 |
NameRegistrationAuthorities ::= SEQUENCE SIZE (1..MAX) OF GeneralName |
| 1306 |
|
| 1307 |
-- The following information object set is defined to constrain the |
| 1308 |
-- set of attributes applications are required to recognize as QCSs. |
| 1309 |
SupportedStatements QC-STATEMENT ::= { |
| 1310 |
qcStatement-1, ... -- For future extensions -- } |
| 1311 |
|
| 1312 |
END |
| 1313 |
|
| 1314 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">B</a>. A Note on Attributes</span> |
| 1315 |
|
| 1316 |
This document defines several new attributes, both for use in the |
| 1317 |
subject field of issued certificates and in the |
| 1318 |
subjectDirectoryAttributes extension. In the interest of conformity, |
| 1319 |
they have been defined here using the ASN.1 ATTRIBUTE definition from |
| 1320 |
<a href="./rfc2459">RFC 2459</a>, which is sufficient for the purposes of this document, but |
| 1321 |
greatly simplified in comparison with ISO/ITU's definition. A |
| 1322 |
complete definition of these new attributes (including matching |
| 1323 |
rules), along with object classes to support them in LDAP-accessible |
| 1324 |
directories, can be found in [PKCS 9]. |
| 1325 |
|
| 1326 |
<span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">C</a>. Example Certificate</span> |
| 1327 |
|
| 1328 |
This section contains the ASN.1 structure, an ASN.1 dump, and the |
| 1329 |
DER-encoding of a certificate issued in conformance with this |
| 1330 |
profile. The example has been developed with the help of the OSS |
| 1331 |
ASN.1 compiler. The certificate has the following characteristics: |
| 1332 |
|
| 1333 |
1. The certificate is signed with RSA and the SHA-1 hash |
| 1334 |
algorithm |
| 1335 |
2. The issuer's distinguished name is O=GMD - Forschungszentrum |
| 1336 |
Informationstechnik GmbH; C=DE |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
3. The subject's distinguished name is CN=Petra M. Barzin, O=GMD |
| 1346 |
- Forschungszentrum Informationstechnik GmbH, C=DE |
| 1347 |
4. The certificate was issued on May 1, 2000 and will expire on |
| 1348 |
November 1, 2000 |
| 1349 |
5. The certificate contains a 1024 bit RSA key |
| 1350 |
6. The certificate includes a critical key usage extension |
| 1351 |
exclusively indicating non-repudiation |
| 1352 |
7. The certificate includes a certificate policy identifier |
| 1353 |
extension indicating the practices and procedures undertaken |
| 1354 |
by the issuing CA (object identifier 1.3.36.8.1.1). The |
| 1355 |
certificate policy object identifier is defined by TeleTrust, |
| 1356 |
Germany. It is required to be set in a certificate conformant |
| 1357 |
to the German digital signature law. |
| 1358 |
8. The certificate includes a subject directory attributes |
| 1359 |
extension containing the following attributes: |
| 1360 |
|
| 1361 |
surname: Barzin |
| 1362 |
given name: Petra |
| 1363 |
date of birth: October, 14th 1971 |
| 1364 |
place of birth: Darmstadt |
| 1365 |
country of citizenship:Germany |
| 1366 |
gender: Female |
| 1367 |
|
| 1368 |
9. The certificate includes a qualified statement private |
| 1369 |
extension indicating that the naming registration authority's |
| 1370 |
name as "[email protected]". |
| 1371 |
10. The certificate includes, in conformance with <a href="./rfc2459">RFC 2459</a>, an |
| 1372 |
authority key identifier extension. |
| 1373 |
|
| 1374 |
<span class="h3"><a class="selflink" id="appendix-C.1" href="#appendix-C.1">C.1</a> ASN.1 Structure</span> |
| 1375 |
|
| 1376 |
<span class="h4"><a class="selflink" id="appendix-C.1.1" href="#appendix-C.1.1">C.1.1</a> Extensions</span> |
| 1377 |
|
| 1378 |
Since extensions are DER-encoded already when placed in the structure |
| 1379 |
to be signed, they are for clarity shown here in the value notation |
| 1380 |
defined in [<a href="#ref-X.680">X.680</a>]. |
| 1381 |
|
| 1382 |
<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> |
| 1383 |
|
| 1384 |
petrasSubjDirAttrs AttributesSyntax ::= { |
| 1385 |
{ |
| 1386 |
type id-pda-countryOfCitizenship, |
| 1387 |
values { |
| 1388 |
PrintableString : "DE" |
| 1389 |
} |
| 1390 |
}, |
| 1391 |
{ |
| 1392 |
type id-pda-gender, |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
values { |
| 1402 |
PrintableString : "F" |
| 1403 |
} |
| 1404 |
}, |
| 1405 |
{ |
| 1406 |
type id-pda-dateOfBirth, |
| 1407 |
values { |
| 1408 |
GeneralizedTime : "197110140000Z" |
| 1409 |
} |
| 1410 |
}, |
| 1411 |
{ |
| 1412 |
type id-pda-placeOfBirth, |
| 1413 |
values { |
| 1414 |
DirectoryString : utf8String : "Darmstadt" |
| 1415 |
} |
| 1416 |
} |
| 1417 |
} |
| 1418 |
|
| 1419 |
<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> |
| 1420 |
|
| 1421 |
petrasKeyUsage KeyUsage ::= {nonRepudiation} |
| 1422 |
|
| 1423 |
<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> |
| 1424 |
|
| 1425 |
petrasCertificatePolicies CertificatePoliciesSyntax ::= { |
| 1426 |
{ |
| 1427 |
policyIdentifier {1 3 36 8 1 1} |
| 1428 |
} |
| 1429 |
} |
| 1430 |
|
| 1431 |
<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> |
| 1432 |
|
| 1433 |
petrasQCStatement QCStatements ::= { |
| 1434 |
{ |
| 1435 |
statementId id-qcs-pkixQCSyntax-v1, |
| 1436 |
statementInfo SemanticsInformation : { |
| 1437 |
nameRegistrationAuthorities { |
| 1438 |
rfc822Name : "[email protected]" |
| 1439 |
} |
| 1440 |
} |
| 1441 |
} |
| 1442 |
} |
| 1443 |
|
| 1444 |
<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> |
| 1445 |
|
| 1446 |
petrasAKI AuthorityKeyIdentifier ::= { |
| 1447 |
keyIdentifier '000102030405060708090A0B0C0D0E0FFEDCBA98'H |
| 1448 |
} |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
<span class="h4"><a class="selflink" id="appendix-C.1.2" href="#appendix-C.1.2">C.1.2</a> The certificate</span> |
| 1458 |
|
| 1459 |
The signed portion of the certificate is shown here in the value |
| 1460 |
notation defined in [<a href="#ref-X.680">X.680</a>]. Note that extension values are already |
| 1461 |
DER encoded in this structure. Some values has been truncated for |
| 1462 |
readability purposes. |
| 1463 |
|
| 1464 |
{ |
| 1465 |
version v3, |
| 1466 |
serialNumber 1234567890, |
| 1467 |
signature |
| 1468 |
{ |
| 1469 |
algorithm { 1 2 840 113549 1 1 5 }, |
| 1470 |
parameters RSAParams : NULL |
| 1471 |
}, |
| 1472 |
issuer rdnSequence : |
| 1473 |
{ |
| 1474 |
{ |
| 1475 |
{ |
| 1476 |
type { 2 5 4 6 }, |
| 1477 |
value PrintableString : "DE" |
| 1478 |
} |
| 1479 |
}, |
| 1480 |
{ |
| 1481 |
{ |
| 1482 |
type { 2 5 4 10 }, |
| 1483 |
value UTF8String : |
| 1484 |
"GMD - Forschungszentrum Informationstechnik GmbH" |
| 1485 |
} |
| 1486 |
} |
| 1487 |
}, |
| 1488 |
validity |
| 1489 |
{ |
| 1490 |
notBefore utcTime : "000501100000Z", |
| 1491 |
notAfter utcTime : "001101100000Z" |
| 1492 |
}, |
| 1493 |
subject rdnSequence : |
| 1494 |
{ |
| 1495 |
{ |
| 1496 |
{ |
| 1497 |
type { 2 5 4 6 }, |
| 1498 |
value PrintableString : "DE" |
| 1499 |
} |
| 1500 |
}, |
| 1501 |
{ |
| 1502 |
{ |
| 1503 |
type { 2 5 4 10 }, |
| 1504 |
value UTF8String : |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
"GMD Forschungszentrum Informationstechnik GmbH" |
| 1514 |
} |
| 1515 |
}, |
| 1516 |
{ |
| 1517 |
{ |
| 1518 |
type { 2 5 4 4 }, |
| 1519 |
value UTF8String : "Barzin" |
| 1520 |
}, |
| 1521 |
{ |
| 1522 |
type { 2 5 4 42 }, |
| 1523 |
value UTF8String : "Petra" |
| 1524 |
} |
| 1525 |
} |
| 1526 |
}, |
| 1527 |
subjectPublicKeyInfo |
| 1528 |
{ |
| 1529 |
algorithm |
| 1530 |
{ |
| 1531 |
algorithm { 1 2 840 113549 1 1 1 }, |
| 1532 |
parameters RSAParams : NULL |
| 1533 |
}, |
| 1534 |
subjectPublicKey '00110000 10000001 10000111 00000010 1000 ...'B |
| 1535 |
}, |
| 1536 |
extensions |
| 1537 |
{ |
| 1538 |
{ |
| 1539 |
extnId { 2 5 29 9 }, -- subjectDirectoryAttributes |
| 1540 |
extnValue '305B301006082B06010505070904310413024445300F0 ...'H |
| 1541 |
}, |
| 1542 |
{ |
| 1543 |
extnId { 2 5 29 15 }, -- keyUsage |
| 1544 |
critical TRUE, |
| 1545 |
extnValue '03020640'H |
| 1546 |
}, |
| 1547 |
{ |
| 1548 |
extnId { 2 5 29 32 }, -- certificatePolicies |
| 1549 |
extnValue '3009300706052B24080101'H |
| 1550 |
}, |
| 1551 |
{ |
| 1552 |
extnId { 2 5 29 35 }, -- authorityKeyIdentifier |
| 1553 |
extnValue '30168014000102030405060708090A0B0C0D0E0FFEDCBA98'H |
| 1554 |
}, |
| 1555 |
{ |
| 1556 |
extnId { 1 3 6 1 5 5 7 1 3 }, -- qcStatements |
| 1557 |
extnValue '302B302906082B06010505070B01301D301B81196D756 ...'H |
| 1558 |
} |
| 1559 |
} |
| 1560 |
} |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
<span class="h3"><a class="selflink" id="appendix-C.2" href="#appendix-C.2">C.2</a> ASN.1 dump</span> |
| 1570 |
|
| 1571 |
This section contains an ASN.1 dump of the signed portion of the |
| 1572 |
certificate. Some values has been truncated for readability |
| 1573 |
purposes. |
| 1574 |
|
| 1575 |
TBSCertificate SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1576 |
length = 631 |
| 1577 |
version : tag = [0] constructed; length = 3 |
| 1578 |
Version INTEGER: tag = [UNIVERSAL 2] primitive; length = 1 |
| 1579 |
2 |
| 1580 |
serialNumber CertificateSerialNumber INTEGER: tag = [UNIVERSAL 2] |
| 1581 |
primitive; length = 4 |
| 1582 |
1234567890 |
| 1583 |
signature AlgorithmIdentifier SEQUENCE: tag = [UNIVERSAL 16] |
| 1584 |
constructed; length = 13 |
| 1585 |
algorithm OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1586 |
length = 9 |
| 1587 |
{ 1 2 840 113549 1 1 5 } |
| 1588 |
parameters OpenType: NULL: tag = [UNIVERSAL 5] primitive; |
| 1589 |
length = 0 |
| 1590 |
NULL |
| 1591 |
issuer Name CHOICE |
| 1592 |
rdnSequence RDNSequence SEQUENCE OF: tag = [UNIVERSAL 16] |
| 1593 |
constructed; length = 72 |
| 1594 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1595 |
constructed; length = 11 |
| 1596 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1597 |
constructed; length = 9 |
| 1598 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1599 |
length = 3 |
| 1600 |
{ 2 5 4 6 } |
| 1601 |
value OpenType: PrintableString: tag = [UNIVERSAL 19] |
| 1602 |
primitive; length = 2 |
| 1603 |
"DE" |
| 1604 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1605 |
constructed; length = 57 |
| 1606 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1607 |
constructed; length = 55 |
| 1608 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1609 |
length = 3 |
| 1610 |
{ 2 5 4 10 } |
| 1611 |
value OpenType : UTF8String: tag = [UNIVERSAL 12] |
| 1612 |
primitive; length = 48 |
| 1613 |
0x474d44202d20466f72736368756e67737a656e7472756d2049... |
| 1614 |
validity Validity SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1615 |
length = 30 |
| 1616 |
notBefore Time CHOICE |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
utcTime UTCTime: tag = [UNIVERSAL 23] primitive; length = 13 |
| 1626 |
000501100000Z |
| 1627 |
notAfter Time CHOICE |
| 1628 |
utcTime UTCTime: tag = [UNIVERSAL 23] primitive; length = 13 |
| 1629 |
001101100000Z |
| 1630 |
subject Name CHOICE |
| 1631 |
rdnSequence RDNSequence SEQUENCE OF: tag = [UNIVERSAL 16] |
| 1632 |
constructed; length = 101 |
| 1633 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1634 |
constructed; length = 11 |
| 1635 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1636 |
constructed; length = 9 |
| 1637 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1638 |
length = 3 |
| 1639 |
{ 2 5 4 6 } |
| 1640 |
value OpenType: PrintableString: tag = [UNIVERSAL 19] |
| 1641 |
primitive; length = 2 |
| 1642 |
"DE" |
| 1643 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1644 |
constructed; length = 55 |
| 1645 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1646 |
constructed; length = 53 |
| 1647 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1648 |
length = 3 |
| 1649 |
{ 2 5 4 10 } |
| 1650 |
value OpenType: UTF8String: tag = [UNIVERSAL 12] |
| 1651 |
primitive; length = 46 |
| 1652 |
0x474d4420466f72736368756e67737a656e7472756d20496e66... |
| 1653 |
RelativeDistinguishedName SET OF: tag = [UNIVERSAL 17] |
| 1654 |
constructed; length = 29 |
| 1655 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1656 |
constructed; length = 13 |
| 1657 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1658 |
length = 3 |
| 1659 |
{ 2 5 4 4 } |
| 1660 |
value OpenType: UTF8String: tag = [UNIVERSAL 12] |
| 1661 |
primitive; length = 6 |
| 1662 |
0x4261727a696e |
| 1663 |
AttributeTypeAndValue SEQUENCE: tag = [UNIVERSAL 16] |
| 1664 |
constructed; length = 12 |
| 1665 |
type OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1666 |
length = 3 |
| 1667 |
{ 2 5 4 42 } |
| 1668 |
value OpenType: UTF8String: tag = [UNIVERSAL 12] |
| 1669 |
primitive; length = 5 |
| 1670 |
0x5065747261 |
| 1671 |
subjectPublicKeyInfo SubjectPublicKeyInfo SEQUENCE: tag = |
| 1672 |
[UNIVERSAL 16] constructed; length = 157 |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
algorithm AlgorithmIdentifier SEQUENCE: tag = [UNIVERSAL 16] |
| 1682 |
constructed; length = 13 |
| 1683 |
algorithm OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1684 |
length = 9 |
| 1685 |
{ 1 2 840 113549 1 1 1 } |
| 1686 |
parameters OpenType: NULL: tag = [UNIVERSAL 5] primitive; |
| 1687 |
length = 0 |
| 1688 |
NULL |
| 1689 |
subjectPublicKey BIT STRING: tag = [UNIVERSAL 3] primitive; |
| 1690 |
length = 139 |
| 1691 |
0x0030818702818100b8488400d4b6088be48ead459ca19ec717aaf3d1d... |
| 1692 |
extensions : tag = [3] constructed; length = 233 |
| 1693 |
Extensions SEQUENCE OF: tag = [UNIVERSAL 16] constructed; |
| 1694 |
length = 230 |
| 1695 |
Extension SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1696 |
length = 100 |
| 1697 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1698 |
length = 3 |
| 1699 |
{ 2 5 29 9 } |
| 1700 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] primitive; |
| 1701 |
length = 93 |
| 1702 |
0x305b301006082b06010505070904310413024445300f06082b060... |
| 1703 |
Extension SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1704 |
length = 14 |
| 1705 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1706 |
length = 3 |
| 1707 |
{ 2 5 29 15 } |
| 1708 |
critical BOOLEAN: tag = [UNIVERSAL 1] primitive; length = 1 |
| 1709 |
TRUE |
| 1710 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] primitive; |
| 1711 |
length = 4 |
| 1712 |
0x03020640 |
| 1713 |
Extension SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1714 |
length = 18 |
| 1715 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1716 |
length = 3 |
| 1717 |
{ 2 5 29 32 } |
| 1718 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] primitive; |
| 1719 |
length = 11 |
| 1720 |
0x3009300706052b24080101 |
| 1721 |
Extension SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1722 |
length = 31 |
| 1723 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1724 |
length = 3 |
| 1725 |
{ 2 5 29 35 } |
| 1726 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] primitive; |
| 1727 |
length = 24 |
| 1728 |
0x30168014000102030405060708090a0b0c0d0e0ffedcba98 |
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
Extension SEQUENCE: tag = [UNIVERSAL 16] constructed; |
| 1738 |
length = 57 |
| 1739 |
extnId OBJECT IDENTIFIER: tag = [UNIVERSAL 6] primitive; |
| 1740 |
length = 8 |
| 1741 |
{ 1 3 6 1 5 5 7 1 3 } |
| 1742 |
extnValue OCTET STRING: tag = [UNIVERSAL 4] primitive; |
| 1743 |
length = 45 |
| 1744 |
0x302b302906082b06010505070b01301d301b81196d756e6963697... |
| 1745 |
|
| 1746 |
<span class="h3"><a class="selflink" id="appendix-C.3" href="#appendix-C.3">C.3</a> DER-encoding</span> |
| 1747 |
|
| 1748 |
This section contains the full, DER-encoded certificate, in hex. |
| 1749 |
|
| 1750 |
3082030E30820277A0030201020204499602D2300D06092A864886F70D010105 |
| 1751 |
05003048310B300906035504061302444531393037060355040A0C30474D4420 |
| 1752 |
2D20466F72736368756E67737A656E7472756D20496E666F726D6174696F6E73 |
| 1753 |
746563686E696B20476D6248301E170D3030303530313130303030305A170D30 |
| 1754 |
30313130313130303030305A3065310B30090603550406130244453137303506 |
| 1755 |
0355040A0C2E474D4420466F72736368756E67737A656E7472756D20496E666F |
| 1756 |
726D6174696F6E73746563686E696B20476D6248311D300C060355042A0C0550 |
| 1757 |
65747261300D06035504040C064261727A696E30819D300D06092A864886F70D |
| 1758 |
010101050003818B0030818702818100B8488400D4B6088BE48EAD459CA19EC7 |
| 1759 |
17AAF3D1D4EE3ECCA496128A13597D16CC8B85EB37EFCE110C63B01E684E5CF6 |
| 1760 |
32291EAC60FD153C266EAAC36AD4CEA92319F9BFDD261AD2BFE41EAB4E17FE67 |
| 1761 |
8341EE52D9A0A8B4DEC07B7ACC76762514045CEE9994E0CF37BAE05F8DE33B35 |
| 1762 |
FF98BCE77742CE4B12273BD122137FE9020105A381E93081E630640603551D09 |
| 1763 |
045D305B301006082B06010505070904310413024445300F06082B0601050507 |
| 1764 |
09033103130146301D06082B060105050709013111180F313937313130313430 |
| 1765 |
30303030305A301706082B06010505070902310B0C094461726D737461647430 |
| 1766 |
0E0603551D0F0101FF04040302064030120603551D20040B3009300706052B24 |
| 1767 |
080101301F0603551D23041830168014000102030405060708090A0B0C0D0E0F |
| 1768 |
FEDCBA98303906082B06010505070103042D302B302906082B06010505070B01 |
| 1769 |
301D301B81196D756E69636970616C697479406461726D73746164742E646530 |
| 1770 |
0D06092A864886F70D01010505000381810048FD14D9AFE961E4321D9AA40CC0 |
| 1771 |
1C12893550CF76FBECBDE448926B0AE6F904AB89E7B5F808666FB007218AC18D |
| 1772 |
28CE1E2D40FBF8C16B275CBA0547D7885B74059DEC736223368FC1602A510BC1 |
| 1773 |
EB31E39F3967BE6B413D48BC743A0AB19C57FD20F3B393E8FEBD8B05CAA5007D |
| 1774 |
AD36F9D789AEF636A0AC0F93BCB3711B5907 |
| 1775 |
|
| 1776 |
|
| 1777 |
|
| 1778 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
<span class="h3"><a class="selflink" id="appendix-C.4" href="#appendix-C.4">C.4</a> CA's public RSA key</span> |
| 1794 |
|
| 1795 |
This section contains the DER-encoded public RSA key of the CA who |
| 1796 |
signed the example certificate. It is included with the purpose of |
| 1797 |
simplifying verifications of the example certificate. |
| 1798 |
|
| 1799 |
30818902818100ad1f35964b3674c807b9f8a645d2c8174e514b69a4b46a7382 |
| 1800 |
915abbc44eccede914dae8fcc023abcea9c53380e641795cb0dda664b872fc10 |
| 1801 |
9f9bbb852bf42d994f634c681608e388dce240b558513e5b60027bd1a07cef9c |
| 1802 |
9b6db37c7e1f1abd238eed96e4b669056b260f55e83f14e6027127c9deb3ad18 |
| 1803 |
afcd3f8a5f5bf50203010001 |
| 1804 |
|
| 1805 |
|
| 1806 |
|
| 1807 |
|
| 1808 |
|
| 1809 |
|
| 1810 |
|
| 1811 |
|
| 1812 |
|
| 1813 |
|
| 1814 |
|
| 1815 |
|
| 1816 |
|
| 1817 |
|
| 1818 |
|
| 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="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
Authors' Addresses |
| 1850 |
|
| 1851 |
Stefan Santesson |
| 1852 |
AddTrust AB |
| 1853 |
P.O. Box 465 |
| 1854 |
S-201 24 Malmo |
| 1855 |
Sweden |
| 1856 |
|
| 1857 |
EMail: [email protected] |
| 1858 |
|
| 1859 |
|
| 1860 |
Tim Polk |
| 1861 |
NIST |
| 1862 |
Building 820, Room 426 |
| 1863 |
Gaithersburg, MD 20899, USA |
| 1864 |
|
| 1865 |
EMail: [email protected] |
| 1866 |
|
| 1867 |
|
| 1868 |
Petra Barzin |
| 1869 |
SECUDE - Sicherheitstechnologie Informationssysteme GmbH |
| 1870 |
Landwehrstrasse 50a |
| 1871 |
D-64293 Darmstadt |
| 1872 |
Germany |
| 1873 |
|
| 1874 |
EMail: [email protected] |
| 1875 |
|
| 1876 |
|
| 1877 |
Magnus Nystrom |
| 1878 |
RSA Security AB |
| 1879 |
Box 10704 |
| 1880 |
S-121 29 Stockholm |
| 1881 |
Sweden |
| 1882 |
|
| 1883 |
EMail: [email protected] |
| 1884 |
|
| 1885 |
|
| 1886 |
|
| 1887 |
|
| 1888 |
|
| 1889 |
|
| 1890 |
|
| 1891 |
|
| 1892 |
|
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Santesson, et al. Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc3039">RFC 3039</a> Qualified Certificates Profile January 2001</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
Full Copyright Statement |
| 1906 |
|
| 1907 |
Copyright (C) The Internet Society (2001). All Rights Reserved. |
| 1908 |
|
| 1909 |
This document and translations of it may be copied and furnished to |
| 1910 |
others, and derivative works that comment on or otherwise explain it |
| 1911 |
or assist in its implementation may be prepared, copied, published |
| 1912 |
and distributed, in whole or in part, without restriction of any |
| 1913 |
kind, provided that the above copyright notice and this paragraph are |
| 1914 |
included on all such copies and derivative works. However, this |
| 1915 |
document itself may not be modified in any way, such as by removing |
| 1916 |
the copyright notice or references to the Internet Society or other |
| 1917 |
Internet organizations, except as needed for the purpose of |
| 1918 |
developing Internet standards in which case the procedures for |
| 1919 |
copyrights defined in the Internet Standards process must be |
| 1920 |
followed, or as required to translate it into languages other than |
| 1921 |
English. |
| 1922 |
|
| 1923 |
The limited permissions granted above are perpetual and will not be |
| 1924 |
revoked by the Internet Society or its successors or assigns. |
| 1925 |
|
| 1926 |
This document and the information contained herein is provided on an |
| 1927 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 1928 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 1929 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 1930 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 1931 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1932 |
|
| 1933 |
Acknowledgement |
| 1934 |
|
| 1935 |
Funding for the RFC Editor function is currently provided by the |
| 1936 |
Internet Society. |
| 1937 |
|
| 1938 |
|
| 1939 |
|
| 1940 |
|
| 1941 |
|
| 1942 |
|
| 1943 |
|
| 1944 |
|
| 1945 |
|
| 1946 |
|
| 1947 |
|
| 1948 |
|
| 1949 |
|
| 1950 |
|
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
Santesson, et al. Standards Track [Page 35] |
| 1957 |
</pre> |