References from rfc4530
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 | normatively references | |
| BCP 64 |
Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) Refs Ref'd by |
Best Current Practice | informatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 4122 |
A Universally Unique IDentifier (UUID) URN Namespace Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4510 |
Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4512 |
Lightweight Directory Access Protocol (LDAP): Directory Information Models Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4514 |
Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 4517 |
Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4520 |
Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) Refs Ref'd by |
Best Current Practice | informatively references |