References from rfc8767
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 219 |
DNS Terminology References Referenced by |
Best Current Practice | informatively references | |
RFC 1034 |
Domain names - concepts and facilities References Referenced by |
Internet Standard | normatively 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 2181 |
Clarifications to the DNS Specification References Referenced by |
Proposed Standard | normatively references | |
RFC 2308 |
Negative Caching of DNS Queries (DNS NCACHE) References Referenced by |
Proposed Standard | normatively references | |
RFC 6672 |
DNAME Redirection in the DNS References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by |
Best Current Practice | normatively references | |
RFC 8499 |
DNS Terminology References Referenced by |
Best Current Practice | informatively references | |
STD 13 |
Domain names - implementation and specification References Referenced by |
Internet Standard | normatively references |