References to RFC 8621
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-jmap-emailpush |
JSON Meta Application Protocol (JMAP) Email Delivery Push Notifications
References Referenced by |
normatively references | ||
draft-ietf-mailmaint-messageflag-mailboxattribute |
Registration of further IMAP/JMAP keywords and mailbox name attributes
References Referenced by |
Informational | normatively references | |
RFC 9007 |
Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 9219 |
S/MIME Signature Verification Extension to the JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
draft-happel-mailmaint-pdparchive |
Personal Data Portability Archive
References Referenced by |
informatively references | ||
draft-ietf-jmap-filenode |
JMAP File Storage extension
References Referenced by |
Proposed Standard | informatively references | |
draft-many-tiptop-email |
Deploying and Using Email in Deep Space
References Referenced by |
informatively references | ||
RFC 8457
As draft-ietf-jmap-mail |
IMAP "$Important" Keyword and "\Important" Special-Use Attribute
References Referenced by |
Proposed Standard | informatively references | |
RFC 8474
As draft-ietf-jmap-mail |
IMAP Extension for Object Identifiers
References Referenced by |
Proposed Standard | informatively references | |
RFC 8887 |
A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
References Referenced by |
Proposed Standard | informatively references |