References from rfc2252
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 |
---|---|---|---|---|
RFC 1278 |
A string encoding of Presentation Address References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 1778 |
The String Representation of Standard Attribute Syntaxes References Referenced by |
Historic | Possible Reference | Possible Downref |
RFC 2026 |
The Internet Standards Process -- Revision 3 References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2044 |
UTF-8, a transformation format of Unicode and ISO 10646 References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2251 |
Lightweight Directory Access Protocol (v3) References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2253 |
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2256 |
A Summary of the X.500(96) User Schema for use with LDAPv3 References Referenced by |
Proposed Standard | Possible Reference | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES References Referenced by |
Internet Standard | Possible Reference | |
STD 1 |
Internet Official Protocol Standards References Referenced by |
Historic | Possible Reference | Possible Downref |
STD 11 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES References Referenced by |
Internet Standard | Possible Reference |