References from rfc5995
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 70 |
Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols Refs Ref'd by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 Refs Ref'd by |
Draft Standard | normatively references | |
RFC 3253 |
Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 3470 |
Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols Refs Ref'd by |
Best Current Practice | informatively references | |
RFC 3744 |
Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 4791 |
Calendaring Extensions to WebDAV (CalDAV) Refs Ref'd by |
Proposed Standard | informatively references | |
RFC 4918 |
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Refs Ref'd by |
Proposed Standard | normatively references | |
RFC 5023 |
The Atom Publishing Protocol Refs Ref'd by |
Proposed Standard | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates Refs Ref'd by |
Informational | Possible Reference | Possible Downref |