Internet X.509 Public Key Infrastructure LDAPv2 Schema
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- The schema defined in this document is a minimal schema to support PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK]
- Publication Date
- 1999-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2587- Link
- https://doi.org/10.17487/RFC2587
- Author(s)
- Sharon BoeyenTim HowesPatrick Richard
- Keyword(s)
- LDAP, PKIX
Latest version of IETF RFC 2587
Document Versions — IETF RFC 2587
-
▶ IETF RFC 2587 (1999-06-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1777 [Superseded*]
- IETF RFC 2119 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2587.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2587, Internet X.509 Public Key Infrastructure LDAPv2 Schema. Available at https://doi.org/10.17487/RFC2587
Snippet:
IETF RFC 2587, Internet X.509 Public Key Infrastructure LDAPv2 Schema. Available at https://doi.org/10.17487/RFC2587
HTML (ISO 690 compliant)
Preview:
IETF RFC 2587, Internet X.509 Public Key Infrastructure LDAPv2 Schema. Available at https://doi.org/10.17487/RFC2587
Snippet:
<span class="citation"><cite>IETF RFC 2587</cite>, Internet X.509 Public Key Infrastructure LDAPv2 Schema. Available at <a href="https://doi.org/10.17487/RFC2587" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2587</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2587, Internet X.509 Public Key Infrastructure LDAPv2 Schema
doi: 10.17487/RFC2587
url: https://doi.org/10.17487/RFC2587
doi: 10.17487/RFC2587
url: https://doi.org/10.17487/RFC2587
Snippet:
<li> <cite id="bib-rfc2587">IETF RFC 2587</cite>, Internet X.509 Public Key Infrastructure LDAPv2 Schema <span class="doi">10.17487/RFC2587</span> </li>
Referenced By
- IETF RFC 4158 [Active*]
- IETF RFC 4325 [Superseded*]