References from rfc3296
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 | |
| RFC 2079 |
Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2251 |
Lightweight Directory Access Protocol (v3) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2252 |
Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2253 |
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2255 |
The LDAP URL Format Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax Refs Ref'd by |
Draft Standard | normatively references |