References from draft-lmo-dprive-phase2-requirements
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 |
References Referenced by |
normatively references | ||
BCP 219 |
References Referenced by |
normatively references | ||
draft-edmonds-dnsop-capabilities |
Signaling DNS Capabilities
References Referenced by |
informatively references | ||
draft-ietf-uta-smtp-require-tls |
SMTP Require TLS Option
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 6698 |
The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
References Referenced by |
Proposed Standard | informatively references | |
RFC 6797 |
HTTP Strict Transport Security (HSTS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 6891 |
Extension Mechanisms for DNS (EDNS(0))
References Referenced by |
Internet Standard | informatively references | |
RFC 7816 |
DNS Query Name Minimisation to Improve Privacy
References Referenced by |
Experimental | informatively references | |
RFC 7871 |
Client Subnet in DNS Queries
References Referenced by |
Informational | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8198 |
Aggressive Use of DNSSEC-Validated Cache
References Referenced by |
Proposed Standard | informatively references | |
RFC 8499 |
DNS Terminology
References Referenced by |
Best Current Practice | normatively references | |
STD 75 |
References Referenced by |
informatively references |