References from rfc3536
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 18 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | informatively references | |
BCP 47 |
Tags for Identifying Languages References Referenced by |
Best Current Practice | informatively references | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by |
Draft Standard | informatively references | |
RFC 2047 |
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text References Referenced by |
Draft Standard | informatively references | |
RFC 2277 |
IETF Policy on Character Sets and Languages References Referenced by |
Best Current Practice | informatively references | |
RFC 2278 |
IANA Charset Registration Procedures References Referenced by |
Informational | Possible Reference | |
RFC 2279 |
UTF-8, a transformation format of ISO 10646 References Referenced by |
Draft Standard | informatively references | |
RFC 2781 |
UTF-16, an encoding of ISO 10646 References Referenced by |
Informational | informatively references | |
RFC 2822 |
Internet Message Format References Referenced by |
Proposed Standard | informatively references | |
RFC 3066 |
Tags for the Identification of Languages References Referenced by |
Best Current Practice | informatively references | |
STD 13 |
Domain names - implementation and specification References Referenced by |
Internet Standard | Possible Reference |