RFC 2587 (rfc2587) - Page 2 of 8

Internet X

RFC 2587                   PKIX LDAPv2 Schema                  June 1999


   entries.  Certificate Revocation List (CRL)is one mechanism for
   publishing revocation information in a repository.  Other mechanisms,
   such as http, are also defined.

   This specification defines the attributes and object classes to be
   used by LDAP servers acting as PKIX repositories and to be understood
   by LDAP clients communicating with such repositories to query, add,
   modify and delete PKI information. Some object classes and attributes
   defined in X.509 are duplicated here for completeness. For end
   entities and Certification Authorities (CA), the earlier X.509
   defined object classes mandated inclusion of attributes which are
   optional for PKIX. Also, because of the mandatory attribute
   specification, this would have required dynamic modification of the
   object class attribute should the attributes not always be present in
   entries. For these reasons, alternative object classes are defined in
   this document for use by LDAP servers acting as PKIX repositories.

3.  PKIX Repository Objects

   The primary PKIX objects to be represented in a repository are:

      -  End Entities
      -  Certification Authorities (CA)

   These objects are defined in RFC 2459.

3.1.  End Entities

   For purposes of PKIX schema definition, the role of end entities as
   subjects of certificates is the major aspect relevant to this
   specification. End entities may be human users, or other types of
   entities to which certificates may be issued. In some cases, the
   entry for the end entity may already exist and the PKI-specific
   information is added to the existing entry. In other cases the entry
   may not exist prior to the issuance of a certificate, in which case
   the entity adding the certificate may also need to create the entry.
   Schema elements used to represent the non PKIX aspects of an entry,
   such as the structural object class used to represent organizational
   persons, may vary, depending on the particular environment and set of
   applications served and are outside the scope of this specification.

   The following auxiliary object class MAY be used to represent
   certificate subjects:








Boeyen, et al.              Standards Track