References from draft-mglt-abcd-doh-privacy-analysis
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 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 188 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| BCP 72 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
| RFC 1035 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3552 |
Guidelines for Writing RFC Text on Security Considerations
References Referenced by |
Best Current Practice | informatively references | |
| RFC 6973 |
Privacy Considerations for Internet Protocols
References Referenced by |
Informational | informatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8484 |
DNS Queries over HTTPS (DoH)
References Referenced by |
Proposed Standard | normatively references | |
| STD 13 |
Domain names - implementation and specification
References Referenced by |
Internet Standard | normatively references |