References from RFC 4969
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 78 | References Referenced by | informatively references | ||
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | Possible Reference | |
| RFC 2426 | vCard MIME Directory Profile References Referenced by | Proposed Standard | normatively references | |
| RFC 2616 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Draft Standard | informatively references | |
| RFC 2617 | HTTP Authentication: Basic and Digest Access Authentication References Referenced by | Draft Standard | informatively references | |
| RFC 2965 | HTTP State Management Mechanism References Referenced by | Historic | informatively references | |
| RFC 3761 | The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) References Referenced by | Proposed Standard | normatively references | |
| RFC 4033 | DNS Security Introduction and Requirements References Referenced by | Proposed Standard | informatively references | |
| RFC 4470 | Minimally Covering NSEC Records and DNSSEC On-line Signing References Referenced by | Proposed Standard | informatively references | |
| STD 13 | References Referenced by | normatively references | ||
| STD 66 | References Referenced by | informatively references |