References to RFC 5518
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 byreference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 5782 | DNS Blacklists and Whitelists References Referenced by | Informational | normatively references | |
| RFC 6212 | Authentication-Results Registration for Vouch by Reference Results References Referenced by | Proposed Standard | normatively references | |
| RFC 8552 | Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves References Referenced by | Best Current Practice | normatively references | |
| RFC 8553 | DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names References Referenced by | Best Current Practice | normatively references | |
| RFC 7001 | Message Header Field for Indicating Message Authentication Status References Referenced by | Proposed Standard | informatively references | |
| RFC 7070 | An Architecture for Reputation Reporting References Referenced by | Proposed Standard | informatively references | |
| RFC 7601 | Message Header Field for Indicating Message Authentication Status References Referenced by | Proposed Standard | informatively references | |
| RFC 8601 | Message Header Field for Indicating Message Authentication Status References Referenced by | Proposed Standard | informatively references |