References from rfc2279
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 19 |
IANA Charset Registration Procedures
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 1642 |
UTF-7 - A Mail-Safe Transformation Format of Unicode
References Referenced by |
Experimental | Possible Reference | Possible Downref |
RFC 2044 |
UTF-8, a transformation format of Unicode and ISO 10646
References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2047 |
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2048 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2049 |
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2152 |
UTF-7 A Mail-Safe Transformation Format of Unicode
References Referenced by |
Informational | Possible Reference | Possible Downref |