References from RFC 3641
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 11 |
References Referenced by |
informatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
RFC 2156 |
MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | normatively references | |
RFC 2252 |
Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
References Referenced by |
Proposed Standard | normatively references | |
RFC 2253 |
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
References Referenced by |
Proposed Standard | normatively references | |
RFC 2279 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Draft Standard | normatively references | |
RFC 3377 |
Lightweight Directory Access Protocol (v3): Technical Specification
References Referenced by |
Proposed Standard | informatively references | |
RFC 3642 |
Common Elements of Generic String Encoding Rules (GSER) Encodings
References Referenced by |
Informational | informatively references | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | normatively references |