References from draft-ietf-calext-caldav-attachments

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.

Reference type help

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