References from rfc3088
This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 1034 |
Domain names - concepts and facilities Refs Ref'd by |
Internet Standard | Reference | |
| RFC 1777 |
Lightweight Directory Access Protocol Refs Ref'd by |
Historic | Reference | |
| RFC 1798 |
Connection-less Lightweight X.500 Directory Access Protocol Refs Ref'd by |
Historic | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 2247 |
Using Domains in LDAP/X.500 Distinguished Names Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2251 |
Lightweight Directory Access Protocol (v3) Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2253 |
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2255 |
The LDAP URL Format Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV) Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2829 |
Authentication Methods for LDAP Refs Ref'd by |
Proposed Standard | Reference | |
| RFC 2830 |
Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security Refs Ref'd by |
Proposed Standard | Reference | |
| STD 13 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | Reference |