Connection-less Lightweight X.500 Directory Access Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 9
- Abstract
- The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]
- Publication Date
- 1995-06-01
- Status Note
- Historic
- DOI
10.17487/RFC1798- Link
- https://doi.org/10.17487/RFC1798
- Author(s)
- Alan Young
- Keyword(s)
- CLDAP, Application
Latest version of IETF RFC 1798
Document Versions — IETF RFC 1798
-
▶ IETF RFC 1798 (1995-06-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1798.json
Superseded by:
RFC3352 NOT IN REGISTRY
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 1798, Connection-less Lightweight X.500 Directory Access Protocol. Available at https://doi.org/10.17487/RFC1798
Snippet:
IETF RFC 1798, Connection-less Lightweight X.500 Directory Access Protocol. Available at https://doi.org/10.17487/RFC1798
HTML (ISO 690 compliant)
Preview:
IETF RFC 1798, Connection-less Lightweight X.500 Directory Access Protocol. Available at https://doi.org/10.17487/RFC1798
Snippet:
<span class="citation"><cite>IETF RFC 1798</cite>, Connection-less Lightweight X.500 Directory Access Protocol. Available at <a href="https://doi.org/10.17487/RFC1798" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1798</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1798, Connection-less Lightweight X.500 Directory Access Protocol
doi: 10.17487/RFC1798
url: https://doi.org/10.17487/RFC1798
doi: 10.17487/RFC1798
url: https://doi.org/10.17487/RFC1798
Snippet:
<li> <cite id="bib-rfc1798">IETF RFC 1798</cite>, Connection-less Lightweight X.500 Directory Access Protocol <span class="doi">10.17487/RFC1798</span> </li>
Referenced By
- IETF RFC 2116 [Active*]
- IETF RFC 2605 [Active*]
- IETF RFC 2896 [Active*]