References from draft-ietf-dnsop-svcb-httpssvc
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.
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 | informatively references | |
BCP 35 |
Guidelines and Registration Procedures for New URI Schemes Refs Ref'd by |
Best Current Practice | normatively references | |
BCP 42 |
Domain Name System (DNS) IANA Considerations Refs Ref'd by |
Best Current Practice | informatively references | |
draft-bellis-dnsop-http-record |
A DNS Resource Record for HTTP Refs Ref'd by |
informatively references | ||
draft-bishop-httpbis-sni-altsvc |
The "SNI" Alt-Svc Parameter Refs Ref'd by |
normatively references | ||
draft-ietf-dnsop-aname |
Address-specific DNS aliases (ANAME) Refs Ref'd by |
Proposed Standard | informatively references | |
draft-ietf-dnsop-attrleaf |
Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves Refs Ref'd by |
Best Current Practice | normatively references | |
draft-ietf-quic-http |
Hypertext Transfer Protocol Version 3 (HTTP/3) Refs Ref'd by |
Proposed Standard | normatively references | |
draft-ietf-tls-esni |
Encrypted Server Name Indication for TLS 1.3 Refs Ref'd by |
normatively references | ||
draft-nygren-dnsop-svcb-httpssvc |
Service binding and parameter specification via the DNS (DNS SVCB and HTTPSSVC) Refs Ref'd by |
Proposed Standard | informatively references | |
draft-nygren-httpbis-httpssvc |
HTTPSSVC service location and parameter specification via the DNS (DNS HTTPSSVC) Refs Ref'd by |
informatively references | ||
RFC 1035 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | normatively references | |
RFC 1928 |
SOCKS Protocol Version 5 Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 2181 |
Clarifications to the DNS Specification Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV) Refs Ref'd by |
Proposed Standard | informatively references | |
RFC 3225 |
Indicating Resolver Support of DNSSEC Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 3597 |
Handling of Unknown DNS Resource Record (RR) Types Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 4648 |
The Base16, Base32, and Base64 Data Encodings Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by |
Internet Standard | normatively references | |
RFC 5952 |
A Recommendation for IPv6 Address Text Representation Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 6066 |
Transport Layer Security (TLS) Extensions: Extension Definitions Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 6147 |
DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 6454 |
The Web Origin Concept Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 6797 |
HTTP Strict Transport Security (HSTS) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 6895 |
Domain Name System (DNS) IANA Considerations Refs Ref'd by |
Best Current Practice | informatively references | |
RFC 7050 |
Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Refs Ref'd by |
Proposed Standard | informatively references | |
RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 7595 |
Guidelines and Registration Procedures for URI Schemes Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 7838 |
HTTP Alternative Services Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 7858 |
Specification for DNS over Transport Layer Security (TLS) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 8305 |
Happy Eyeballs Version 2: Better Connectivity Using Concurrency Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3 Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 8484 |
DNS Queries over HTTPS (DoH) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 8499 |
DNS Terminology Refs Ref'd by |
Best Current Practice | informatively references | |
STD 13 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | normatively references | |
STD 68 |
Augmented BNF for Syntax Specifications: ABNF Refs Ref'd by |
Internet Standard | normatively references |