References to rfc1864
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
draft-ietf-extra-imap4rev2 |
Internet Message Access Protocol (IMAP) - Version 4rev2 References Referenced by |
Proposed Standard | normatively references | |
RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 References Referenced by |
Proposed Standard | normatively references | |
RFC 4021 |
Registration of Mail and MIME Header Fields References Referenced by |
Proposed Standard | normatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields References Referenced by |
Best Current Practice | informatively references | |
RFC 2069 |
An Extension to HTTP : Digest Access Authentication References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2660 |
The Secure HyperText Transfer Protocol References Referenced by |
Experimental | Possible Reference | |
RFC 3792 |
Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents References Referenced by |
Informational | Possible Reference | |
RFC 2060 |
Internet Message Access Protocol - Version 4rev1 References Referenced by |
Proposed Standard | Reference | |
RFC 2068 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Proposed Standard | Reference | |
RFC 2076 |
Common Internet Message Headers References Referenced by |
Informational | Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | Reference | |
RFC 3230 |
Instance Digests in HTTP References Referenced by |
Proposed Standard | Reference |