References from draft-reddy-add-resolver-info
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 |
---|---|---|---|---|
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 7493 |
The I-JSON Message Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 7816 |
DNS Query Name Minimisation to Improve Privacy
References Referenced by |
Experimental | normatively references | |
RFC 7858 |
Specification for DNS over Transport Layer Security (TLS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | informatively references | |
RFC 8484 |
DNS Queries over HTTPS (DoH)
References Referenced by |
Proposed Standard | informatively references | |
RFC 8499 |
DNS Terminology
References Referenced by |
Best Current Practice | informatively references | |
RFC 8914 |
Extended DNS Errors
References Referenced by |
Proposed Standard | normatively references |