References from draft-sah-resolver-information

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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
BCP 219 DNS Terminology
Refs Ref'd by
Best Current Practice normatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-acme-ip ACME IP Identifier Validation Extension
Refs Ref'd by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 7493 The I-JSON Message Format
Refs Ref'd by
Proposed Standard normatively references
RFC 7858 Specification for DNS over Transport Layer Security (TLS)
Refs Ref'd by
Proposed Standard informatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
Refs Ref'd by
Best Current Practice informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard normatively references
RFC 8484 DNS Queries over HTTPS (DoH)
Refs Ref'd by
Proposed Standard informatively references
RFC 8499 DNS Terminology
Refs Ref'd by
Best Current Practice normatively references
RFC 8615 Well-Known Uniform Resource Identifiers (URIs)
Refs Ref'd by
Proposed Standard informatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard normatively references