References from rfc7372
This is an experimental product. 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 |
|---|---|---|---|---|
| BCP 138 |
A Registry for SMTP Enhanced Mail System Status Codes Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 3463 |
Enhanced Mail System Status Codes Refs Ref'd by |
Draft Standard | normatively references | |
| RFC 5248 |
A Registry for SMTP Enhanced Mail System Status Codes Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 6376 |
DomainKeys Identified Mail (DKIM) Signatures Refs Ref'd by |
Internet Standard | normatively references | |
| RFC 7001 |
Message Header Field for Indicating Message Authentication Status Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7208 |
Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 Refs Ref'd by |
Proposed Standard | normatively references | |
| STD 76 |
DomainKeys Identified Mail (DKIM) Signatures Refs Ref'd by |
Internet Standard | normatively references |