References from draft-ietf-tls-svcb-ech
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 219 | References Referenced by | informatively references | ||
| draft-ietf-tls-esni | TLS Encrypted Client Hello References Referenced by | Proposed Standard | normatively references | |
| RFC 1034 | Domain names - concepts and facilities 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 4648 | The Base16, Base32, and Base64 Data Encodings References Referenced by | Proposed Standard | normatively references | |
| RFC 7838 | HTTP Alternative Services 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 9001 | Using TLS to Secure QUIC References Referenced by | Proposed Standard | informatively references | |
| RFC 9147 | The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 References Referenced by | Proposed Standard | informatively references | |
| RFC 9364 | DNS Security Extensions (DNSSEC) References Referenced by | Best Current Practice | normatively references | |
| RFC 9460 | Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records) References Referenced by | Proposed Standard | normatively references |