References from RFC 2070
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 1345 |
Character Mnemonics and Character Sets
References Referenced by |
Informational | Possible Reference | |
RFC 1468 |
Japanese Character Encoding for Internet Messages
References Referenced by |
Informational | Possible Reference | |
RFC 1641 |
Using Unicode with MIME
References Referenced by |
Experimental | Possible Reference | |
RFC 1642 |
UTF-7 - A Mail-Safe Transformation Format of Unicode
References Referenced by |
Experimental | Possible Reference | |
RFC 1738 |
Uniform Resource Locators (URL)
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 1766 |
Tags for the Identification of Languages
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 1866 |
Hypertext Markup Language - 2.0
References Referenced by |
Historic | Possible Reference | |
RFC 1867 |
Form-based File Upload in HTML
References Referenced by |
Historic | Possible Reference | |
RFC 1942 |
HTML Tables
References Referenced by |
Historic | Possible Reference | |
RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | Possible Reference | |
RFC 2068 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Proposed Standard | Possible Reference | |
STD 1 |
References Referenced by |
Possible Reference |