References from RFC 5785
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 26 | References Referenced by | normatively references | ||
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 2616 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Draft Standard | informatively references | |
| RFC 3986 | Uniform Resource Identifier (URI): Generic Syntax References Referenced by | Internet Standard | normatively references | |
| RFC 4918 | HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) References Referenced by | Proposed Standard | informatively references | |
| RFC 5226 | Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by | Best Current Practice | normatively references | |
| RFC 5741 | RFC Streams, Headers, and Boilerplates References Referenced by | Informational | Possible Reference | Possible Downref |
| STD 66 | References Referenced by | normatively references |