References to RFC 3516
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 |
---|---|---|---|---|
RFC 4005 |
Diameter Network Access Server Application
References Referenced by |
Proposed Standard | normatively references | |
RFC 4466 |
Collected Extensions to IMAP4 ABNF
References Referenced by |
Proposed Standard | normatively references | |
RFC 5259 |
Internet Message Access Protocol - CONVERT Extension
References Referenced by |
Proposed Standard | normatively references | |
RFC 5524 |
Extended URLFETCH for Binary and Converted Parts
References Referenced by |
Proposed Standard | normatively references | |
RFC 5550 |
The Internet Email to Support Diverse Service Environments (Lemonade) Profile
References Referenced by |
Proposed Standard | normatively references | |
RFC 7155 |
Diameter Network Access Server Application
References Referenced by |
Proposed Standard | normatively references | |
RFC 7888 |
IMAP4 Non-synchronizing Literals
References Referenced by |
Proposed Standard | normatively references | |
RFC 9051 |
Internet Message Access Protocol (IMAP) - Version 4rev2
References Referenced by |
Proposed Standard | normatively references | |
RFC 4416 |
Goals for Internet Messaging to Support Diverse Service Environments
References Referenced by |
Informational | informatively references | |
RFC 4978 |
The IMAP COMPRESS Extension
References Referenced by |
Proposed Standard | informatively references | |
RFC 5530 |
IMAP Response Codes
References Referenced by |
Proposed Standard | Possible Reference |