References from RFC 8607
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 205 |
References Referenced by |
informatively references | ||
BCP 90 |
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 2518 |
HTTP Extensions for Distributed Authoring -- WEBDAV
References Referenced by |
Proposed Standard | normatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
RFC 4331 |
Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections
References Referenced by |
Proposed Standard | normatively references | |
RFC 4791 |
Calendaring Extensions to WebDAV (CalDAV)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4918 |
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5023 |
The Atom Publishing Protocol
References Referenced by |
Proposed Standard | informatively references | |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5546 |
iCalendar Transport-Independent Interoperability Protocol (iTIP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 6266 |
Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6638 |
Scheduling Extensions to CalDAV
References Referenced by |
Proposed Standard | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | normatively references | |
RFC 7240 |
Prefer Header for HTTP
References Referenced by |
Proposed Standard | normatively references | |
RFC 7320 |
URI Design and Ownership
References Referenced by |
Best Current Practice | informatively references | |
RFC 7538 |
The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | informatively references | |
RFC 8144 |
Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)
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 | |
STD 68 |
References Referenced by |
normatively references |