Skip to main content

References from draft-melnikov-smtp-metadata

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.

Reference type help

Document Title Status Type Downref
BCP 138
References Referenced by
normatively references
BCP 14
References Referenced by
normatively references
BCP 26
References Referenced by
normatively references
RFC 1845 SMTP Service Extension for Checkpoint/Restart
References Referenced by
Experimental informatively references
RFC 1870 SMTP Service Extension for Message Size Declaration
References Referenced by
Internet Standard normatively references
RFC 2033 Local Mail Transfer Protocol
References Referenced by
Informational normatively references
RFC 2034 SMTP Service Extension for Returning Enhanced Error Codes
References Referenced by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2920 SMTP Service Extension for Command Pipelining
References Referenced by
Internet Standard normatively references
RFC 3030 SMTP Service Extensions for Transmission of Large and Binary MIME Messages
References Referenced by
Proposed Standard informatively references
RFC 3207 SMTP Service Extension for Secure SMTP over Transport Layer Security
References Referenced by
Proposed Standard informatively references
RFC 3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
References Referenced by
Draft Standard normatively references
RFC 3501 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by
Proposed Standard normatively references
RFC 4468 Message Submission BURL Extension
References Referenced by
Proposed Standard informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 5228 Sieve: An Email Filtering Language
References Referenced by
Proposed Standard informatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 5248 A Registry for SMTP Enhanced Mail System Status Codes
References Referenced by
Best Current Practice normatively references
RFC 5321 Simple Mail Transfer Protocol
References Referenced by
Draft Standard normatively references
RFC 5322 Internet Message Format
References Referenced by
Draft Standard normatively references
RFC 5598 Internet Mail Architecture
References Referenced by
Informational informatively references
RFC 6409 Message Submission for Mail
References Referenced by
Internet Standard normatively references
RFC 7001 Message Header Field for Indicating Message Authentication Status
References Referenced by
Proposed Standard normatively references
RFC 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by
Internet Standard Possible Reference
STD 10
References Referenced by
normatively references
STD 60
References Referenced by
normatively references
STD 68
References Referenced by
normatively references
STD 72
References Referenced by
normatively references